AI Receptionist
Missed-call text-back for home service businesses
A homeowner calls your shop at 12:15 while your whole crew is on roofs. Nobody picks up. They do not leave a voicemail. They call the next shop, which answers. You just lost a job you never knew existed, and your phone log is the only witness.
This happens constantly in home services. The crew is the business, and the crew cannot answer the phone while they are working. Missed-call text-back exists for exactly this gap. The moment a call goes unanswered, the caller gets a text: a human-sounding message, from the business, acknowledging the missed call and starting a conversation. It does not replace answering. It catches what answering missed.
What the text should say
The research on this is consistent and refreshingly simple. Keep it to two or three sentences. Use a real name. Reference the missed call directly so the caller knows why they got the text. Set an expectation for what happens next. Skip anything that sounds like marketing.
Weak version: “We received your call. Please hold while a representative reviews your inquiry.” Nobody believes a representative is reviewing anything. Strong version: “Hi, this is Dan from Apex Plumbing. Sorry we missed your call. I will call you back within the hour.” The second one works because a name and a specific promise make it feel like a person wrote it, even when a system sent it.
The expectation is the load-bearing sentence. “I will call you back within the hour” only works if someone calls back within the hour. If your shop cannot make that window, promise the one you can: “We will call you back today before 5.” A kept modest promise beats a broken fast one every time.
Timing: fast for urgent, measured for the rest
Not every missed call deserves the same speed. For calls that smell like emergencies, a burst pipe, no heat, sparking, the text should go out immediately and offer a path: “Reply URGENT if this cannot wait.” For routine inquiries, an instant reply can feel oddly aggressive, like the shop was watching the phone and chose not to pick up. A short delay reads more naturally, and the message can be calmer: “Sorry we missed you. We will call back this afternoon.”
The smarter setups let the AI receptionist decide which is which. Because it knows why the call came in, or at least what the caller said before hanging up, it can send the urgent text to the urgent caller and the routine text to the routine one. That is the difference between a text-back feature and a text-back system.
Two-way, not a dead end
A text that says “we will call you back” and accepts no reply is a slightly nicer voicemail. The versions that book jobs are conversational. The caller can reply with what they need, and the system can ask the two or three questions that matter: what is going on, where is the property, when are you available. By the time a human calls back, the intake is done and the conversation is about scheduling, not discovery.
This is also where the emergency path earns its keep. A caller who replies URGENT should not wait in the same queue as everyone else. Their message should page the on-call tech or trigger the escalation the shop set up for after-hours emergencies. The text-back is the tripwire. The dispatch process behind it is what saves the job.
When text-back is not enough
Be honest about the limits. A text-back is reactive: the caller already experienced not getting through. It recovers some of those callers, but the ones who needed help right now may already be gone. For shops where a large share of calls are urgent, answering the call in the first place with an AI receptionist converts better than the best text-back ever will. The text-back is the safety net under the trapeze, not the trapeze.
The practical setup for most home service shops is both: the AI answers live calls during the day when the crew cannot, and the text-back catches whatever still slips through, including after-hours. For the answering side, see turning lost calls into booked jobs. For why speed matters so much in the first place, why the first five minutes matter lays out the case, and calculating what missed calls cost helps you put a number on the gap before you fix it.
Start with the message, then the system
Before buying anything, write your text. Two versions: urgent and routine. Read them out loud. If they sound like a person from your shop, you are ready. Then make sure someone owns the replies. A text-back system that nobody monitors is a promise machine with no one keeping the promises. Assign the inbox, set the callback windows, and check the first week’s replies. The callers will tell you, in their own words, whether the net is catching them.
I write the agents that run on clinic phone lines and inboxes: the conversation engine and the booking logic behind them, plus the integrations with Pabau, Fresha and Phorest. Everything here comes out of systems we have actually shipped, not a content plan.
