Service dispatch
Field services
TriggerNew service request from booking app, phone log, or CRM
Steps- Classify the request type and required skill
- Match against available technicians and SLAs
- Draft a dispatch with travel estimate and parts list
- Notify the technician and the customer
ReviewDispatcher approves the assignment for high-priority or first-visit jobs.
OutputTechnician dispatched; customer notified with ETA; ticket open with full audit trail.
Status follow-up
Cross-vertical
TriggerCron — runs on a schedule (daily, hourly) per workflow
Steps- Pull current state across systems (CRM, ticketing, ops board)
- Identify items past their SLA or stalled
- Draft a status update or escalation
- Send to the responsible owner with context
ReviewExternal-facing follow-ups pause for an account owner; internal updates send auto.
OutputDaily digest of stalled items; status updates sent; nothing slips because nobody noticed.
SOP execution
Cross-vertical
TriggerWorkflow or button-trigger — "run our standard onboarding"
Steps- Read the SOP for this scenario from your knowledge base
- Execute each step against the right system
- Pause at named human-review gates
- Log every step with timestamp and outcome
ReviewSOP-defined review gates pause the workflow until a human approves.
OutputSOP run end-to-end; full audit trail of who approved what.
Cross-system handoff
Cross-vertical
TriggerState change in System A (e.g., deal closed in CRM)
Steps- Validate the data is complete enough to hand off
- Map fields from System A to System B's schema
- Create or update the System B record
- Notify the receiving team with a context summary
ReviewPauses if any required field is missing or low-confidence.
OutputClean handoff between teams; no manual re-typing; audit log of every transfer.