Running-late notices
When the morning job runs long, one field update texts the rest of the day’s customers their new windows. Nobody stands at a window wondering.
Trigger
Dispatch updates the Running late field or shifts the day’s windows.
Built from
Why teams set this up
A twenty-minute overrun at 9am becomes four angry customers by 4pm, each angrier than the delay deserved, because nobody told them.
One update reaches every affected customer
Fewer doorstep confrontations about timing
Reschedules sorted before the truck arrives
How the automation runs
The 8am water heater turns into a bigger job. Dispatch flags it once, and the 11, 1, and 3 o’clocks each get their new windows by text. The 3 o’clock moves to tomorrow by reply, which conveniently gives the crew their lunch back.
- 1Ticket field
Dispatch flags the delay once
- 2Outbound SMS
Every affected customer gets their personal revised window
- 3Two-way texting
Reschedule replies are handled on the spot
- 4Calendar
Accepted changes rewrite the day’s schedule
- 5Team notification
Dispatch sees who accepted, moved, or went quiet
The same workflow in different businesses
Home services
Schedule slips broadcast themselves, and customers adjust by reply instead of by complaint.
Property management
Vendor delays reach affected residents automatically, keeping access appointments intact.
Built from standard Frontdesk blocks
No custom development. Each step is a building block you can rearrange, retime, or extend, so this workflow can grow into the next one.
Retention journeys that include this workflow
This workflow is one step inside larger retention journeys that run the full customer lifecycle.
Customer retention
Combine behavior, sentiment, service history, and conversation data into proactive retention workflows.
See the journey →Churn risk intervention
Route each at-risk customer into a playbook based on value, issue, urgency, and preferred channel.
See the journey →Renewal journey automation
Coordinate education, value review, objections, approvals, offers, and signatures before the deadline.
See the journey →Common questions
How does the running-late notices workflow start?
Dispatch updates the Running late field or shifts the day’s windows.
Which channels does this use?
This workflow runs over sms, two-way sms. Each step can use the channel that fits the customer and the urgency.
Can my team stay in control of when it fires?
Yes. The trigger can be a field a person flips on a ticket or contact, so a human makes the decision and Frontdesk does the follow-through. Any step can also route to a teammate with the transcript and collected data.
Does it keep our records up to date?
Every call, text, and email in the workflow is logged against the contact and ticket, with transcripts attached. Frontdesk can also sync contacts and fields to your CRM.
What happens when a customer needs a human?
The workflow hands off with context: the right teammate gets the full history, the transcript, and the collected answers, so the customer never repeats themselves.
Thinking bigger than one workflow?
The customer journey library maps full lifecycle automations across activation, onboarding, retention, and growth.
Explore customer journeys →More from field service operations
Dispatch, ETAs, parts, and emergencies coordinated over phone and text.
Emergency dispatch line
A dedicated line where the AI takes the address, assesses severity by your rules, pages the on-call tech, and texts the caller the ETA.
Job status update texts
Each stage of the job texts the customer as the ticket field changes: scheduled, en route, in progress, done. The phone stops ringing because people already know.
Parts arrival scheduling
When the part lands, flip Parts received and the AI calls the customer to book the install before the part gathers dust.