Answer the Missed Call, Fast

A missed call is not a lost customer. It is a customer who is going to call the next shop on the list in about four minutes.

The fix is not a bigger front desk. It is a text that arrives while they still have the phone in their hand, saying something worth reading.

The polite nothing does not work

The default message every system ships with is some version of sorry we missed you, we will get back to you shortly.

That message has never earned anybody a job. It asks for nothing, offers nothing, and reads as an automated shrug. Worse, it uses up the one moment when the customer was definitely paying attention.

Ours says what we do and asks exactly one thing. If a price is genuinely knowable at that point, the price goes in. That last part is not decoration. Customers ask what things cost constantly, and most automated replies in this trade have never once answered.

Write like a person, which means shorter

We measured our own automated messages against how our owner actually texts customers, on the same day, to the same kinds of people. The gap was not flattering.

His messages average about ten words. Ours averaged twenty four. He never stacks two questions into one message. Ours did it in nearly half of them. He gives a number whenever a number exists. Ours gave one zero times out of sixty four.

He also opens differently. Ours began with a filler acknowledgement roughly a third of the time. His never does. He just answers.

Short, one question, a real number. That is the entire style guide and it took a spreadsheet to see it, because everybody believes their automated copy already sounds human.

One question at a time is the hard part

Stacking questions feels efficient. Ask for the name, whether it is mobile or in shop, and the year make and model, and you have everything in one message.

What actually happens is that you get one answer out of three, usually the easiest one, and now you are chasing the other two against a colder lead than you started with.

Asking one thing gets one answer, reliably, and the reply keeps the conversation alive so you can ask the next thing. It takes more messages and fewer minutes. That trade is almost always worth it.

Day and night are different conversations

A call at two in the afternoon and a call at two in the morning are not the same lead and should not get the same words.

Overnight carries the after hours rate up front, because a person calling at that hour needs to know what it costs before they get their hopes up. Putting it in later feels like a bait. Putting it in first is just respect for their time.

We derive the mode from the clock rather than switching it by hand, which matters more than it sounds. Anything a person has to remember to flip back gets left flipped, usually on the night it costs the most.

Keep the message in one place

Ours existed in four places at one point. The live setting, the value restored automatically every morning, and two separate fallbacks in the code.

Change one of those and the message reverts overnight and nobody can work out why. It looks like the change never saved. We lost real time to this.

If your customer facing copy exists in more than one place, that is a bug waiting for a deadline. Find every copy before you edit any of them.

Alarm on the outcome, not on the job

The trap with anything that runs on a timer is watching whether the task ran instead of whether the thing happened.

A sweep can execute flawlessly every minute for a full day, send nothing at all, and show green the entire time. We have had exactly that, and the alert that was built to catch it was watching the wrong signal.

Alarm on texts sent. On replies received. On leads answered. Never on ticks completed, because a tick completing is a statement about your server and tells you nothing about your customers.