Delivery Shock, Size Doubt and the Empty Basket: Seven Chat Scripts for UK Checkout Recovery
Photo by Photo by SumUp on Unsplash on Unsplash
A shopper leaves your checkout for reasons that feel enormous to them and entirely guessable to you. Postage costs four quid more than they expected. The size guide is written in a language they do not trust. The guest checkout button is missing. And nobody asks them anything, so they close the tab and buy elsewhere.
Live chat will not fix a broken checkout. It will, however, catch the doubt in the thirty seconds before the doubt becomes a decision — provided your opener sounds like a person rather than a pop-up.
Why the exit is rarely about the price of the item
British shoppers are famously reluctant to complain, and equally reluctant to ask a question that makes them feel foolish. That is why 'do you have this in a 12?' gets typed and deleted four times before the tab closes. A chat that opens with the right question removes the effort of asking.
The golden rule for every script below: name the hesitation before the customer has to. Do it once, do it gently, and never repeat it.
Script 1 — Delivery cost shock
The moment: they reach the delivery step, see £4.95, and go quiet for more than ninety seconds.
Before: "Hi! How can I help you today?"
After: "You're on the delivery step — the £4.95 is tracked 48-hour, and it drops to free over £50. Want me to show you anything near that?"
Why it lands: it answers the question they were too polite to ask, and it offers a route rather than a discount.
Script 2 — Size uncertainty
The moment: two sizes added to basket, one removed, page revisited, then nothing.
Before: "Need any help?"
After: "Between sizes? Our returns are free and the 12 fits like a generous 12 — if you're usually a 12 in other brands, stick with it."
Why it lands: it gives a specific recommendation instead of a size chart link. Be honest: if the answer is 'size up', say so. Recovery today, returns cost tomorrow.
Script 3 — The guest checkout stall
The moment: they hover on the account-creation prompt and either bounce or sit there.
After: "You can check out as a guest — the account is optional. Takes about forty seconds either way."
Why it lands: mandatory registration is one of the most quietly expensive decisions in UK e-commerce. If yours is compulsory, at least have an agent explain why.
Script 4 — Card declined and payment wobble
The moment: a failed payment attempt, or a long pause on the card fields.
After: "Sometimes declines are just the bank being cautious with a new retailer — a different card or PayPal usually sorts it. Nothing's been charged."
Why it lands: it removes the fear that they have already been billed twice, which is the actual reason many people abandon rather than retry.
Script 5 — The 'just looking' opener
The moment: three or more product pages, 90 seconds on a category page, no basket activity.
After: "Just browsing, or after something specific? Happy to narrow it down if it helps."
Why it lands: it explicitly gives permission to be left alone. Counter-intuitively, that permission is what gets a reply — and roughly half of replies turn into a product question.
Script 6 — Discount hunting
The moment: an idle cart, a returning visitor, or a search for 'discount code'.
After: "No secret codes knocking about, I'm afraid — we do free delivery over £50 though, which is the honest version of a discount."
Why it lands: it is disarming. A cheerful 'no' beats a scripted 'let me check with my manager' that never resolves. If you do have a welcome offer, say so here and nowhere earlier.
Script 7 — The post-abandon nudge
The moment: basket abandoned 45 minutes ago, chat widget unavailable, email or SMS open.
After: "Left something in your basket — still in stock, still free delivery over £50. If it was the sizing, reply here and I'll help you pick."
Why it lands: it guesses the obstacle rather than nagging about the basket. One nudge, one question, no countdown timers.
| Abandonment moment | Script | Metric to watch |
|---|---|---|
| Delivery cost shock | 1 | Checkout completion rate |
| Size doubt | 2 | Return rate alongside conversion |
| Guest checkout friction | 3 | Cart-to-order rate |
| Payment failure | 4 | Retry success rate |
| Browse-only session | 5 | Chat-to-basket rate |
| Discount hunting | 6 | Margin per recovered order |
| Post-abandon | 7 | Recovered revenue |
Testing this without a data team
Change one thing at a time. Run each script for two weeks or a hundred conversations, whichever comes first, and compare against a control group where the widget fires the old generic opener. Track recovered baskets, not chat volume — an agent can double their conversations and halve their value.
Keep a shared doc of what got ignored. A script that dies silently is telling you the trigger was wrong, not the words.
A note on tone for UK shoppers
Skip the exclamation marks. Avoid 'awesome', 'reach out' and anything that sounds like a Californian call centre. Say 'no worries', 'happy to help', 'that's a fair question'. Apologise once, then solve the problem. And never, under any circumstances, open with 'I'm your personal shopping assistant today'.
Before peak lands
If you are running these scripts for the first time in November, test them on a Tuesday afternoon in low traffic first. The scripts that survive a quiet weekday are the ones worth switching on when the queue triples — and by then, the wording will already sound like you.
