1.5Customer relations by email & chat
The essentials in 30 seconds
- Email: precise subject, hello + name, point-by-point answer, action + deadline, full signature — acknowledge within 24h.
- Chat: answer within a minute, short messages, announced searches, summary + transcript before closing.
- Reflex: re-read aloud, never an untenable promise (writing stays); when tense: draft + pause, or phone.
Threaded mini-case — Rania answers in writing
Same agency in Algiers: Rania handles a tense email received at 6pm and a live chat. Email: precise subject (“Order #4521: incomplete delivery received, solution Thursday”), hello + name, 3 points (acknowledged, action, date), full signature. Chat: answer within a minute, short bubbles, “I'm checking, 1 minute”, summary before closing. Final episode of the thread.
Final episode of cases 1.1–1.4 — welcome and listening in writing.
1. Email: subject, structure, lead time
Precise subject ("Your order #4521: Thursday delivery"), hello + name, point-by-point answer, action + lead time ("I'll get back to you Thursday 10 a.m."), full signature (name, role, phone). Acknowledge within 24h even without a solution: silence worries more than waiting.
2. Chat: fast, short, human
Answer in under a minute, short messages (one idea per bubble), announce research ("checking, 1 minute"), summarise before closing + transcript sent. Multitask chat (3-4 conversations) demands canned responses (L2) without cold copy-paste.
3. Costly mistakes: tone and evidence
Re-read aloud (curtness can be heard), no CAPITALS (= shouting), named attachments, never an untenable written promise (writing stays). When tense: draft + pause + re-read before sending — or switch to phone.
🔎 Concrete example — 🔎 Hands-on example — An email that closes instead of inflaming
Objet : Commande #4521 : incomplet reçu, solution jeudi Bonjour M. Karim, 1. Oui : 2 colis manquants constatés, je suis désolée. 2. Action : réexpédition demain, suivie par mes soins. 3. Je vous confirme jeudi 10 h par SMS. Lina — Service client — 05 50 00 00Takeaway: acknowledged, actioned, dated, signed.
Lesson: point-by-point proves you read everything.
Section vocabulary
- Written customer relations
- Interactions by email, chat or messaging, with no voice or body language to shade tone.
Simple example: The email and chat handled by Rania at the agency.
What it is not: a call where voice carries the emotion.
Reflex: offset the missing voice with a warm tone.
- Structured answer
- A clear, easy-to-read message (paragraphs, points) fully answering the request.
Simple example: Precise subject + 3 numbered points + deadline in Rania's email.
What it is not: a confusing block forgetting half the request.
Reflex: answer everything, point by point.
- Response time
- Time taken to answer, a major satisfaction criterion in writing (answer fast or acknowledge).
Simple example: Rania's acknowledgment within 24h even with no solution; chat within a minute.
What it is not: 5 days of silence without a word.
Reflex: fast or acknowledged — never silence.
- Chat
- Real-time written channel, conversational: short messages, responsiveness, slightly lighter tone.
Simple example: Rania: short bubbles, “I'm checking, 1 minute”, summary before closing.
What it is not: a novel in one message after 10 minutes of silence.
Reflex: short, fast, human — without sloppiness.
- Re-reading
- Checking tone, clarity and spelling before sending (writing stays and can be shared).
Simple example: Rania re-reads her tense email aloud after a pause.
What it is not: sending while hot with no re-read when tense.
Reflex: draft + pause + re-read, or phone.
In practice — Hands-on - Succeed at written customer relations (email, chat)
- Write clear, structured, complete answers (answer everything so customers need not chase).
- Mind politeness (opening, closing), avoid jargon and compensate for the lack of voice with a warm, positive tone.
- In email: personalise, answer point by point, offer a clear solution (steps, lead times); answer fast or acknowledge receipt.
- Systematically re-read before sending (tone, clarity, mistakes) — writing stays and can be shared.
Ready-to-say script — moving tense writing to the phone (30 s)
“Hello Mr Karim, thanks for your message — I read it point by point. To settle this fast with no misunderstanding, may I call you for 2 minutes? Otherwise I'll answer in writing tonight with the action and deadline.”
Adapt by email or chat: acknowledge, offer the call, promise a dated written answer if declined.
Copy-paste template — email that closes
SUBJECT: _______________ : _______________ + _______________ (precise, not “hello”)
HELLO + NAME: “Hello Mr _______________,”
1. ACKNOWLEDGED: _______________ (yes: fact noted)
2. ACTION: _______________ (what I'm doing)
3. DEADLINE: “I'll confirm _______________ at _______________”
SIGNATURE: Name — Role — PhoneFormal email
Precise subject, polished politeness, full point-by-point answer in one send, full signature.
SME in Algiers
Rania acknowledges within 24h even with no solution, names attachments, only promises the tenable in writing.
Live chat
Within a minute, one idea per bubble, announced searches, summary + transcript before closing.
Tense message
Draft + pause + aloud re-read — or switch to phone rather than answering while hot.
✓ Best practices
- Acknowledge in 24h even without a solution.
- Point by point + lead time.
- Re-read aloud.
✗ Common pitfalls
- No subject ("hello").
- Silence for 5 days.
- Hasty answer when tense.
Key takeaways
- In writing, no voice or body to nuance: a badly worded message quickly seems curt or ambiguous.
- Golden rule: clarity, politeness, effectiveness; structured, complete answer, no jargon or mistakes.
- Response time is a major criterion: answer fast, or acknowledge receipt if it takes time.
- Re-read before sending (tone, clarity, spelling): writing stays and can be shared.
48h Challenge — apply tomorrow
Rewrite 1 real email with the template (precise subject, point by point, deadline, signature), re-read aloud and send. Compare with the original.
- I can structure an email (subject, points, deadline, signature).
- I can handle chat (fast, short, summary before closing).
- I did the 48h challenge or scheduled its date.
Frequently asked questions
Why can an email seem cold or curt when you don't mean it?
Because in writing, everything that nuances an oral message is missing: tone of voice, smile, body language, intonation. A sentence you would say warmly and casually can, written "raw", seem curt, distant or even aggressive — readers project the tone they imagine, often more negative than intended. For example, a short factual answer ("Your order will be delivered Thursday.") that you judge effective may be felt as hasty and impersonal. It is a classic writing trap, amplified by speed (we write fast, without re-reading). To compensate for this lack of voice, you must take particular care of tone and form: add warm politeness formulas (opening, closing), personalise (customer name, reference to their request — to show you address them), use positive language, explain and thank, avoid overly abrupt phrasing. A sentence like "Hello Mrs X, with pleasure: your order will be delivered Thursday. Don't hesitate if you have any questions, have a nice day!" says the same thing but warms the message completely. The rule: in writing, you must consciously inject the warmth voice would naturally bring orally, and always re-read asking "how will this be perceived?". Writing stays, is re-read cold, and can even be shared — hence the importance of irreproachable tone. What seems neutral to you may seem cold to customers: when in doubt, warm it up.
Should you answer differently in chat than in email?
Yes, because they are two written channels with different codes, even if they share fundamentals (clarity, politeness, accuracy). Email is asynchronous and often used for more detailed requests or those needing a formal record: favour a complete, structured answer (answering all points at once, to avoid back-and-forth), more formal politeness (careful opening and closing formulas), and the response time (reasonable) is a key criterion. Chat is synchronous (real-time) and conversational: favour short messages, strong responsiveness (customers wait live — prolonged silences are badly received), and a slightly lighter, more direct tone (without slipping into lax or over-familiar abbreviations — stay professional). In chat, you can split the exchange into several small messages, ask a question and wait for the answer, advance step by step — while in email you structure a fuller answer in a single send. Chat tolerates (and even expects) a brisker pace and a more conversational style; email demands more formality and exhaustiveness. In both cases, the basic principles remain: clarity, no mistakes, warm tone, answering the real request. It is about adapting form to the channel (as for all channels, section 0.4) while keeping the same quality standard and the same service spirit. Good customer-relations professionals know how to modulate their written style between formal email and instant chat.
Tense email received at 6pm. Rania's reflex?