Skip to content

An AI receptionist setup checklist: 15 things to have ready

Fifteen things to gather before an assistant answers a customer, grouped by what each one protects, with the five that are the real minimum and the three most businesses forget.

Sohail Safdar · · 6 min read

Most of setting up an AI receptionist is not configuration. It is writing down things you already know and say several times a day, in a form something else can read.

Here are fifteen of them, grouped by what each group protects, plus the five that are the real minimum and the three nearly everybody forgets.

Group one: what it will say

The five items that make up the large majority of what customers ask.

1. Services, prices and durations. One line each. Where a price genuinely depends on a visit, write a starting price and the fact that it depends: "Deep clean from $180, confirmed after we see the room." That is what your front desk says, and it is both honest and answerable.

2. Hours for each location, including the holidays you already know about. Add the one that gets missed: the difference between when the door closes and when you stop accepting work. A kitchen, a workshop and a surgery all have two closing times and customers want the second one.

3. Five core policies. Cancellation, late arrival, deposits, payment methods, what to bring. These five cover most of what an argument is ever about.

4. Your twenty most common questions, in your customers' words. From last month's texts, voicemails and web chats rather than from memory. This is the highest-value item on the list and the one most often done wrong, because the list you write from memory is the list of questions you find interesting and the list in the messages is the list people actually ask. If your service is "orthodontic consultation" and your customers type "braces for my daughter", the FAQ needs to say both.

5. Where to book. The link, written as a fact the assistant can quote in a sentence rather than as a setting buried somewhere.

Group two: what it must not say

The three items that protect you. If you do nothing else on this page, do these.

6. A written list of topics it never answers. Clinical, legal and financial judgement. Anything about another customer. Any price that depends on seeing the job. Any complaint. Write it down as a list rather than assuming the vendor's defaults cover your trade.

7. Escalation keywords. The words that send a message straight to a person before anything else happens. Start from the universal six categories and add your trade's own: gas and flooding for a plumber, bleeding and swelling for a dentist, court and arrest for a law firm. The starter list has all nine trades and the reason to tune them to over-fire.

8. The handoff wording. One or two sentences in your voice saying who will reply and roughly when. Write this by hand rather than letting it be generated, because it is the reply a customer is most likely to remember: it arrives at the moment they did not get what they asked for.

Group three: who picks up

9. A named owner for handed-off conversations, per location, with a named backup for their days off. Skipped more than any other item on this list, and the direct cause of the worst possible week one: customers who were told a person would reply, and then waited.

10. Your team's roles. Who may approve drafts, who may edit the knowledge, who may only read. Worth deciding before rather than after somebody edits a price by accident.

Group four: how it reaches people

11. A texting number registered for business messaging. In the US this means A2P 10DLC brand and campaign registration, which takes time you cannot compress, so start it early. Choosing a business texting number covers the choice and the 10DLC guide covers the process.

12. Consent wording for reminders, shown as an unticked box at the point of booking. Unticked matters: a pre-ticked box is not consent, and reminders are the one message type where a missing consent record is noticed.

13. Your web chat placement, if you use web chat. Which pages, and what the bubble says before anybody clicks it.

Group five: how it sounds, and how you will check

14. A tone paragraph. Four or five sentences: formality, reply length, the kind of warmth, the words to avoid, and how to say no. Setting your tone of voice has the full version and the phrases worth banning outright.

15. A supervised first week. Approval mode on, one named person reading drafts, and a daily look at the questions it could not answer. The day by day version is a week of about ten minutes a day.

The three nearly everybody forgets

Not on the list above, because they are not things to gather. They are decisions.

How much customer history it may read. There is usually a setting, with a narrow default, and it should stay narrow until you have a reason. An assistant answering one message does not need three years of somebody's conversations to answer "what time do you open", and the widest setting should be one you chose rather than one you inherited.

Who owns keeping the facts current. Not who loads them: who changes them in December when the holiday hours move and in March when a price goes up. An assistant answering from approved facts is exactly as right as those facts, and a stale fact does not produce silence, it produces a confident wrong answer. One name, and a minute a week.

What happens the first time it gets something wrong in front of a customer. Decide now, calmly, rather than in the moment: who apologises, whether you say an assistant wrote it, and who fixes the underlying fact. The answer is usually simpler than people fear, and having it decided in advance is the difference between fixing a fact and switching the whole thing off.

The order to do it in

1 to 5 first, because they are most of what customers ask and every one of them removes handovers.

6 to 8 next, because they are what protects you, and they are quick.

9 before going live. It takes thirty seconds and it is the one that ruins week one.

The rest during the first week. Do not wait for completeness: the gaps log after five days will tell you exactly what is missing, in your customers' own words, which is better than anything you would have guessed.

In Frontiva

Knowledge holds items 1 to 5 as structured facts and approved FAQs, seeded from your industry template, so a practice picking its trade at signup starts with a service list and a set of FAQ starters rather than an empty box. It can also read your existing website and documents, which is usually the fastest route to a first draft of items 1 to 3, with everything staying in a review queue until you approve it.

The AI agents settings hold items 7, 8 and 14, plus the approval mode that is item 15, and the readiness suite is how you check items 6 and 7 actually work before a customer tests them for you. For the wider process, how to train an AI receptionist on your business covers the afternoon in detail.

Frequently asked questions

How long does setting up an AI receptionist take?

For a single-location business, an afternoon to gather items 1 to 10, then a supervised week to find what you missed. The afternoon is the part people overestimate and the week is the part they skip. Nearly all of the afternoon is writing down things you already know and say out loud several times a day; almost none of it is configuration.

Do I need all fifteen before going live?

Five are the real minimum: your service list with prices, your twenty most common questions, the list of topics it must never answer, your escalation keywords, and a supervised first week. The rest can be finished while it runs. The one item never to skip is the list of things it must not answer, because going live without it means the first sensitive message gets an answer rather than a person.

What if my prices change often?

Keep them in exactly one place and give one named person the job of changing them the same day. A stale price is the most common wrong answer any assistant gives, and the reason is never the software: it is that the price lived in three places and two of them were updated. If a price genuinely depends on seeing the job, write a starting price and say that it depends, which is both true and the answer your front desk already gives.

Where do I get the twenty most common questions from?

Last month's texts, voicemails and web chats, not from memory. The list you write from memory is the list of questions you find interesting; the list in the messages is the list customers actually ask, in the words they use. Those differ more than anybody expects, and the wording matters as much as the question, because an FAQ phrased in your trade's vocabulary will not match a customer asking in theirs.

Who should own handed-off conversations?

One named person per location, with a named backup for their days off. Not a team, not a shared mailbox nobody owns, and not the owner unless the owner is the person who answers customers. This is the most skipped item on the list and the one that produces the worst week-one outcome: customers who were promised a person and waited hours, which is a worse experience than never being promised one.

Get the next one by email

Email me when Frontiva publishes a new guide or post. At most one a week, nothing else, and an unsubscribe link in every one.

To keep spam out, we record your IP address, approximate location and browser with your message. Privacy Policy

Start free. Be live this week.

Built for dental, med spa, home services, and the businesses that live on the phone.