The Core: Real-Time Field Service Workflow Automation
The Core is the automation and intelligence layer growing inside Field Ascend. Today, its live beta observes business events in real time, matches explicit tenant rules, performs guarded actions, and records exactly what happened.
That working event stream is the foundation for the bigger goal: an AI operations manager that can help coordinate a field service business across work orders, customers, field technicians, compliance, and finance—with human control matched to the risk.
Important: the current beta is rules-based automation. Autonomous AI decision-making remains a future vision.
What is The Core today?
The Core is a live-beta field service automation engine. It watches meaningful changes from the database and scheduled clocks, turns them into business events, evaluates your enabled process templates, runs approved action types, and stores an audit result.
It is useful automation today. It is not yet the autonomous AI operations manager described in the long-term vision, and this page keeps those two stages deliberately separate.
How The Core Works
Observe the truth, apply a clear rule, act through a constrained handler, and preserve the evidence.
A live feed of what the business is doing
The Core listens below individual pages and apps, at the database-change layer. That means it can observe a work order update whether it came from the office, mobile app, customer workflow, background task, or another approved integration.
- Work order, schedule, field technician, invoice, estimate, quote, ticket, and purchase-order events
- Clock-derived events for time-sensitive work such as overdue invoices
- Plain-language summaries beside the underlying event type
- A rolling recent feed rather than a permanent copy of every raw database change
Build from guarded process templates
Choose a template, define when it should fire, add all-match conditions, and review the intended action. The beta stays template-led so automation power grows inside clear operational boundaries.
- When a mapped business event occurs
- Only if status, category, priority, value, date, or other supported conditions all match
- Then update an allowlisted field, send an approved email template, or call a secure HTTPS webhook
- Lookup conditions and updates store stable IDs as well as names, so renaming a status does not silently break the rule
Run history that explains every outcome
Automations are operational changes, so the log matters as much as the builder. Run History shows what fired, whether it was a dry run or live, why an email was skipped, what action ran, and the relevant before-and-after state.
- Dry-run, success, and failed outcomes
- Filter by automation and inspect recent runs
- Before-and-after snapshots for field updates
- Plain-language skip reasons when recipient preferences or templates do not allow an email
- Seven-day statistics on each automation card
Customer communication with audience controls
The Core does not invent a second email system. Content comes from your existing Email Setup templates; the audience comes from each contact's notification preferences and, for work order emails, their selected job categories.
- Booked, moved, and canceled appointment updates after a settle window
- Technician en route, arrived, work order status, and completed-work messages
- Invoice, credit, estimate, quote, ticket, and service-due workflows
- No silent fallback to a generic customer email when nobody is opted into the right notification
- The final schedule state is emailed after rapid planner edits settle, avoiding a message for every drag
It complements existing AI and field service workflow automation without duplicating those tools.
Automation With Safety Rails
The Core is designed around reversible learning, constrained actions, and visible evidence—not a black box with unrestricted database access.
Mandatory seven-day dry run
Every new automation listens and records what it would have done before it can perform live actions.
Account Pause All
Authorized users can pause every account automation without deleting rules or history. A separate engine-level emergency-stop setting exists for operational intervention; it is not a second self-service button.
Cooldown and volume limits
Per-rule cooldowns and hourly or daily caps absorb redelivery, prevent loops, and disable abnormal firing behavior.
Allowlisted changes only
Field updates are limited to supported entities and tenant lookup values; existing target values become no-op writes.
Secure outbound webhooks
Webhook actions require HTTPS, block private and reserved destinations, resolve DNS, and use a short timeout.
Permission-gated management
A dedicated automation permission controls who can view and change processes that may edit data or send messages.
What Is Live, What Is Next, and the Long-Term Vision
The honest product map matters. The foundation is live; increasingly intelligent operations are the direction, not a claim about today's beta.
Real-time rules and actions
- Business event feed
- Template-based automations
- All-match condition builder
- Field update, email, and webhook actions
- Dry run, pause controls, and Run History
More expressive automation
- Build-from-blank processes
- AND/OR condition groups
- Delayed and scheduled action steps
- Create-record actions
- SMS, push, and additional action plug-ins
An AI operations manager
- Classify inbound work
- Recommend and coordinate dispatch
- Manage customer journeys across channels
- Drive estimate-to-invoice follow-through
- Spot operational and maintenance risk proactively
Frequently Asked Questions
What is The Core today?
A live-beta event and automation engine. It observes mapped business events, evaluates explicit rules and conditions, runs approved action types, and stores an audit result.
Does AI make autonomous decisions now?
No. Today's beta is deterministic. AI decisions, proactive operational scans, and per-action autonomy levels are future vision and will require their own controls and release testing.
What actions are live?
Allowlisted field updates, template-driven email, and secure HTTPS webhooks. Create-record, delayed, SMS, push, and AI actions are not live in the current beta.
How do you test an automation safely?
Every new rule spends seven days in dry-run mode. Run History records what it would have done, letting an authorized person review real event matches before live actions begin.
Can I stop all automations?
Yes. Authorized account users can use Pause All while keeping rules, conditions, and history intact. A separate engine-level emergency-stop setting exists for operational intervention rather than as a second button in the Core screen.
How do I access the beta?
The rollout is controlled by account access and a dedicated permission. Contact Field Ascend to discuss availability and a suitable first process.
Related Field Ascend Capabilities
Start With One Process. See What Your Business Is Telling You.
Talk to us about The Core beta, the safety rails, and a practical first automation that removes repetitive administrative work without hiding control.
Ask about The Core beta