Chapter 1 · The resource
The handoff summary, so the customer repeats nothing
Follow this course in your space: your progress is saved, and the community answers your questions.
Follow for freeThe customer explained their problem to your assistant. They gave their address, described the issue, mentioned when they're available. Then you call them back, and your first sentence is: "So, what's going on?" Back to square one. As far as they're concerned, the assistant was useless.
The handoff summary fixes that. It's a short note the assistant prepares at the moment of handoff, and you read it before replying. With it, your first sentence becomes: "Hi Mrs. Martin, this is Mike, I'm calling about the leak under your sink."
The five sections
A good summary answers five questions, always in the same order.
- Who: first name, last name if given, the preferred way to get back in touch.
- What: the request in one sentence, in the customer's words if needed.
- What's already been said: the information the assistant gave, so you don't contradict it.
- What's expected: what the customer wants to get, and what triggered the handoff.
- How to follow up: the channel, the preferred time, and the response time announced to the customer.
The template to copy
HANDOFF SUMMARY
Who: [first and last name] · [phone or email] · prefers [text / call / email]
What: [the request in one sentence]
Details given: [location, date, order number, photo attached...]
Already said by the assistant: [information given, choices offered]
What's expected: [what the customer wants]
Handoff trigger: [asked for a human / 2 misses / complaint /
refund / emergency / strong emotion / outside info]
Mood: [calm / in a hurry / unhappy / worried]
Follow-up: [preferred time] · response time announced: [response time]
The "Mood" line is optional but valuable: knowing a customer is unhappy before you pick up changes your opening line.
The instruction for your assistant
HANDOFF SUMMARY
Every time you hand off, you write a summary using the template below.
You make nothing up: if a piece of information is missing, you write
"not specified."
You use the customer's exact words for the request when they matter
(a symptom, a reference number, a date).
You note what you've already answered, so [your name] doesn't
contradict you.
You never copy health information, banking details or a password
the person may have typed: you only note "sensitive information
given, ask again in person if needed."
Before sending the handoff, you tell the customer:
"I'm passing on your request with everything you've already told me,
so you won't have to repeat anything."
That last sentence matters. It reassures the customer on the point that annoys them most.
Three filled-in examples
Plumber
Who: Mrs. Martin · (555) ...-.... · prefers a call
What: leak under the kitchen sink, "it's dripping nonstop"
Details given: Columbus, third-floor apartment, shutoff valve closed
Already said by the assistant: no service on Sundays, callback Monday morning
What's expected: a quick repair
Trigger: emergency
Mood: worried
Follow-up: Monday before 10 a.m. · response time announced: Monday morning
Vacation rental
Who: Thomas · thomas@... · prefers text
What: booked stay, can't find the lockbox
Details given: arrived on site at 6:40 p.m., booking under Durand
Already said by the assistant: location described in the welcome guide
What's expected: to get into the rental
Trigger: emergency (guest on site)
Mood: in a hurry
Follow-up: right now · response time announced: within the hour
Photographer
Who: Leah · leah@... · prefers email
What: wants a photo from her wedding removed from the website
Details given: wedding on June 14, photo on the "Weddings" page
Already said by the assistant: request passed on, no decision by the assistant
What's expected: removal of the photo
Trigger: outside info
Mood: calm
Follow-up: by email · response time announced: within two business days
How long to keep summaries
Summaries contain personal data. In France, the CNIL's chatbot guidance (2021) gives a reference point: keep data only as long as needed for the purpose it was collected for. In practice:
- A handoff that's handled and closed: the summary can be deleted, or filed in your customer record if you keep one
- A complaint in progress: keep it while you handle it
- Your privacy policy says how long you keep these exchanges
Common mistakes
- A summary that's too long: if you have to reread the whole conversation, the summary didn't do its job.
- A summary that interprets: "the customer seems to be acting in bad faith." The assistant describes, it doesn't judge.
- Forgetting the announced response time: you risk calling back later than promised.
- Not reading the summary before calling. Thirty seconds of reading saves you from the sentence that sets people off.
Your turn
- Copy the summary template and the instruction into your assistant's settings.
- Run three test conversations: an emergency, a complaint, a question outside its information.
- Read the three summaries it produces. For each one, ask yourself: "Could I call this customer back without asking a single question?" If not, add the missing section to the instruction.
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.