The first reply decides the conversation
By the time you send your second message, the customer has already decided whether this is going to be easy or a fight. Almost none of that comes from the answer — it comes from how long they waited, whether you repeated their problem back correctly, and whether you promised something you then kept.
Acknowledge before you know
The instinct is to open the order, check the courier, read the notes, and then write. That is the right order for accuracy and the wrong order for the person watching an empty chat window.
Split it. Send something within thirty seconds that proves a human is on it, then go and find out. The acknowledgement costs you eight seconds and buys you five minutes of patience.
One message, four minutes later
“Hi, I've checked and your order #4182 was delivered to the pickup point on Rue de Marseille yesterday at 16:40. You have until Friday to collect it.”
Two messages, same four minutes
“Hi Leila — I'm opening your order now, one moment.”
(four minutes later)
“It was delivered to the pickup point on Rue de Marseille yesterday at 16:40. You have until
Friday to collect it.”
Same facts, same delay, completely different feeling. In the first, the customer spent four minutes wondering whether the chat was even monitored. In the second, they spent four minutes waiting for someone they had already met.
Say the problem back in your own words
One sentence that restates the situation does more for trust than any apology. It proves you read the message rather than pattern-matched it to a category — which is exactly the thing customers suspect when a reply arrives quickly.
Restate, don't repeat. Copying their words back verbatim reads as a script. Putting it in your own words shows comprehension: “So the parcel arrived but the second item is missing from the box — got it.”
It also catches misunderstandings while they are cheap. If you have the wrong end of it, they correct you in ten seconds. Without the restatement, you find out after three messages of answering the wrong question.
Promise a time, not an outcome
“I'll sort this out for you” is a promise you might not be able to keep. “I'll come back to you within ten minutes” is one you control entirely, and it is the one that actually reduces anxiety — because what people find intolerable is not waiting, it is not knowing how long.
Rules that hold up in practice:
- Give a number, never “shortly” or “ASAP”. Those words mean nothing and everyone knows it.
- Pad it. If you think five minutes, say ten. Early is a gift; late is a broken promise.
- Come back at the time even if you have nothing. “Still on it, the warehouse hasn't replied yet — I'll chase again at 15:00” keeps the trust you built.
How to say “I don't know yet”
Uncertainty is not the problem. Hiding it is. What loses the customer is the vague answer that sounds confident and turns out to be wrong — because after that, nothing you say counts.
A workable shape: what you know, what you don't, what you're doing about it, when they'll hear back.
Confident and unfounded
“It should arrive in the next day or two, no problem.”
Honest and specific
“Tracking hasn't moved since Monday, so I don't want to guess a date. I've opened a case with the courier — they answer within one working day. I'll message you here as soon as they do, and if it's lost, we ship a replacement at our cost.”
The second message contains worse news and leaves the customer calmer, because it tells them the floor: whatever happens, they are not out a parcel and their money.
Match their register, not their mood
If they write two clipped lines, do not reply with three paragraphs and an exclamation mark. If they write warmly, warmth back is fine. Mirroring register — length, formality, whether they use emoji — makes the exchange feel like a conversation rather than a service encounter.
Mood is different. When someone is angry, do not mirror the anger and do not counter it with forced cheerfulness, which reads as not listening. Stay level, be concrete, and move quickly to what happens next. Speed and specificity defuse far better than sympathetic adjectives.
Skip the opening ritual
“Thank you for reaching out to us! We appreciate you taking the time to contact our support team.” Nobody has ever been pleased by this. It delays the answer, it costs the customer a screen of scrolling on a phone, and it announces that a process has begun rather than that a person has arrived.
Open with their name and the thing they asked about. The politeness lives in the accuracy.
Close the loop yourself
The last thirty seconds matter almost as much as the first. Before you resolve, do two things: confirm what will happen next in one line, and make it clear the thread stays open to them.
“So: replacement ships tomorrow, tracking lands in your email by the evening. If it doesn't, reply here and it comes straight back to me.” That sentence prevents the follow-up chat where somebody asks whether anything actually happened — which is, on most teams, a surprising share of the queue.
The first sixty seconds, in order
- Reply within thirty seconds, even with nothing but “I'm on it”.
- Restate their problem in your own words so a misunderstanding surfaces now.
- Promise a time you control, padded, and come back at it regardless.
- When you don't know: say what you know, what you don't, and the floor they can count on.
- Skip the greeting ritual. Open with their name and their question.