The office should be able to see the promise.
A customer who replies to a reminder may be asking to change the appointment. Treating texting as a one-way broadcast misses that work. Keep the conversation visible and agree on who handles replies, failed sends, and schedule changes during the day.
What this looks like in practice.
Write the messages in your voice
Review the templates for confirmations, reminders, en-route updates, and follow-up. Include only the details the customer needs at that stage. Check your organization’s toggles so the messages match the workflow you actually run.
Respond with the job in view
Open the conversation from the lead, job, or app. Read the earlier messages before replying and update the work record when a customer changes access instructions or timing. A useful text should lead to an accurate job.
Watch the message log
Review sent, scheduled, and failed messages to see what happened. If a message fails or a customer uses another contact method, make the next step explicit. Automation supports the conversation; it does not confirm the customer has seen an update.
Use timing carefully.
A reminder about a visit and a follow-up on an old estimate serve different purposes. Set a cadence the team can explain and customers can understand. Keep contact preferences and applicable messaging requirements in mind, and make space for a human response when the question needs one.
Keep the handoff clear
- Two-way messages connected to customer work
- Configurable appointment and job updates
- Visible sent, scheduled, and failed states
Before you get started.
Can we turn automatic messages off?
Yes. The existing workflow includes organization-level controls for automatic message types. Review the templates and toggles before enabling them for live work.
Can we see whether a text failed?
The message log includes message status. Make reviewing failures part of the office routine so a missed notification does not become a missed appointment.