Chapter 2 · Seasonal Instructions and Testing
Review the week's conversations in 15 minutes
Follow this course in your space: your progress is saved, and the community answers your questions.
Follow for freeAn AI assistant doesn't get better on its own. It answers with your instructions and your information: if there's a gap, it falls into it every time. The only way to see it is to read what it actually answered. Not everything: a sample, once a week, in fifteen minutes.
This lesson also works if you don't have an assistant: review the replies you or your team sent by message the same way.
Before you start: what you can read
Depending on the tool, you have access to the conversation history, a summary, or only the requests it forwarded. Check what your tool keeps, and for how long: it's also a privacy question for your visitors (the lesson on the law tells you what to check). If your tool keeps nothing, read the requests it forwarded to you and the questions your customers ask you again on the phone: those are the week's failures.
The routine in 3 parts
Minutes 1 to 5 · Pick 10 conversations
Don't read at random. Take:
- 3 conversations that were handed off (the assistant said "I'll pass this on"): was it justified?
- 3 short conversations (one or two messages, then nothing): did the visitor leave satisfied or discouraged?
- 2 long conversations (more than 6 messages): why did it take so many exchanges?
- 2 at random.
Minutes 6 to 12 · Read with 4 questions
For each conversation, one line in your log, with these four questions:
- Accurate? Is the answer correct, based on your information?
- Complete? Did the visitor have what they needed to act (a link, a number, a date)?
- Careful? No promises, nothing made up, no advice outside its role?
- Short? Easy to read on a phone, with no unnecessary paragraphs?
A "no" to any question = a fix to make.
Minutes 13 to 15 · Fix one thing only
Pick the fix that comes up most often and make it right away:
| What you see | What you fix |
|---|---|
| It doesn't know a piece of information people ask for | Add the information to block 2 (sources) |
| It hands off a simple question | Add the answer to your FAQ |
| It promises or guesses | Strengthen the rule in block 4, with a fallback line |
| It writes long paragraphs | The 3-line rule in block 3 (lesson 5) |
| It misreads a way of phrasing something | Add that version of the question to your FAQ |
One fix per week. You'll see its effect the following week; with five fixes at once, you won't know which one worked.
The review log
| Date | Conversation (summary, no name) | Accurate | Complete | Careful | Short | Fix |
|-------|---------------------------------|----------|----------|---------|-------|-----|
| 12/7 | Delivery before Christmas? | Yes | No | Yes | Yes | Add the tracking link |
| 12/7 | Open on the 26th? | No | - | - | - | Block 0: 26th = closed |
Don't write any visitor's name, number or email in it: a summary of the question is enough.
The sign it's working
After a few weeks, the same mistakes stop coming back, and you find fewer and fewer "no" answers. That's the time to space it out: one review every two weeks, except in December, when the questions change fast.
Your turn
Block 15 minutes in your calendar, every week, on the same day. This week, run the routine on ten conversations (or ten messages you sent yourself) and write down your first fix.
Recommended tool
Flopia, the AI assistant from Flopix
Flopia is in testing. Join the waitlist to hear as soon as it opens.
Premium
Unlock every course of the group Flopia
Every lesson, new courses as soon as they come out, and the community. No commitment.