Skip to content

Your AI receptionist's first week, day by day

What to read and what to fix on each of the first seven days, which kind of day-one failure is fine and which is not, and the three thresholds that tell you it is ready for more autonomy.

Sohail Safdar · · 6 min read

The first week of an AI receptionist is not a launch. It is supervision, and the work is reading.

What makes it worth doing properly is that the gaps are densest in week one and they will be found by somebody either way. Either you find them from drafts nobody sent, or your customers find them from replies they received.

Day 0: before a single customer sees anything

Two things, both before the first real message.

Run the readiness test, if your assistant has one. Not a demo conversation you steer, but a fixed scored set: an unknown question, a request for a human, an attempt to manipulate it, a sensitive question, and a real price question from your own service list. The point of a fixed set is that you cannot accidentally test only the things you already know work.

Name the person who owns handovers, and a backup for their days off. This is the single most skipped item and it is the one that makes day five go wrong.

Day 1: watch, and change nothing

Approval mode on. One person reads every draft before it sends. Fix only outright errors; write everything else down.

Expect "I am not sure, somebody will come back to you" on questions you would have sworn were obvious. That is correct behaviour for a system that has not been told something, and it is the most useful output of the day.

The distinction worth making on day one is between two kinds of failure that look similar in a list:

And one failure that is not negotiable: a clinical, legal or urgent message that got an answer instead of a person. If that happens on day one, stop and fix the escalation before the next message arrives.

Day 2: fill the obvious gaps

Open the list of questions it could not answer and work down it. Most will be things everybody in the building knows by heart: parking, a price, whether you see children, what to bring.

The valuable part is not that the gaps get filled. It is that the list is written in your customers' own words, which is the one thing you cannot produce by sitting in a room guessing. If your FAQ says "orthodontic consultation" and the gaps log says "braces for my daughter", rewrite the FAQ.

A dozen facts added on day two typically removes a third of the handovers.

Day 3: tune the tone, once

Read twenty drafts in a row, out loud. Reading aloud catches what reading silently does not.

If they are too formal, too cheerful or too long, change the tone paragraph once, then reread the same twenty. Do not edit individual replies for tone: that fixes one message and teaches the system nothing. Setting your tone of voice has the paragraph and the phrases worth banning.

Resist tuning tone again on day four. Two changes in two days and you cannot tell which one did what.

Day 4: try to break the handovers

From your own phone, deliberately send the messages that must reach a person:

Confirm each one handed off, and confirm somebody actually saw it. Those are two different checks and the second is the one that fails.

Then try the awkward versions, because customers will. The emergency word inside a longer sentence. The complaint that never uses a complaint word. The request for a person phrased as "is there anyone there".

Day 5: look at the numbers, especially the waiting

Four numbers:

  1. How many conversations it handled.
  2. How many it handed over.
  3. How long handed-over customers waited for a person.
  4. How many drafts your team edited before sending.

Number three is the one that matters and it is not about the AI at all. A customer who was promised a person and then waited three hours has had a worse experience than one who got a plain "we are closed, we open at nine". If that number is bad, the fix is ownership, not tuning, and it is a conversation with the team rather than with the settings.

Number four is the best single measure of whether this is working. Edits trending down means the system is learning your business. Edits flat after five days means something structural is wrong, usually the knowledge rather than the model.

Day 6: fix what repeated

Go through the edits your team made and look for the same edit twice. Every repeated edit is one of three things:

Repeated edits are the highest-value signal of the whole week, because somebody has already done the work of identifying the right answer. All that is missing is moving it from a person's head into the knowledge base.

Day 7: decide, narrowly

If the three thresholds hold, let the easy conversations send on their own:

Then widen it narrowly. Hours, directions, parking, the booking link: these can go autonomous with very little risk, because a wrong answer is inconvenient rather than expensive. Keep prices, new-customer enquiries and anything in a sensitive category supervised for longer, and keep them supervised separately rather than as part of one switch.

If the thresholds do not hold, run another week. Another week of supervision costs one person ten minutes a day. The alternative costs a customer.

What the second week is for

Mostly nothing, which is the point. Read the gaps log twice a week, read the escalated conversations once a week, and widen autonomy one question type at a time.

The one scheduled job that does not go away: somebody owns keeping the facts current. Holiday hours, a price change, a service you stopped offering. An assistant answering from your approved facts is exactly as right as those facts are, and a stale fact does not produce silence, it produces a confident wrong answer.

In Frontiva

AI agents start in approval mode, so day one is the default rather than something to configure. The knowledge gaps log counts every question the agent could not answer and keeps the customer's own wording, which is what makes day two work. The readiness suite is the day-zero test described above, and it can be re-run whenever the knowledge changes. The playground is where to do day four's deliberate breakage without using a real conversation.

For the day-seven decision specifically, autonomous vs approval mode sets out what each mode does and does not change.

Frequently asked questions

What if the AI is wrong a lot on day one?

Expect it, and look at the shape of the wrongness rather than the amount. Saying it does not know is the correct behaviour for a system that has not been taught something yet, and a day of those is a day of free research into what your knowledge base is missing. What is not fine on day one is a confident answer that is wrong, or a sensitive message that got answered rather than handed over, and those two need fixing before anything else.

Who should read the drafts during the supervised week?

Whoever answers the phone today. They know the right answer, they know the tone, and they are the person who can tell in one glance that a reply is subtly off. It should not be the owner if the owner is not the one speaking to customers, and it should not be split between four people, because a single reader notices the pattern across twenty drafts and four readers each see five.

Can we skip the supervised week and go straight to autonomous?

You can, and the cost is that your customers find the gaps instead of you. Every missing fact becomes a wrong answer somebody received rather than a draft somebody caught, and the first week is exactly when the gaps are densest. If you are going to skip it, skip it for the narrow question types only (hours, directions, the booking link) and supervise prices and new customers.

How long should the handed-off conversations wait for a person?

Minutes during opening hours. If handed-off customers are waiting hours, that is not an AI problem and no amount of tuning will fix it: the handovers are going somewhere nobody owns. Name one person per location, with a named backup for their days off, before going live rather than after noticing.

What are the signals that it is ready for more autonomy?

Three, and they should all hold. Most drafts going out unedited over a run of twenty rather than cherry-picked. The list of questions it could not answer shrinking day on day rather than staying flat. And every deliberate handover test passing, including the ones you tried to be clever about. Any one of those failing means another week, and another week is cheap.

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.