Resolved means done.

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.

Every request is a promise someone has to keep.

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.

Requests arrive by email, chat, SMS, social DMs, phone and AI assistants, meet in your helpdesk and end as done, or come back as asked again.EmailChatSMSSocial DMsPhoneAI assistantsYour helpdeskDoneAsked again

Getting it to them

Supply chain & fulfillment

When they need help

Customer service & support · this page

How customer service changed

Every channel had its own people.Each counted tickets closed.

Email 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.

Then the helpdesks learned to answer.And started billing per resolution.

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.

So the edge moved to finishing the job.One record of what actually happened.

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.

Skip the walkthrough

Look inside.Six parts, built around your business.

  1. Your business.Every system a request touches.

    Orders, shipments, payments, policies and products. The state a chat window can’t see, and the core every part reads from.

  2. Order changes.Done before the warehouse picks.

    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.

  3. Delivery problems.Fixed before the customer chases.

    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.

  4. Product help.Answers from the right version.

    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.

  5. Knowledge.One version of every policy.

    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.

  6. Proof.Closed means done.

    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.

Built in your accounts.Yours to keep, whoever runs it.

Your orders, your policies and your playbooks stay in accounts you control. If we ever part ways, the engine stays.

Two weeks after the launch. One request at a time.

Fernway’s canvas field jacket has just gone to market. Here is the support engine at work, day by day.

  1. Day 1

    Cancel the whole order. I ordered twice.

    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.

    AI
    Reads the request, writes the reply
    Rules
    Checks the window, stops the pick
    Your team
    Sets the policy and the limits
    Use caseChange or cancel orders before the warehouse picks
    Completion record · CX-1042Order O-8421
    StepResultTime
    Customer verifiedOwns O-8421, paid $846:12 pm
    Warehouse stopF-882 stopped before pick6:12 pm
    Shopify orderCanceled6:13 pm
    Refund$84 issued once6:13 pm
    Customer toldConfirmed by email6:14 pm

    Cancellation policy CAN-3

  2. Day 3

    The warehouse picked it between the lookup and the cancel.

    The stop came back unconfirmed, so nothing said “canceled” until it was. The one step left, the refund’s settlement, has an owner.

    AI
    Writes what’s true, no more
    Rules
    No “canceled” until the stop is confirmed
    Your team
    Finance owns the settlement
    Use caseChange or cancel orders before the warehouse picks
  3. Day 6

    Olive M stalled at a carrier hub. The customer hadn’t asked yet.

    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.

    AI
    Reads the scan history
    Rules
    One replacement per case
    Your team
    Logistics owns the claim
    Use caseRecover delayed and lost shipments before customers chase
    REC-209 · O-8452
    StepWhat happenedState
    DetectedNo scan for 4 days, promise missedOpened
    RemedyReplacement O-8452-R1, Olive M reservedShipped
    CustomerTold the new date before askingSent
    Carrier claimLogistics owns it, not blockingOpen

Resolved. Not the same.

Two conversations the helpdesk scores identically. Switch views to see what each one cost.

Whose view

Cancel O-8421

A duplicate order, stopped before the pick

StatusResolvedUnchanged

Billed by the helpdeskCost of this conversation

  • AI fee$0.99
Billed asRefund
Resolved, $0.99Issued
Customer ratingCame back
5 starsNo

ResolvedDone

Cancel O-8433

A duplicate order, shipped before the stop

StatusResolvedUnchanged

Billed by the helpdeskCost of this conversation

  • AI fee$0.99
  • Agent reworkNot shared$6
  • Return shippingNot shared$18
  • RefundNot shared$84
Billed asRefund
Resolved, $0.99Never created
Customer ratingCame back
5 starsYes

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.

  1. Day 9

    A shopper asked at 11 pm if it’s waterproof.

    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.

    AI
    Answers in the shopper’s words
    Rules
    Only approved facts
    Your team
    The merchandiser owns the facts
    Use caseAnswer product questions from the right version of the facts

    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

  2. Day 11

    Six conversations quoted the old returns policy.

    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.

    AI
    Finds answers using the old policy
    Rules
    Retired sources can’t be cited
    Your team
    The CX lead approves the policy
    Use caseKeep every answer current when policies and products change
    Policy change · RET-13

    3 of 3places that still carried RET-12, now fixed

    • Help center article now says 30 days
    • AI knowledge source now says 30 days
    • Agent macros now say 30 days
    • Test added: a return on day 20 is allowed
    • Six customers told the right windowDue tomorrow

    RET-12 retired · RET-13 effective Oct 15

  3. Day 14

    Of 2,140 conversations marked resolved, 1,860 were done.

    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.

    AI
    Judges each conversation
    Rules
    Checks the record, not the ticket
    Your team
    The CX lead and finance decide
    Use caseCheck that AI and agents actually finished the job
    Launch reviewDay 14
    • Marked resolvedLaunch conversations, Day 1 to 142,140Closed
    • Verified doneMatches the order, warehouse and payment record1,860Done
    • Not doneMostly cancellations280Reopen
    • DecisionFix cancellations first, then check again30 daysDecided

    Checked against order, warehouse and payment records

Built around your team. Whatever it looks like today.

Your setup

You’re answering support between everything else.

What we usually find

  • Shopify Inbox
  • A part-timer
  • A shared inbox

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.

  1. Design
  2. Build
  3. Run

A good team, with the helpdesk’s AI agent switched on.

What we usually find

  • Shopify Plus
  • Gorgias or Zendesk
  • The helpdesk’s AI agent
  • A 3PL

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.

  1. Design
  2. Build
  3. Equip

An outsourced team on per-seat or per-ticket terms.

What we usually find

  • A BPO
  • Per-seat or per-ticket terms
  • Your helpdesk
  • A monthly QA report

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.

  1. Design
  2. Build
  3. Run

A helpdesk AI vendor, a BPO and in-house specialists, and nobody owns the outcome.

What we usually find

  • A helpdesk AI vendor
  • A BPO
  • In-house specialists
  • Three dashboards

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.

  1. Design
  2. Build
  3. Run

Yours to keep. Whoever runs it.

If your vendor or BPO disappeared tomorrow, would your team still know how every request gets finished?

When the engagement ends, with
What leaves
The people, the playbooks and the know-how.
What stays
Last month’s QA report.
What leaves
The actions set up in their platform, and their definition of “resolved.”
What stays
A conversation export.
What leaves
Nothing.
What stays
All of it: in your accounts, documented, with your team trained to run it.
  1. Design

    The engine, mapped to your orders, policies and team.

  2. Build

    In your helpdesk and systems, connected, tested and documented.

  3. Run it, or hand it over

    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.

We’ve built the systems support depends on.

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.

  • 15+ years building commerce products, teams and systems
  • $2B+ in annual revenue supported by platforms led in prior roles
  • Seven figures to acquisition on technology built from scratch
About the team

Start with a support review. See what really got finished.

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

  • Status questions3,100
  • Address changes600
  • Product questions1,500
  • Returns900

Closed, but not finished

2,100

Marked resolved, but the records disagree

  • Cancellations700
  • Delivery problems900
  • Returns500

Came back within a week

1,600

The request wasn’t finished the first time

  • Cancellations300
  • Delivery problems800
  • Policy questions500

1,600 contacts a month came back within a week. That’s 16% of the total, and each one is a request nobody finished.

Two to four weeks. A plan that’s yours.

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.

  • Two to four weeks
  • Fixed fee, quoted after a short call, credited in full if we build it
  • The plan is yours, whoever builds it
  • The findings are yours whether or not we build

Make resolved mean done. Start with a support review.

We reply within one business day.