LearnAI home

During ยท Lesson 4

How to Answer Customer Questions Faster

Quick, accurate replies that still sound like a person wrote them.

Fast is only half the job

If you work in support, you are measured on two things that pull in opposite directions: how quickly you reply and how often the customer comes back because your reply did not actually help.

AI can make you dramatically faster. It can also make you dramatically faster at sending confident, well-written, completely wrong answers, which is the worst possible outcome because the customer believes you.

The whole trick is to stop asking AI what the answer is and start asking it to write up an answer you already have.

In plain English

Knowledge base:
Your company's written record of how things work. Help articles, internal docs, the policy page nobody updated.
Ticket:
One customer issue, tracked from the first message to the moment it is resolved.
Macro:
A saved reply your helpdesk can insert with one click. Fast, and usually the reason support email sounds robotic.
Escalation:
Passing an issue to someone with more authority or more information than you.

Draft from your own words, never from its memory

This is the single most important habit in the lesson. An AI assistant does not know your refund policy, your delivery times or whether your product supports single sign-on. If you ask, it will make something plausible up, because plausible is what it does.

So paste the source in.

Prompt you can copy: reply from your knowledge base

Below is a customer message, then the relevant section of our help documentation. Write a reply using ONLY the information in the documentation.

If the documentation does not answer part of their question, say so explicitly at the end under the heading GAPS instead of guessing. Warm, clear, under 150 words. No corporate padding.

CUSTOMER MESSAGE: [paste it, with their name and account number removed]

OUR DOCUMENTATION: [paste the relevant help article or policy]

The GAPS heading is your safety net. It turns the moment where AI would normally invent something into a visible flag telling you which bit you need to go and find out.

Never let an AI tool state a price, a delivery date, a refund window or a technical capability that you have not read with your own eyes in your own documentation. Those four are where support replies go badly wrong, and the customer will quote you back to you.

The angry customer

Someone is furious, possibly rightly. Your first draft will be defensive, because you are a human being and they just insulted your company in three paragraphs.

This is where AI genuinely helps, not because it writes better than you, but because it is not annoyed.

Prompt you can copy: reply to an angry customer

A customer is angry. Write a reply that:

  • acknowledges the specific thing that went wrong, not a generic sorry
  • does not blame them, our supplier, or the system
  • states exactly what we are doing and by when
  • offers one clear next step

Calm, human, under 120 words. No defensiveness. No over-apologising either, one apology is enough. Do not promise anything not listed below.

THEIR MESSAGE: [paste it, identifiers removed]

WHAT WE CAN ACTUALLY DO: [the refund, the fix, the date]

Then read it back as if you were the customer having the worst morning of your week. If any sentence would make you angrier, cut it. Usually it is the one starting with unfortunately.

Checkpoint

Paste your documentation in and ask for a reply built only from it, with anything missing flagged as a gap rather than invented.

Saying no politely

Half of support is telling people they cannot have what they want. Refunds outside the window, features that do not exist, exceptions you are not allowed to make.

The bad version buries the no in so much softening that the customer replies asking whether that was a yes. The good version is clear early, kind throughout, and offers whatever you can actually offer instead.

Prompt you can copy: a clear, kind no

Write a reply telling a customer we cannot do [the thing]. The real reason is [reason]. What we CAN offer instead is [alternative], or nothing if there is genuinely no alternative.

Rules:

  • Say no in the first three lines. Do not bury it.
  • Give the reason once, plainly, without hiding behind policy language
  • Do not apologise more than once
  • Offer the alternative, or acknowledge honestly that there is not one
  • Under 110 words, warm but not falsely cheerful

Ban the phrase unfortunately at this time from your support writing. It signals a corporate no is coming and customers have learned to stop reading at the word unfortunately.

Knowing when to stop typing and pick up the phone

AI makes writing so frictionless that you can end up in a nine-message thread that a two-minute call would have ended on message two.

Stop typing and call when: the thread is past four messages and nobody is converging, the customer is upset enough that tone is being misread in both directions, money or a cancellation is on the table, or you need to ask something you cannot phrase in writing without it sounding like an accusation.

Also call when you have written the same reply three times and it still feels wrong. That is not a writing problem. That is a sign the conversation needs a different channel.

A useful test before you send message five: could I say this whole thing out loud in ninety seconds? If yes, and the customer is reachable, the call is faster for both of you and considerably harder to misread.

Keeping it sounding like a person

Support replies drift towards beige faster than any other kind of writing, because the same twelve situations come up every day. The fix is the same as everywhere else: give it examples of your own good replies and ask it to match them. Three saved replies you were proud of will do more for your tone than any instruction about being friendly and professional.

And read every word before you send. You are the one whose name is at the bottom.

๐Ÿ“ Quiz

Question 1 of 4

What should you do instead of asking an AI tool what your refund policy is?

Found this useful? Pass it on.