The close carries more weight than its length suggests
Most training attention goes to the opening: the greeting, the acknowledgement, the first
useful sentence. The close gets almost none, which is odd, because it is the part the customer
carries away. A conversation that solved the problem but ended abruptly is remembered as
unsatisfying, and a satisfaction score given a minute after the chat is largely a verdict on the
final exchange.
Endings are also where the operational damage happens. An unconfirmed close leaves the
customer unsure whether anything is going to happen, which produces the follow-up chat tomorrow
asking exactly that — volume you generated yourself.
Confirm the outcome, do not assume it
The single most common closing mistake is treating the delivery of an answer as the end of the
conversation. The agent has finished; the customer may not have. Closing well means checking,
explicitly, that the thing they came for actually happened.
A close that holds up has four parts, and it fits in two lines:
- State what was done or decided. “I have refunded the 12.99 to the card ending 4402.” Concrete, with the details they will look for.
- Say what happens next and when. “It will show in your account within three working days.” Unstated timelines become complaints.
- Check nothing is outstanding. “Is there anything else on this order I can sort out while I have it open?”
- Leave a route back. “If it has not appeared by Friday, reply here and I will chase it.”
That fourth element does more work than it appears to. Telling someone how to come back reduces
anxiety about the close, and anxious customers are the ones who reopen conversations
unnecessarily.
Closing when the issue is not resolved
Plenty of chats end without a resolution — something needs investigating, another team
must act, a part is on order. These endings are harder and matter more, because the customer is
being asked to accept an unfinished state.
Three things make an unresolved close acceptable: name the specific next step, name who owns
it, and give a real time. Vagueness in any of the three converts a reasonable wait into a
grievance.
“I have not been able to fix this myself, so I have passed it to the billing team
with everything you have told me. They work Monday to Friday and will email you by Wednesday. If
you have not heard by then, come back to me here and I will chase it personally.”
Compare with “I have escalated this, someone will be in touch.” Same facts, no
commitment, and no way for the customer to know when to worry. The first version also creates
accountability for the agent, which is the point — a promise nobody recorded is a promise
nobody keeps.
The chats that never really end
A large share of chats do not get closed at all; they trail off. The customer stops replying,
the window sits open, and eventually something times out. This looks harmless and quietly
distorts everything: workload figures are inflated by phantom open chats, and the customer may
have left with an unanswered question.
Handle the silence deliberately rather than waiting it out.
- Check in once after a reasonable gap, with something useful rather than “are you still there?” — a summary of where things stand is better.
- Say what you are going to do if there is no reply: “I will leave this here for now, and if you come back the history will still be with me.”
- Close it properly, with a short summary of what was covered and anything outstanding, so the record is useful if they return.
Distinguish this from the genuinely busy customer who is mid-task on your instructions. Closing
a chat on someone who is three minutes into checking their router is a small betrayal that reads
as impatience.
Do not ask for a rating in a way that begs
Where a satisfaction survey is offered at the close, keep it brief and neutral. Explaining how
much the score matters, or hinting at what a good one looks like, distorts the feedback and
reads badly. The rating is more useful when it is honest than when it is high.
Equally, do not ask for a rating on a conversation that ended unresolved. It invites a poor
score for a process failure the agent handled correctly, and teams learn to close prematurely to
avoid it.
Match the sign-off to the conversation
Closing warmth should be proportionate. A cheerful “Have a wonderful day!” on a
chat about a lost order reads as tone-deaf; a curt “Resolved.” on a friendly
pre-sales conversation reads as cold. The safe general shape is a brief thanks, the route back,
and a plain sign-off — then stop. Long farewells make the customer feel obliged to reply,
which keeps the chat open past its natural end.
What to measure
Two numbers say whether closes are working. Track reopened or repeat contacts within a few
days on the same issue — a rising number usually means closes are being declared, not
confirmed. And track how many chats end with an explicit agent close versus timing out; a high
timeout share is a coaching opportunity hiding in the reports.
Then read some endings. Sample the last three messages of a handful of chats a week and ask a
simple question of each: would the customer know what happens next? That single check finds more
closing problems than any dashboard.