Home  /  Resources  /  Retail case study
Retail · E-commerce

The peak-season queue that stopped growing

A mid-market home & lifestyle retailer had tried temps, macros and a buried “contact us” link. The queue grew anyway. Here’s what changed when the returns flow started resolving itself.

It started, as these things do, on a Friday in late November. By 11 p.m. the support queue was four hundred deep and still climbing, and roughly three of every four messages were a version of the same two questions: where’s my order? and how do I send this back? The team had done the sensible things — hired seasonal temps, written more macros, quietly nudged the “contact us” link a scroll further down. The queue grew anyway.

The problem was never that the answers were hard. They already existed — they just lived in five different places: the order system, the carrier’s tracking feed, the returns policy, the payment gateway and a folder of resolved tickets. A human agent’s real job wasn’t knowing the answer. It was stitching those five systems together, forty times an hour, on the busiest night of the year.

“We weren’t trying to take people out of the conversation. We were trying to take away the fifteen browser tabs.”

— Head of Customer Experience
Where they started

They didn’t boil the ocean.

Rather than switch everything on at once, they picked the one flow that hurt most and was most rule-bound: returns. The reasoning was simple — if Wiztra could take a damaged-item return from first message to refund, safely and within the guardrails the team set, everything else would be easier to trust. So they started there, on a single flow, with a person watching every move.

An ordinary Tuesday

A damaged-headphones return, start to finish.

No form, no queue. The agent reads the order, checks the policy, runs a fraud check, and — under the team’s cap — issues the refund.

U
My headphones from order #10482 turned up damaged — I’d like a refund please.
W
Oh no, sorry about that. Let me sort it out now.
◎ Order & returns policy⚙ Return created · refund issued✓ Resolved
W
All done. I’ve created your return, emailed a prepaid label, and refunded $129 to your original card — you’ll see it in 3–5 business days. Keep the box; the courier will collect. Anything else?
What actually won the room

What won the room wasn’t the answer — it was the action, and the controls around it. Early on the team capped auto-refunds at a figure they were comfortable with and routed anything above it to a human. Within a fortnight they’d raised the cap twice: the built-in fraud check was catching serial-returners the humans used to miss, and every refund left a clean line in the audit log. It was the approvals that earned their trust, not the AI.

How Wiztra resolves it

Understand, ground, act.

Customer“Where’s my refund?”Wiztra agentreads · checks policy · refundsOrder systemgrounded lookupReturns policypolicy & rules✓ Refundedend to end
Request Grounded lookup Resolved
The five systems it had to touch

Store platform

Shopify · commercetools

Order & OMS

Order system · carriers

Payments

Stripe · Adyen

Helpdesk & CRM

Zendesk · Salesforce

Marketing

Klaviyo

Shipping

FedEx · UPS

Peak, the second time around

The numbers that mattered.

WSupport Analytics · trailing 6 months
Resolution rate
71%
was 34%
Avg first response
1.9s
was 6m 40s
Repeat-contact rate
8%
was 19%
Cost / resolution
$0.46
was $3.10
Resolution rate — first 6 months
50%71%38%M1M2M3M4M5M6
By intentbar = share of volume
Order status & WISMO
82% resolved
Returns & refunds
74% resolved
Product & stock
66% resolved
Complex / edge cases
→ human

The read: About 3,400 interactions a month are now resolved without a person. Repeat contacts more than halved, and the last peak was handled without a single seasonal hire — the returns flow alone paid back the rollout.

The next peak came and went without a hiring spree. Routine order and returns interactions resolved in seconds; the team spent its hours on the genuinely tricky cases instead. Their advice to another retailer was refreshingly unglamorous: start with the flow you dread most, keep a human on the expensive decisions, and watch the audit log — that’s where the confidence comes from.

See Wiztra resolve one of your busiest flows.

Book a short demo and watch it take a real return, WISMO query or order change from message to done, on your own data.