45 Live Chat Scripts, Organised by the Moment That Goes Wrong

Every list ranking for this query groups scripts the same way: greetings, sales, support, closing. That is how email is organised, and chat is not email.

Chat goes wrong at specific mechanical moments — the silence while you look something up, the transfer, the conversation that will not end. These are grouped by those.

One rule before any of them

Chat messages must be short enough to read in one glance. A six-line paragraph pasted into a chat window reads as a wall and gets skimmed; the same text in an email reads as thorough.

Two lines is the working maximum. If an answer needs more, send it as two or three separate messages a second apart — it reads as a person thinking rather than a macro firing. Everything below is written to that constraint.

Opening (5)

The proactive ones matter more than they look. A proactive chat that opens with can I help you today is ignored; one that names what the person is doing gets a reply, because it demonstrates the window is attached to something.

The silence (6)

The single most common failure in live chat. You go to look something up, thirty seconds pass, and the customer cannot tell whether you left. Nothing in the interface distinguishes checking from gone.

Naming a duration is what makes these work. About a minute sets a clock the customer can hold you to, and breaking it with an update at sixty seconds costs you nothing. Silence is what makes people close the window.

Asking for things (5)

The last one is not optional. Chat transcripts are stored, searchable and frequently visible to more people than anyone assumes, and a customer will paste a full card number if you do not stop them first.

Not knowing (4)

• "I don't know — let me find out rather than guess." Says the quiet part and buys real credit.
• "That's outside what I can see from here. [Team] handles it and I'm bringing them in."
• "I want to check before I answer, because I've seen this go both ways."
• "Honest answer: I'm not sure that's supported. Give me two minutes to confirm before you plan around it."

Confident wrong answers cost more in chat than anywhere else, because the customer acts on them immediately. The window is open, they are at the keyboard, and by the time you correct it they have already done the thing.

Transfers and escalation (6)

They'll have the whole conversation is the line that does the work, and only if it is true. Making someone re-explain after a transfer is the single most reliable way to turn an inconvenience into a complaint.

When they are annoyed (5)

• "That's a fair thing to be annoyed about. Here's where it actually stands."
• "You're right that this shouldn't have happened. I can't undo it — here's what I can do."
• "I'm not going to tell you it's fine. Let me tell you what I'm doing about it."
• "Three days without a reply isn't acceptable. I have it now and I'm not passing it on."
• "I'd be annoyed too. Give me five minutes to get you a real answer rather than an apology."

None of these begin with I understand how you feel. In chat that phrase arrives instantly, which makes it read as automated, and a customer who has been on hold twice this week recognises it as the thing that comes before nothing happening.

Saying no (5)

Say the no first. Chat rewards front-loading — a customer reading three lines of context before the refusal will skim to the end anyway, and the delay reads as evasion rather than care.

Ending (5)

The four scripts to delete

These appear on most ranking lists for this query and all four do damage.

Where these go once you have AI

Chat is the channel automation reaches first, and the openings, the lookups and the routine noes are exactly what an AI layer will take. The silence scripts stop mattering — a machine does not go quiet to check something.

What stays human is the annoyed section, the second transfer, and every no where the reason is that you got it wrong. Those are the ones worth rehearsing, and they are the ones every ranking list treats as an afterthought.

Written to be used rather than read. Square brackets are the only things to replace. The grouping by chat mechanics is our own — we have not found another list organised this way, which is the reason this page exists.

WRITTEN BY AR · UPDATED 2026-08-04

I read the fine print. Vendor pricing pages, billing definitions, terms, funding filings and acquisition notices — then I do the arithmetic nobody publishes: what a platform actually costs at your volume, what its headline metric is really counting, and who owns it now. I do not run benchmarks, and no page here pretends otherwise.

How we work · About the author