How to use it
- Acknowledge the missed call directly.
- Give the next response window clearly.
- Offer one simple next step instead of three choices.
These are meant to be useful right away, even before you change your software stack.
Use these when a lead calls after hours or no one can pick up fast enough. The goal is not to sound robotic. The goal is to buy a little time and keep the conversation alive.
Hi {{first_name}}, thanks for calling {{company_name}}. We missed you, but we did get your call. If you text back your address and a quick note on the issue, someone from our team will follow up first thing in the morning.
Hi {{first_name}}, this is {{company_name}}. We missed your call. If this is urgent, text your address, the problem, and the best callback number. We will route it as quickly as we can.
Use these when quotes go out and then disappear into silence. Good follow-up is clear, short, and timed around buyer decision points.
Hi {{first_name}}, thanks again for meeting with {{company_name}} today. Your estimate is ready. If you want, I can also text a quick summary of the recommended option and next steps.
Hi {{first_name}}, checking in on the estimate we sent over for {{project_name}}. Happy to answer questions or walk through options if that helps you make a decision.
Use these right after the job when the customer still remembers the result and the crew experience. The best review request feels specific and easy.
Thanks again for choosing {{company_name}} today. If the visit went well, would you mind leaving a quick review here? {{review_link}} It helps other homeowners know what to expect.
We appreciate the opportunity to help with {{project_name}}. If you have a minute, a quick review here would mean a lot to the team: {{review_link}}
Use these to reduce inbound "where is the tech?" calls and make the day feel more organized for customers and office staff.
Hi {{first_name}}, {{tech_name}} from {{company_name}} is on the way and should arrive in about {{eta_window}}. If anything changes, we will let you know.
Use these when you need to respond without sounding defensive. The public response should show accountability and a path to fix the issue.
Thank you for the feedback. This is not the experience we want associated with our team. We are reviewing what happened and would like the chance to make it right. Please contact {{name}} at {{phone_or_email}} so we can address it directly.
Use these for tune-ups, recurring services, or seasonal service windows when a reminder can turn existing customers into repeat work.
Hi {{first_name}}, this is {{company_name}}. As temperatures start to shift, now is a good time to schedule your HVAC tune-up before the busy rush. Want us to send over a few appointment windows?
Use these when you want fewer misunderstandings after the work is done and a cleaner handoff into payment, review, or next-visit steps.
Today we completed {{scope_summary}} at {{service_address}}. We also noted {{follow_up_note}}. If you have any questions after today's visit, reply here and the office will help.
Use these when you want to clean up repeat admin work before adding more software. A better SOP often creates more value than another app.
Draft a one-page SOP for our office team handling {{workflow_name}}. Include trigger, owner, required inputs, customer-facing message, handoff steps, and common failure points. Keep it practical for a small contractor business.