Cancel O-8421
A duplicate order, stopped before the pick
Billed by the helpdeskCost of this conversation
- AI fee$0.99
- Billed asRefund
- Resolved, $0.99Issued
- Customer ratingCame back
- 5 starsNo
ResolvedDone
Everything a request needs to actually finish: order changes, delivery problems, product help and the knowledge behind every answer. We build it into the helpdesk and systems you already use, then run it with you or hand it over.
Led by operators who’ve built the order, fulfillment and internal systems behind service, in businesses up to $2B+ in annual revenue.
Each request touches an order, a shipment, a payment or a product. Support is finished when that thing has actually happened, not when the chat closes.
Getting it to them
Supply chain & fulfillmentWhen they need help
Customer service & support · this pageKeeping them
Retention & lifecycleEmail had a team, chat had another, social and phone had their own. Five queues, five tools and one number: tickets closed. Nobody could see whether the refund had actually been issued.
Shopify’s AI staff member answers order questions for free. Gorgias, Zendesk and Intercom’s Fin answer and act, then bill per resolution: one counts a configured handoff, one needs 72 hours without a human, one has an AI check it.
Finishing a request means changing an order, a shipment or a payment, and checking that it changed. That takes your policies, your systems and a record no vendor’s invoice can supply.
Orders, shipments, payments, policies and products. The state a chat window can’t see, and the core every part reads from.
| System | State | Time |
|---|---|---|
| Shopify | Canceled | 6:13 pm |
| Warehouse | Stopped before pick | 6:12 pm |
| Payment | $84 refund issued | 6:13 pm |
| Customer | Confirmed | 6:14 pm |
Cancellations, address fixes and size swaps check the edit window, stop the pick and refund once. Anything the warehouse already started goes to a person.
A stalled scan opens a case with a promised date, a remedy and an owner, not another tracking email. Returns and exchanges follow the same path.
| Case | Problem | Remedy |
|---|---|---|
| REC-209 | Olive M, no scan for 4 days | Replacement shipped |
| REC-211 | Navy L, marked delivered, not received | Refunded, claim open |
| REC-214 | Sand S, address returned by carrier | Waiting on customer |
| REC-216 | Trail pant, exchange for a 34 | Label sent |
Answers come from approved product facts, with the version named. When the facts don’t cover a question, the shopper hears that, and a person picks it up.
Is the canvas field jacket machine washable?
Yes, on cold. Fernway hasn’t published a waterproof rating, so we don’t claim one.
From product facts, version 2
Every policy and product fact has an owner, a version and an effective date. When one changes, the old one is retired everywhere at once.
| Source | Version | Owner | Effective |
|---|---|---|---|
| RET-13 · Returns | 30 days | CX lead | Oct 15 |
| RET-12 · Returns | 14 days | CX lead | Retired |
| CAT-042 · Product facts | Version 2 | Merchandiser | Sep 24 |
| CAN-3 · Cancellations | Before the pick | CX lead | Aug 1 |
A separate record joins each conversation to what actually happened in the order, warehouse and payment systems. It doesn’t depend on any helpdesk’s idea of resolved.
Your orders, your policies and your playbooks stay in accounts you control. If we ever part ways, the engine stays.
Fernway’s canvas field jacket has just gone to market. Here is the support engine at work, day by day.
Day 1
Order O-8421 hadn’t been picked. The warehouse stop, the cancellation and the $84 refund finished in two minutes, and the customer was told once it was true.
| Step | Result | Time |
|---|---|---|
| Customer verified | Owns O-8421, paid $84 | 6:12 pm |
| Warehouse stop | F-882 stopped before pick | 6:12 pm |
| Shopify order | Canceled | 6:13 pm |
| Refund | $84 issued once | 6:13 pm |
| Customer told | Confirmed by email | 6:14 pm |
Cancellation policy CAN-3
Day 3
The stop came back unconfirmed, so nothing said “canceled” until it was. The one step left, the refund’s settlement, has an owner.
Your order O-8426 is canceled
Your order is canceled and the $84 refund has been initiated. We’ll confirm any remaining payment status separately.
Sent after the warehouse confirmed the stop
Day 6
No scan for four days opened a recovery case with a promised date, a remedy and an owner. The replacement shipped before the customer wrote in.
| Step | What happened | State |
|---|---|---|
| Detected | No scan for 4 days, promise missed | Opened |
| Remedy | Replacement O-8452-R1, Olive M reserved | Shipped |
| Customer | Told the new date before asking | Sent |
| Carrier claim | Logistics owns it, not blocking | Open |
Two conversations the helpdesk scores identically. Switch views to see what each one cost.
A duplicate order, stopped before the pick
Billed by the helpdeskCost of this conversation
ResolvedDone
A duplicate order, shipped before the stop
Billed by the helpdeskCost of this conversation
ResolvedReopen and fix
How many of your resolved tickets are the $109 kind?
A support review finds out, on your own conversations, in two to four weeks.
Day 9
The answer came from the product facts, version 2. It said what Fernway claims and what it doesn’t, and a teammate has the rest in the morning.
Is it waterproof? I’m heading out Saturday and it might rain.
No. Fernway doesn’t give the canvas field jacket a waterproof rating, so we can’t promise it keeps rain out. If it gets muddy, it’s machine washable on cold. I can pass you to the team for a better fit for Saturday.
From product facts, version 2 · 11:04 pm
Day 11
Returns went from 14 days to 30 on October 15, but some answers still quoted RET-12. RET-13 replaced it everywhere, and tests now catch an answer that quotes the old window.
3 of 3places that still carried RET-12, now fixed
RET-12 retired · RET-13 effective Oct 15
Day 14
The other 280 didn’t match the order, warehouse or payment record, most of them cancellations. The decision: fix cancellations first, and check again in 30 days.
Checked against order, warehouse and payment records
Edits, cancellations and status, finished in every system.
Problems fixed before the customer chases.
The right answer for the exact product and version.
One current version of every policy and fact.
Closed means done, and fixes that stick.
Your team, AI and partners, each on the right work.
What we usually find
Where it falls back on people
Every change request means checking Shopify, the warehouse and the payment by hand, usually late in the evening.
What we’d do
We switch on Shopify’s AI staff member first, add the order-change path it lacks, and run it with you until you hire.
What we usually find
Where it falls back on people
The AI answers, then agents finish the cancellations, delivery problems and policy questions it can’t, and nobody checks what really got done.
What we’d do
We configure the AI you already pay for, build the missing order and delivery paths, and train the team to run the record.
What we usually find
Where it falls back on people
The BPO reports tickets closed and a QA score. Policy changes reach it late, and nobody can show what actually finished.
What we’d do
We build the record of what’s finished in your accounts, so the next contract can be written on outcomes instead of tickets.
What we usually find
Where it falls back on people
Each reports its own number, and a request that crosses them goes round again.
What we’d do
We connect them to one record of what finished, then coordinate the work or run it.
If your vendor or BPO disappeared tomorrow, would your team still know how every request gets finished?
The engine, mapped to your orders, policies and team.
In your helpdesk and systems, connected, tested and documented.
We run it with you, or train your team and step back.
Fixed fees to design and build. Monthly to run, with part of the fee tied to agreed targets where the numbers support it.
Our operators built and ran commerce, order, fulfillment and internal tools in businesses up to $2B+ a year. We know what a support agent can’t see from the helpdesk, because we built what sits behind it.
Fernway’s 9,800 contacts last month, sorted by what really happened
9,800
Done, and stayed done
6,100
Confirmed in the order, warehouse and payment records
Closed, but not finished
2,100
Marked resolved, but the records disagree
Came back within a week
1,600
The request wasn’t finished the first time
1,600 contacts a month came back within a week. That’s 16% of the total, and each one is a request nobody finished.
We read a month of your conversations against your order, warehouse and payment records, find what’s really finished, and map the engine. Every opportunity is sized and given a verdict: do first, validate, defer or leave alone.
We reply within one business day.