For retail & D2C
Your customer explained it three times. Once should have been enough.
Voice, chat, text and email are usually four teams with four tools and no shared memory. An AI employee is one worker across all four, and it remembers your customer.
We’ll call you back, once. Your number never enters a marketing list.
Voice
Chat
Text
M
Live call · 0:45
Voice
Your order 41822 is going to be two days late. Nothing’s wrong, it’s held at the hub. I’ve raised it and I’ll come back when it moves.
Oh. I needed it for the weekend, honestly.
Then let me fix it, not explain it. I’ll put a replacement on overnight so it reaches you Friday, at no cost. Keep the original if it turns up.
Voice
Chat
Text
Resolved in one call
Why it became four teams
Four teams, because no one person was ever good at all four.
Phone needs someone fast on their feet. The hard written tail needs patience. Chat means holding five at once. So you hired a team per skill, each with its own budget and metric. Then your customer moved between them, and nothing followed.
WHAT YOU HAVE NOW: FOUR TEAMS, FOUR TOOLS
ONE EMPLOYEE
Voice
Fast on your feet
Chat
Five at once
Text
Short and instant
Patient with the hard tail
one memory of your customer
The boxes are what you have today. The line is the product.
An AI employee doesn’t have that constraint
The same one is fluent on a call and patient in writing, and holds your customer’s whole history either way.
Four channels stop being four teams.
The handoff between them stops existing.
What your customer said on Monday is still true on Friday.
“We already have a helpdesk that covers all four channels.”
You probably do, and your customer still repeats the whole story. Three reasons, none fixed by adding a fifth channel.
One inbox is not one memory. Four queues on one screen are still four conversations.
A macro is not a judgment. It fires on a keyword, not on what your customer told you on Monday.
The handoff is where the memory dies. The tool moves the ticket, not the context.
What it does, channel by channel
The same employee on all four. Equal billing, because your customers don’t rank them.
What it actually does on each one, and where it stops.
Voice
The phone line you already have, and nobody wants to staff
Only really staffed in office hours. It answers there, with no menu, and hands over the moment judgment is needed.
Chat
The window on your site, holding several conversations at once
In the widget you already run, at chat speed, already knowing what your customer wrote to you last week.
Text
SMS, where the short questions live
One line answers on the number your customer used, on the same thread, not a fresh conversation every time.
The hard tail, where patience is the actual skill
The six reply case and the policy edge. It answers what it can and drafts the rest with the history attached.
Demo call, recorded with consent
Transcript below, word for word.
NORTHBOUND CARE
Hi Maria, this is Northbound customer care. Your order 41822 was due Thursday and it’s going to be two days late. Nothing’s wrong with it, it’s held at the sorting hub. I’ve raised it and I’ll come back to you when it moves.
MARIA
Oh. I needed it for the weekend, honestly.
NORTHBOUND CARE
Then let me fix that rather than explain it. I can put a replacement on overnight so it reaches you Friday morning, at no cost. If the original turns up after that, keep it or send it back free, your choice.
MARIA
Yes, do that. That’s a relief, thank you.
The replacement and the free return in that call were both inside the authority this brand set.
One customer, one week
Your customer never has to say it twice.
Monday email. Wednesday chat. Friday call. Watch the row that says what it already knew.
3
channels
1
memory
0
times your customer repeats themselves
Moment 1 · Monday · Email
YOUR CUSTOMER SAID
My order was supposed to arrive Friday and it’s still not here. I need it before the weekend.
WHAT IT ALREADY KNEW
Order 41822, your customer’s first with you, promised Friday. The carrier scan stalled at the sorting hub on Thursday night.
WHAT IT DID
Answered in writing, and raised the carrier exception itself rather than asking your customer to chase it. Then it recorded the thing that matters: the parcel has to be there before the weekend.
SYSTEMS IT TOUCHED
Shopify
Carrier tracking
Gorgias
The deadline your customer gave is now a fact you hold, not a line inside a closed ticket.
Moment 2 · Wednesday · Chat
YOUR CUSTOMER SAID
Any update?
WHAT IT ALREADY KNEW
All of Monday, including your customer’s deadline. It never asks for the order number.
WHAT IT DID
Opened with the update instead of a question. The scan cleared Tuesday, so it gave your customer the new date and said out loud that Saturday is past the deadline.
SYSTEMS IT TOUCHED
Carrier tracking
Shopify
Gorgias
Two words from your customer, and no part of Monday repeated.
Moment 3 · Friday · Voice
YOUR CUSTOMER SAID
I’d rather just cancel it at this point.
WHAT IT ALREADY KNEW
Monday and Wednesday. The deadline, both messages, the carrier history, and that this is your customer’s first order.
WHAT IT DID
Took the call on the phone line you already have, with no menu. It offered the one thing inside its authority that fixes the deadline, then handed your customer to a person, because cancelling a paid order sits outside the envelope you set.
SYSTEMS IT TOUCHED
Voice
Shopify
Stripe
Gorgias
Your rep opens with all of that on screen. None of it is a question for your customer.
When it needs a person
Your rep opens with the history, not with “can you tell me what happened”.
What your customer hears today
“Can I take your order number.”
“Bear with me while I read back through the thread.”
“Sorry, which size was it.”
“I’ll have to check with the warehouse and call you back.”
Every one is a question your customer has already answered.
What your rep opens with
Who your customer is, and that this is a first order with you.
What your customer asked for on Monday, in their own words.
The deadline your customer gave, and that it has now been missed.
Every message it sent your customer, and what the carrier actually did.
The one thing it already offered, and the one only a person can approve.
Either your rep starts with all of that on screen, or they start by asking your customer to repeat the whole story. It takes a minute to check in a demo.
The two numbers you’re judged on
CSAT up and cost to serve down. Those used to be the same lever.
Both dials used to be one dial, which was hours of people’s time, so every gain on one side cost you the other. An AI employee takes the volume nobody could ever staff, at any hour, and your own people spend their day where a human changes the outcome. That’s why the two can move together now.
CSAT
Goes up by 30%
What your customer thinks of you after they have needed you.
Cost to serve
Goes down by 70%
What it costs you to keep your customer happy, hour by hour.
Prove it, don’t claim it
A random slice of your customers never hears from us at all.
They’re your control group. Whatever they do anyway is what would have happened without us. The difference is the only honest definition of what we were worth, and it’s the number we report.
Incremental repeat purchase
Treated group against the matched control, same window, same cohort.
Incremental revenue
Per thousand customers worked, counted only where the holdout shows a difference.
Contact rate, opt-outs, complaints
Reported in both directions, including when it moves the wrong way.
If we can’t show 8loop caused a result, we don’t count it. That includes the quarters where the answer is smaller than we hoped.
Ask us these, and ask everyone else
Four questions to ask any AI support vendor, including us.
Ask us first, then ask everyone else on your list the same four.
01
Does it work on voice, in the languages your customers actually speak, over the networks they actually have?
A language count is not evidence. An accent, a bad line, someone talking over it: that’s where voice agents fall over.
Ask to hear a call.
02
When your customer moves from chat to email to a call, does one memory follow, or does each channel start from nothing?
Four channels on one invoice is not one employee.
Ask to see the same customer on two channels.
03
What happens when it needs a person?
All of them hand off. What matters is what your rep sees when they do.
Ask whether your rep opens with the history, or opens by asking your customer what they already explained.
04
Can they show you what they caused, against a group of your customers who heard nothing?
Most can’t. They’re paid per conversation, so a control group is a bill they’d rather not write.
Ask for the control group.
The fourth is last on purpose. It’s the only one a demo can’t answer.
What your people do instead
It takes the volume nobody could ever staff. Your team keeps the judgment calls, and gets better at them.
The honest version, and the part you can read out to your floor.
A coach, for your own reps
It reviews your team’s conversations, not just its own
It compares each rep to what your best people do, and tells them what would have won that conversation. Not a QA score. The sentence they could have used.
A trainer, on demand
Then it rehearses it with them
It plays the customer, and the objection, until it sticks. Your new starter runs forty hard conversations in a week without one real customer paying for it.
The repetitive, out-of-hours contacts stop existing rather than getting handled faster, so your people spend their day on calls where a human changes the outcome. We won’t put a number on your staffing in a sales page. That’s your decision, not our claim.
What it plugs into, and what it costs your team
It reads your systems. It doesn’t ask you to move into ours.
Shopify
Shopify Plus
Gorgias
Zendesk
Gladly
Klaviyo
Attentive
Loop Returns
Narvar
AfterShip
Recharge
Stripe
Carrier tracking
Your data warehouse
Week 0
Read-only access to orders, tracking, returns and helpdesk history. An API key and a scoped app install. No migration.
Week 1
We write the employee from your own conversations and policy pages. You approve the plan and the guardrails before anything dials.
Week 2
Live on one result, with the holdout running.
Total ask on your developers: negligible.
Where the line is
It acts inside an envelope you set, and proposes everything outside it.
It quotes nothing that didn’t come from your systems, never invents a rate or a charge, and never commits you beyond the authority you gave it in writing. Inside the envelope it acts. Outside it, it waits for a person.
Replacement and expedited shipping, without approval
up to $150
Waiving a return, inside published policy
allowed
Committing to a delivery date
only dates the carrier confirmed
Reporting a refund
after finance releases it, never before
Issuing a discount or goodwill credit
Anything above the limits, or outside policy
proposed to a person
You write these lines. You can widen them later, and every use is on the record with the amount and the reason.
Security and compliance
Quiet by default is the easiest thing a compliance team ever approved.
Consent state, frequency caps, calling windows and one-tap opt-out aren’t bolted on top. Restraint is the default, and every conversation is reviewed, scored and exportable.
TCPA
DNC scrubbing
Per-timezone calling windows
One-tap opt-out
Transactional and marketing separated
Never captures a card on a call
CCPA
Tenant isolation
Immutable conversation log
SOC 2
PCI scope
The only thing we’re asking for
Two weeks. One result. A control group.
What it costs to find out
2,000 calls, free
No fee and no commitment beyond the two weeks. What counts as a win is agreed in writing before anything dials.
One result, chosen by you
Delay recovery, failed payment, winback, or post-purchase retention. Not a platform rollout.
A randomised holdout from day one
Agreed size, agreed cohort, agreed before anything goes live.
Success metrics in writing, first
What counts as a win is settled before start, not argued in the review.
Clock starts at go-live, not signature
Integration time is ours to absorb, not yours to pay for.
About a day of your developers
Read-only access to the systems you already run. No migration.
Your data stays yours
Your customers and what they told us never leave your tenant.
Book your two week pilot
If you would rather talk to a person
Twenty minutes, and you’ll have heard three real calls before you’ve heard a pitch.
Some want to be called by the product. Some want a person and a calendar. No deck either way.
What the twenty minutes actually is
Three real recordings, first. Before we ask you anything. If they’re not good, we’d both rather know at minute three.
Your envelope, live. We write your authority limits on screen with you: replacement ceiling, what it may promise, what it may never do.
One result, picked. Which single outcome a two week pilot would chase, and what number would count as a win.
The money, out loud. What happens after the pilot, on this call rather than the third.
No deck, no discovery questionnaire, and nobody from our side who can’t answer a technical question.
Bring whoever owns your helpdesk. Twenty minutes is enough for an engineer to judge whether the integration is real.
Prefer email? Send one line and we’ll reply with the three recordings, no meeting needed.
Your customer should only ever have to explain it once.
Three minutes from now you can have heard it answer on the phone, and you’ll know exactly what your own rep would have seen next.
Book a demo