Five lessons, about an hour. The same complaint means something different depending on where it lands. This module is about reading each channel's actual rules — what speed it demands, what tone it forgives, what leaves a trail and what doesn't — so the same judgement from modules 2 and 3 lands right wherever the customer chose to write.
Email is the one channel where the customer, and sometimes a colleague, a lawyer, or the customer's own future self, might reread exactly what you wrote, days or months later, with no memory of the tone you meant. That changes what "good" looks like here more than on any other channel.
Write every email as if it will be forwarded to someone who wasn't in the conversation.
State the outcome plainly near the top, not buried in paragraph three — a reread skims. Avoid a tone that depends on being heard rather than read; a line that would sound warm spoken aloud can read as curt on a screen with no vocal inflection to soften it. And be precise about commitments, because email is the channel where "I'll look into it" versus "I'll have an answer by Thursday" gets held against you literally, in writing, later.
"Hi! Thanks so much for your patience on this. We've been looking into your order and after checking with our warehouse team we can confirm that we are able to process a refund for you, which should appear in your account within..."
"Hi Funmi — good news: your refund is approved and processing, you'll see it in 3–5 business days. (Details: I checked with the warehouse, the item was confirmed damaged in transit.) Let me know if it's not showing by next Tuesday."
The second version front-loads the outcome, then gives the reasoning for anyone who wants it — including a future reread that only needs the first line to understand what happened.
Take an email reply you've written recently, for this or any context, and rewrite its first two lines so the outcome is stated immediately.
Chat sets an expectation email never does: the customer is watching a "typing..." indicator, in real time, and a long silence reads as being ignored even when you're legitimately checking something. The pressure this creates is exactly what causes chat's most common failure — replies sent fast enough to hit the clock, but sloppy enough to need a second message fixing the first.
Send a holding message the moment you need more than a few seconds — "Checking that for you now, one moment" — rather than going silent while you look something up. This costs nothing and converts a silence that reads as neglect into a wait that reads as being handled. Then take the extra ten seconds to make the actual answer right the first time, because a correction message in chat reads worse than a slightly slower first reply would have.
[40 seconds of nothing] "yes it ships to Kenya" [30 seconds later] "sorry, actually let me double check that, one sec" [correction follows]
"Checking our Kenya shipping zones now, one moment" [45 seconds] "Yes! We ship to Kenya via DHL, 8–12 working days, duties included at checkout."
Lesson 2.4's macro test applies here too, under more time pressure — which is exactly when it's most tempting to paste a saved reply unedited and hope it fits.
Write your default holding message, ready to paste, for the next time you need to look something up mid-chat.
A customer messaging on WhatsApp or Instagram DM is usually writing the way they'd text a friend — lowercase, no punctuation, voice notes, emoji. Matching that register too rigidly the other way, with a formal corporate reply, reads as jarring and cold on a channel built for informality. But informal tone is not the same as no boundaries, and this is where beginners overcorrect.
You can be warm and relaxed in wording while still: confirming order details precisely rather than casually, never promising something you can't verify just because the tone feels friendly, and keeping a record — WhatsApp Business and most DM tools log conversations, but if a customer moves to a personal number, note the key facts somewhere they're not lost when the chat disappears from view.
Customer: "hii do u guys still have the rose clay mask in stock 👀" Reply: "heyy yes we do! 🌸 just added more stock this week, want me to hold one for you while you check out?"
Warm, on-brand, uses emoji the way the customer did — and still confirms a specific, checkable fact (stock, this week) rather than a vague "probably!"
Write a casual, on-brand WhatsApp reply to a stock question, keeping the facts precise.
Every other channel gives you a moment to reread before sending. A live call, and to a lesser extent a voice note, doesn't — the words are out the instant they're said, in a tone the listener actually hears rather than reads. This is where the acknowledge-own-act shape from module 3 needs to already be second nature, because there's no editing pass.
Before answering a call about a known difficult situation, take fifteen seconds to decide your opening line — the acknowledge move from 3.2 — so it's ready rather than improvised under the pressure of a live voice on the other end. And when leaving a voice note yourself, a short pause before speaking and a slower pace than feels natural both compensate for the listener not being able to reread if they miss something the first time.
Tone of voice carries information text doesn't — a customer who sounds tired versus one who sounds sharp with anger may need genuinely different responses even to the same words. Listen for it, not just for the content of what's said.
Say out loud — record yourself if you can — the acknowledge line you'd open with for a customer calling about a late order. Listen back once.
Sometimes the best move isn't a better reply on the current channel — it's moving the conversation somewhere else entirely. A heated public comment thread cools down remarkably fast the moment it moves to a DM, partly because the audience disappears and partly because switching channels itself signals "I'm taking this seriously enough to handle it properly."
Move to a slower, more permanent channel (email) when a commitment needs a written record. Move to a faster, more personal one (a call) when text has gone back and forth twice without landing and a real-time conversation would resolve it in two minutes. And move to a private one whenever the current channel is public. Always name the switch explicitly rather than just going quiet on the original thread — "I'm going to email you directly so we have this in writing" tells the customer what's happening and why.
Write the one-line message you'd use to move a public complaint to a private channel, naming the switch plainly.
The same underlying complaint — a delayed order — arrives from the same customer on four channels within one afternoon: an email, a live chat message, a WhatsApp text, and a comment on a public post. Reply to each appropriately without contradicting yourself across channels.
Whether the same judgement holds its shape across very different registers under real time pressure — not whether you know five sets of rules in the abstract.
You should now have: an email shape built for a reread, a chat holding-message habit, a sense of WhatsApp's tone-without-vagueness balance, prepared openings for calls, and a channel-switch script. Module 5 turns to the judgement behind the reply itself — refunds, returns, and reading a policy the way it's meant to be read.