Customer Service Skills for Any Role: Writing Helpful Responses in Email and Chat

Why asynchronous writing matters

Email and chat are “asynchronous” channels: the other person may read hours later, on a phone, and without context. Helpful writing reduces back-and-forth by making the request, action, and next steps unmistakable on the first read. Your goal is not to write more—it’s to write so clearly that the customer can act immediately or confidently wait for the next update.

A repeatable structure for helpful email and chat

1) Subject lines that sort, search, and set context (email)

A strong subject line helps the customer (and your team) find the thread later and understand what it’s about without opening it. Use a simple formula:

• [Topic] + [Identifier] + [Action/Status]
• Keep it under ~60 characters when possible.
• Avoid vague subjects like “Question” or “Update.”

Examples

• Invoice #10482 — Request to change billing address
• Account access — Reset link not working (Case 39127)
• Order 77821 — Replacement shipped (tracking inside)

When to change the subject: If the topic changes materially, start a new thread (or update the subject with “New topic:” and reference the prior case/order).

2) Opening lines that restate the request

Start by confirming what you understood and what you’re going to do. This prevents misalignment and reduces clarification loops.

Continue in our app.

You can listen to the audiobook with the screen off, receive a free certificate for this course, and also have access to 5,000 other free online courses.

Or continue reading below...

Download the app

• One sentence restating the request in the customer’s words (no jargon).
• One sentence stating the immediate outcome or what you’re doing next.

Examples

• Thanks for reaching out—you're looking to update the shipping address for Order 77821. I can help with that; please confirm the new address below.
• I understand the reset link is expiring before you can use it. I’m going to send a fresh link and a quick checklist to make sure it works.

3) Step-by-step instructions that customers can follow

When you need the customer to do something, write instructions like a mini-procedure. Make it scannable and testable.

Step-by-step checklist

• Lead with the goal: “To update your password…”
• Number the steps (1, 2, 3) for anything more than one action.
• One action per step; keep steps short.
• Use exact labels the customer will see (button names, menu items).
• Include expected result after key steps (“You should see…”).
• Include a fallback if a step fails (“If you don’t see…, try…”).

Example: instructions in email/chat

1. Go to Settings → Security.
2. Select Change password.
3. Enter your current password, then your new password twice.
4. Select Save. You should see “Password updated.”

If you don’t see Security, tell me whether you’re using the mobile app or the web version and I’ll send the right steps.

4) Hyperlinks and attachments etiquette

Links and files are useful, but they can also create friction (security concerns, blocked attachments, broken links). Make them easy and safe to use.

Hyperlinks: best practices

• Describe the link (don’t paste a bare URL only). Example: Download your invoice (PDF).
• Use one link per action when possible; avoid link overload.
• Tell them what they’ll see: “This opens a secure page to confirm your address.”
• Prefer direct links to the exact page, not a homepage.
• Check access: if login is required, say so.

Attachments: best practices

• Name files clearly: Order-77821-Return-Label.pdf.
• State file type and size: “PDF, 240 KB.”
• Summarize what’s inside so they know why to open it.
• Offer an alternative if attachments are blocked: “If you can’t open PDFs, tell me and I’ll paste the text here.”
• Be careful with sensitive data: only request or send what’s necessary; use approved secure methods when needed.

5) Closing lines that confirm outcome and next steps

End with a clear “what happens now” so the customer doesn’t wonder whether they need to reply.

• Confirm the current status: what’s done vs. in progress.
• Specify the next step and who owns it (you or the customer).
• Give a time cue if relevant: “by 3 PM,” “within 1 business day.”
• Invite a specific reply: ask for exactly what you need, or confirm no reply is needed.

Examples

• I’ve updated the billing address on Invoice #10482. No further action is needed—your next invoice will reflect the change.
• Once you confirm the new shipping address, I’ll apply it and reply with confirmation.

Templates for common situations

Use these as starting points. Replace bracketed text with your details and keep the structure consistent to maintain a recognizable brand voice.

Template 1: Request received (acknowledgment)

Subject: [Topic] — Received your request ([Case/Order #])  Hi [Name],  Thanks for your message. You’re asking about [restate request in one sentence].  Here’s what I’m doing next: [action you will take].  Timing: You can expect my next update by [time/date].  If you have it handy, please reply with [one key detail], which will help me move faster.  Thanks,  [Name]

Template 2: Need more information (targeted questions)

Subject: [Topic] — Need a couple details to proceed ([Case #])  Hi [Name],  To help with [restate request], I need two quick details:  1) [Question 1 — include example format]  2) [Question 2 — include example format]  Once I have those, I’ll [what you will do] and reply with the result.  Thanks,  [Name]

Tip: Keep questions “answerable” by allowing copy/paste responses (IDs, dates, screenshots if appropriate) and avoid asking for information you don’t truly need.

Template 3: Delay update (proactive status)

Subject: [Topic] — Update on timing ([Case/Order #])  Hi [Name],  Quick update on [restate request]. We’re still working on it because [brief reason in plain language].  New expected timing: [date/time or range].  In the meantime, you can [workaround/alternative if available]. If that doesn’t work for you, reply with [preference/constraint] and I’ll adjust the plan.  Thanks,  [Name]

Template 4: Resolution summary (what was done + verification)

Subject: [Topic] — Resolved ([Case/Order #])  Hi [Name],  This is now resolved. Here’s what I did:  - [Action 1]  - [Action 2]  What you should see now: [expected result].  If you have a moment, please try [one verification step]. If anything looks off, reply to this message and include [specific detail to speed up follow-up].  Thanks,  [Name]

Template 5: Refusal with alternatives (can’t do X, can do Y)

Subject: [Topic] — Options for next steps ([Case/Order #])  Hi [Name],  I’m not able to [requested action] because [brief reason tied to policy/technical limitation].  Here are the best alternatives:  Option A: [alternative + benefit + how to do it]  Option B: [alternative + benefit + how to do it]  If you tell me which option you prefer (A or B), I’ll take the next step on my side.  Thanks,  [Name]

Note: Keep the refusal factual and short; spend more words on what you can do next.

Message quality checklist (before you hit send)

Exercises: rewrite for brevity, warmth, and consistent voice

Exercise 1: Make the subject line specific

Original: Update

Rewrite (include topic + identifier + status):

• ________________________________________

Exercise 2: Restate the request in one sentence

Original: We received your email and will look into it.

Rewrite (what they asked + what you’ll do next):

• ________________________________________

Exercise 3: Turn a paragraph into numbered steps

Original: To fix this, go to settings and then security and update your password. If it doesn’t work, try again later or reinstall the app.

Rewrite (numbered, one action per step, include expected result):

1. ________________________________________
2. ________________________________________
3. ________________________________________

If you don’t see ________, then ________.

Exercise 4: Ask for more info without sounding demanding

Original: You didn’t give enough information. Send the details.

Rewrite (two targeted questions + why you need them):

• ________________________________________

Exercise 5: Delay update that reduces “any news?” follow-ups

Original: We’re still working on it.

Rewrite (reason + new timing + what customer can do meanwhile):

• ________________________________________

Exercise 6: Resolution summary that prevents reopening

Original: It should be fixed now.

Rewrite (what you did + what they should see + one verification step):

• ________________________________________

Exercise 7: Refusal with alternatives

Original: No, we can’t do that.

Rewrite (brief reason + two options + ask them to choose):

• ________________________________________

Exercise 8: Brand voice consistency (same message, three tones)

Rewrite the message below in your organization’s preferred voice. Keep the facts identical; change only phrasing.

Base message: I can’t change the plan mid-cycle. I can switch it on the renewal date. Tell me which plan you want.

• Version A (more formal): ________________________________________
• Version B (more friendly): ________________________________________
• Version C (more concise): ________________________________________

Exercise 9: Remove friction words

Rewrite to remove or replace words that can sound blaming or bureaucratic (e.g., “obviously,” “you failed,” “as per policy,” “must,” “should have”).

Original: As per policy, you must provide the correct information or we cannot proceed.

Rewrite: ________________________________________