Automating customer contact: from first question to an appointment in your own system

The chain: where a question arrives and where it has to end

At most small businesses every channel runs differently: the phone ends on a sticky note, the web form in a mailbox nobody owns, and WhatsApp on the manager’s personal phone. Automating customer contact means every question goes through the same six steps:

1. 01Arrival. Phone, email, web form, chat, WhatsApp — each with its own noise and its own expectation about how fast you reply.
2. 02Recognition. Who is this, are they already in your system, and what is the question about.
3. 03Completing it. Collecting the three or four details you always need: address, make and model, order number, preferred date.
4. 04Routing. A breakdown goes to planning, an invoice query to accounts, a new enquiry to sales.
5. 05Recording. As a ticket, a diary appointment or a quote request in your own package. Not in a separate tool alongside it.
6. 06Feedback. The customer knows what happens next and when. This step gets skipped most often.

The phone: what an AI receptionist actually does

An AI receptionist — also sold as an AI telephonist, an AI phone assistant or part of an AI phone system — is software that answers the phone, understands what is said and acts on it in your system. There is one reason people look for it: calls get lost. What such a link does is limited and concrete:

• Answering when nobody else would: outside opening hours, or when every line is busy. Not always — for many businesses that is exactly the wrong choice.
• Asking who is calling, from which company, what it is about and on which number to call back. Four questions, no more.
• Recognising the subject: a breakdown, a quote request, an invoice query, or somebody who wants to move an appointment.
• Putting the call into your package as a note or callback request, and where it fits, as a diary appointment.
• Transferring to the right colleague, rather than to a central number where the call starts all over again.

What an AI on the phone should not do, and where it goes wrong

Just as important is what you keep away from it. No negotiating: no discounts, no confirming prices, no delivery dates — a promise is a promise, even from a computer. And no handling complaints: an angry customer wants a person.

One boundary is not up for discussion. You tell the caller at the start that they are speaking to a computer, and there is always a way out to a person: anyone asking for an employee gets one straight away.

Beyond that, the phone is the hardest link of all, and sales pitches rarely say so:

• Intelligibility. An engineer on a building site, a driver in a moving cab: background noise pushes recognition down, and so do strong accents. Postcodes, house numbers and email addresses come through wrong most often — have those repeated back or texted.
• Callers who want putting through immediately. Some will not wait for the opening line and simply say “John, please”. If your system does not react, you have lost the caller.
• The feeling of being fobbed off. This is the real risk: somebody who answers three questions from a computer and then hears nothing is angrier than somebody who got voicemail.

The mailbox: automating customer questions starts here

For most businesses the mailbox is the channel with the most volume and the dullest questions. Start there, not on the phone: cheaper, easier to check, and a mistake is recoverable.

This link sorts and forwards. Mail to info@ or sales@ is read, linked to the customer and the open order, and passed on by subject: a breakdown becomes a ticket for planning, an invoice query goes to accounts with the invoice number attached, an enquiry becomes a quote request.

The second step is draft replies for the questions that come back every week: where is my order, can I have a copy invoice. The AI writes the draft using data from your system, a person reads it and sends it — always, at the start.

What goes wrong: emails that only say “see attached”, forwarded chains where the real question sits at the bottom, and customers asking three things at once. That last one trips up almost every setup that treats one email as one subject.

The form on your site: the cheapest gain there is

The contact form is the most-skipped link and at the same time the cheapest. An enquiry that arrives as “I would like some information” costs you two emails and two days before you know what it is about.

Complete means the questions adapt to what somebody picks. If a visitor to a heating firm picks “my boiler has broken down”, you ask for make, model, year and a photo of the sticker; if they pick “quote for a new installation”, you ask about the property and the preferred period. The enquiry then goes straight into your system, with the customer matched if they already exist.

Where it goes wrong: too many questions. Every extra field costs enquiries. Ask only what you need to get started.

Site chat and WhatsApp: links, not an all-knowing chatbot

This is where the distinction matters most. A chat on your site does not have to know everything and does not have to sell. It is a link: it catches the question, recognises the subject, collects the few details you need and passes it on to the same place as email and the form.

That is a far smaller job than what usually gets sold as a “chatbot”, which is why it works more often. A chat that says “I do not know, but I will make sure Marieke calls you tomorrow — can I have your number?” beats one that confidently gives the wrong answer. Chat does need visitors, though; below a few hundred a week it is decoration.

WhatsApp is the fastest channel in many trades and the messiest: messages land on one person’s phone. Automating starts here not with AI but with a business channel more people can reach. Mind the cost: WhatsApp Business runs through a provider and charges per conversation. The channel does not matter, the endpoint does.

Handling: ticket, diary or a person — and what people keep doing

Everything above is preparation. What counts is where it ends, and there are only three good endpoints: a ticket in your service system, an appointment in the diary, or a person taking over with the context attached. Whether your version of Exact, AFAS, Microsoft 365 or HubSpot supports the integration you need is a question for your supplier; we check that before building.

Handing over to a person is the most important step in the chain and the worst built. It fails on one point: the customer has to tell their story again. A good handover carries who called, about what, what has been asked and answered, and what is missing — on one screen.

So automating customer service does not mean customer service disappears. Only the first two minutes of each contact stop being manual; after that it stays human work: exceptions, complaints, promises about price and delivery, and the conversation that carries a relationship. One task is added: somebody reviews a few conversations every week, otherwise quality slips away unnoticed.

How this plays out per department is covered on our customer service department page.

An off-the-shelf tool, or this

There are subscriptions that do part of this out of the box: phone assistants with their own number, helpdesk packages with AI replies, chat widgets you install in ten minutes. If your current package has such a feature you are not using, switch that on first.

A tool like that hits three walls. The integration: the conversation lands in the tool, not in your system, so you gained a screen rather than lost work. Your own language: standard software does not know your product names or exceptions. And the chain, because a tool covers one channel while your customer picks.

We work the other way round: process first, product second, and per link the simplest thing that works — an AI component, an integration, or just a better form. If your current package is good enough, we will say so.

Recordings, transcripts and GDPR

This is not legal advice; run it past your own lawyer or privacy officer before you go live. These are the points you have to decide on beforehand:

• Say that this is an automated assistant, at the start of the call and visibly in the chat. That is not optional.
• Decide whether you record calls or only keep a transcript or summary. All three are personal data; less is usually better.
• Make sure anyone who does not want anything recorded can carry on with a person.
• Agree a retention period and actually delete. Two years of call recordings in a folder is a risk without a purpose.
• Check where the data sits and who can reach it, including at the speech model supplier. Ask for a data processing agreement and put in writing that your data will not train models.
• Watch out for sensitive subjects: a health question or a payment arrangement touches data you would rather not process automatically.

What automating customer contact costs

Our rates are fixed. A core session on your shop floor is a half-day (4 hours) at €596 excluding VAT and travel; a full day is €1,192. The advisory rate is €149 per hour. Building is €110 per hour for straightforward work and €165 for complex development, paid monthly in advance from an AI budget you set. Travel is €0.45 per kilometre. Running costs come on top and scale with your volume:

• Telephony is the most expensive link: you pay per call minute for speech recognition and spoken answers, plus whatever your telephony provider charges. At hundreds of calls a week that is a real monthly item, which we work out beforehand.
• Email, forms and chat are cheaper: you pay per processed message, small amounts that only show up at volume.
• WhatsApp charges per conversation through the provider, with its own rules per conversation type.
• Maintenance: a supplier changes an integration, an answer no longer fits. Budget a few hours a month once something runs.

When not to start this, and how to start properly

Three situations in which we advise against starting. Too little volume: at a handful of calls a day you never earn a build back, and a clear voicemail with a same-day callback serves you better. Too many exceptions: if nearly every question is bespoke, there is little to automate. And no system to put it into: if the arrangements live in people’s heads, you are building a chain that ends nowhere.

If you do start, do it with one channel: the one with the most volume and the dullest questions. At almost every business that is the mailbox or the form — not the phone. Let it run for a few weeks and add a second only once the first stands up unsupervised.

The order that works best: the endpoint first, then the biggest channel, then the feedback to the customer, and only then the phone. Start the other way round and after three months you have an AI receptionist and nothing else.

Frequently asked questions

What we do for this

Further reading

Other topics

Start with the free AI scan

Five minutes online, no sales pitch: you get a score, concrete opportunities and a price indication. Already know which channel matters most? Book an intro call and we will discuss whether a core session on your shop floor is worth it.