Illustrative workflow
From a Missed Call to an Inspection
Starting event
A homeowner calls the roofing business outside of office hours. The call is not answered.
How the workflow moves
- 1System
Detects the missed call and checks SMS eligibility for the number.
- 2System
Sends a short acknowledgment text: 'We missed your call. This is [Company]. How can we help with your roof?'
- 3System
Creates a callback task and assigns it to the on-call owner.
- 4Owner
Reviews the task, calls the homeowner back, and qualifies the request.
- 5Owner
Books the inspection through the live calendar and confirms the time.
Exception branch
If the number cannot receive texts, the system logs the missed call and escalates the callback task with a higher priority flag. The owner is notified that no text was sent.
Sample output
Callback task: 'Missed call from 555-0100 at 6:42 PM. Text sent. Owner: Maria. Status: Open.'
Illustrative sample. No real customer data or achieved metric.
Measurement definitions
Eligible missed calls
Calls that met the configured eligibility rules during the reporting period.
Successful acknowledgments
Eligible missed calls that received a sent text confirmation.
Callback completion
Assigned callback tasks marked complete by the owner.
Booked outcomes
Callbacks that resulted in a scheduled inspection.
Questions about this workflow
- No. The system sends a text and creates a task. A person makes the callback. Automated voice calls are not part of this workflow.
Apply this to your business
A strategy session identifies whether this workflow fits your operation and what to build first.
30 minutes. For roofing owners and operating leaders.