The worst way for a receptionist to find out about the new website assistant is from a customer. "Your chatbot said to ask you about the parking permit" is an awkward sentence to hear when nobody told you there was a chatbot.
It happens more than owners would like to admit. The tool gets set up on a quiet Sunday, goes live on Monday, and the people who handle enquiries every day are left to work out what it is, what it is saying on their behalf and whether their job is next.
Introducing an AI receptionist to staff is not a training problem. The software takes an afternoon to learn. It is a trust problem, and it is best handled before launch, in a conversation, with specifics.
What people are actually worried about
When staff go quiet in the meeting, these are the thoughts they are usually having:
- "Is this replacing me?" The first and biggest worry, and one many owners skip because it feels uncomfortable to raise. Raise it yourself.
- "Will it make me look bad?" If the assistant gives a wrong answer, the customer complains to whoever picks up the phone next.
- "More work, not less." Another inbox, another set of notifications, another thing to check.
- "It won't know our customers." Front desk staff know that Mrs Patel always books the late slot and that "just a quick question" means a twenty-minute call. They doubt software will cope.
All four are reasonable. The fourth is partly right. Pretending otherwise loses you credibility in the first five minutes.
Answer the job question in plain words
Be direct about what the assistant does and does not do. A website assistant answers visitors on your website. It does not pick up the phone, greet people at the desk, deal with a distressed customer in person or make judgement calls about exceptions.
Then say what you plan to do with the time it frees, and only say it if it is true. "I want you spending less time on opening hours emails and more time calling back new enquiries" is a real answer. "Nothing will change" is not believable and will not be believed.
If you do intend to change staffing, this article cannot help you avoid that conversation, and neither can the software.
Show them their own inbox
Abstract promises about efficiency land badly. Evidence from the team's own week lands well.
Before the meeting, go through the last month of website enquiries and emails and tally the questions that came up again and again. Then put the before and after side by side.
| Task in a typical week | Who handles it now | After launch |
|---|---|---|
| "What are your opening hours?" and "Where do I park?" | Front desk, by email and phone | Assistant answers on the website; phone calls unchanged |
| Price range questions for standard services | Front desk, often forwarded to owner | Assistant answers from published prices; unusual jobs captured as leads |
| Enquiries sent at 10pm | Waiting in the inbox until morning | Assistant takes details overnight; leads are ready at 9am |
| Complaints and refund requests | Front desk, then manager | Assistant opens a ticket and hands to a person; staff still handle it |
| Returning customers with account questions | Front desk | Still front desk, via handover |
The last two rows matter as much as the first three. They show staff the difficult, human parts of the job stay with humans.
Decide who owns what before launch
Most adoption problems are not resistance. They are a lead arriving at 7am with no clear owner, getting glanced at by three people and answered by none.
- Name the lead owner. One person checks new leads each morning and makes sure every one gets a reply. They can delegate, but the list is theirs.
- Name the content owner. One person updates prices, hours and Q&A pairs, and reviews unanswered questions weekly. This is usually the most experienced front desk person, and it should come with time set aside for it.
- Name the handover owner for each shift. Whoever is marked on duty picks up live conversations from the inbox. Everyone else can ignore them.
- Agree the reply time. Write down how fast leads get a human reply. The assistant tells customers this, so the team has to be able to meet it.
- Agree the escalation route. Decide which topics go straight to a manager, such as complaints about staff or anything legal.
Put these on one page and pin it somewhere. It sounds bureaucratic for a five-person team. It prevents the first missed lead from becoming an argument.
Let the front desk break it first
Your front desk team knows the strange, sideways questions customers ask. Hand them the test.
Give them an hour with the assistant before launch and ask them to catch it out: vague questions, typos, questions about things you stopped offering, the customer who writes three paragraphs. Every wrong or weak answer they find becomes a content fix, credited to them.
This does two things at once. The assistant improves fast, and the people most anxious about it become the people who shaped it. Front desk staff who spent an afternoon writing the answers are far less likely to be embarrassed by them later. The free FAQ generator can give them a starting draft to edit rather than a blank page.
Your next step
Before you publish the widget, hold a thirty-minute team conversation. Bring the tally of repeated questions and the before-and-after table filled with your own tasks. Raise the job question yourself in the first five minutes, then agree the owners and the reply time on the spot.
Schedule the front desk testing hour for the same week and launch only after it. Two weeks in, ask the team what is annoying them about it and fix the top item. Why your support team should help train the chatbot goes further into making them part of the ongoing work, and deciding when a person takes over will help you write the handover rules together.