Plain answers about the phone, the diary and the jobs in between.

Nobody sends you an invoice for a job you never heard about, so the cost of a missed call stays invisible. Most owners guess, and the guess can be out by a long way in either direction.

Your phone provider’s call log and last month’s invoices are enough to put a real figure on it. With that figure you can judge any fix, whether it’s another person, a service or software, by whether it costs less than it recovers. If the number turns out small, that is worth knowing too.

Voicemail, a staffed answering service and an AI receptionist can all pick up the phone. They differ in what happens next. A message tells you someone called; a booked visit means the job is already in the diary.

Start from what a successful call means for you, how many calls can arrive at once, and which enquiries need a person’s judgement. Then put the same questions to every provider and hear how each one handles a call like yours.

The usual worry about automated call answering is less about how it sounds and more about what it might say. That worry is justified, and the answer is to write the limits down before the first call: which prices are fixed, which topics always go to a person, and what happens when the system is unsure.

Those rules should be in plain English, so you can read them and change them. How Ringbridge handles a call shows where they apply during a real conversation.

A demo shows a system on a good day, with calls the supplier picked. Your customers will ring with half the details, a bad signal and a question nobody planned for. The only way to know how it copes is to try those calls yourself before you divert your number.

The articles here cover the practical side of switching over: testing, routing and what to check in the first weeks. The practical guide to AI call answering covers the set-up decisions that come before.