1
Chief
Reads each ticket, applies your policy pack, and hands the unit to the right runner. Anything the pack does not cover goes to a person, with the reason written down.
Never writes to your store, your helpdesk or a customer.
Returns & WISMO Desk
“Where is my order?” and “I want to return this” — answered and actioned, end to end.
Four digital workers on one workflow, in the store and the helpdesk you already run. Each works in its own isolated browser session on our side, so there is nothing to install. The runners work at the same time. The Checker works alone, in a session it shares with no one. Every refund at or above your cap waits for a person.
Start a 30-day pilot
From $2,500 a month. Free for the pilot, no card.
What it handles
- Looks up every order-status question in your store and replies with the real shipment state
- Opens returns that fall inside your policy window, with the right reason code
- Processes the refund or store credit once the return is accepted
- Routes everything else to the right human queue instead of guessing
Where it stops and asks
- A refund over your threshold holds for your approval
- An order outside the return window escalates to a person
- Damaged-goods claims and partial returns are never decided alone
Works in
- Shopify, Magento or your own order system
- Zendesk, Freshdesk, Intercom or Salesforce Service Cloud
- Gmail or Outlook
The desk
Four workers, each allowed to touch one thing
The split is by blast radius, not by confidence. A worker that reads never writes; a worker that prepares money never sends it; the worker that checks never shares a session with the one it is checking.
2
WISMO Runner
Opens the order in your store, reads the real shipment state, and drafts the reply in your helpdesk. Every fact in the draft is read from a screen, not remembered.
Never touches a refund or a return.
3
Returns Runner
Checks the order against your return window and reason codes, opens the return, and prepares the refund or store credit for the gate.
Never sends money on its own — the gate decides.
4
Checker
Re-reads the order in a separate session and fails the unit if the amount, the order or the customer do not match. A failed check is corrected and re-checked, up to three times, then held.
Never shares a session, a login or a transcript with a runner.
Reads and routes
Chief
Applies your policy pack to each ticket and hands it to the runner that owns it.
one unit at a time
Runs concurrently
WISMO Runner
Reads the shipment state in your store and drafts the reply.
no edge between runners
Runs concurrently
Returns Runner
Checks the window, opens the return, prepares the refund.
every unit
Separate session
Checker
Re-reads the order and fails the unit on any mismatch. Corrects up to three times, then holds.
gate
Hold
Refund at or above your cap, outside the window, or a failed check. Waits in your approval inbox.
Commit
Reply sent, return opened, receipts written. Replayable.
The gate
Closed until a person or a rule opens it
Money, customer-visible sends and production writes are held by default. A hold is a decision for a named person in your approval inbox, and every decision is recorded with the receipt. A rule you set can decide for you, for example a refund cap, and only a person changes that rule.
- A refund at or above your cap holds for a named person. It cannot be committed without their decision on file
- An order outside the return window, a partial return or a damaged-goods claim holds rather than resolves
- A customer-visible send goes out only after the Checker passes the unit
- Three failed corrections on one ticket and the ticket holds; the desk moves on
Sizes
Priced by the volume the desk carries
All four workers, the policy pack, the approval inbox, receipts and replay come with every size. The size sets how much the desk is built to carry each month.
Core
$2,500 / month
Up to 1,500 order-status and return tickets a month
- All four workers on the desk
- Your policy pack: refund cap, return window, reason codes
- Approval inbox for every hold
- A work receipt and a cost receipt on every finished ticket
- Replay of every session
StandardMost pilots
$4,500 / month
Up to 5,000 tickets a month
- Everything in Core
- Runners work several tickets at once inside the same policy pack
- Daily roll-up: every ticket accounted for, missing ones listed by id
- Hold rate and wrong-order rate reported beside close time
High volume
$7,500 / month
Up to 15,000 tickets a month; talk to us above that
- Everything in Standard
- Peak-season windows: the desk keeps its caps while the queue spikes
- Weekly policy review with a person from our side
- Dedicated Workspace add-on available for tools behind a VPN or allow-list
Individual digital workers are still available at Entry $1,000, Mid $2,250 and Expert $4,500 a month, and the Dedicated Workspace add-on at $500 a month. A desk does not replace them; it is the same workers with the workflow designed for you. Core costs less than four Mid workers because it is not four unrestricted seats: it is a packaged graph with a ticket cap, one workflow, and a policy pack that decides what it may and may not do.
What we report
Close time is never reported alone
A desk that closes tickets fast by closing them wrong is worse than no desk. Every number comes with the two that keep it honest, and the daily roll-up lists any ticket the desk did not account for, by id.
- Close time
- Hold rate: how often a person had to decide
- Wrong-order rate: how often the Checker caught a mismatch
- Cost per finished ticket
The pilot
30 days on a slice of your queue
Your order-status and return tickets for 30 days, with a human approving every refund above the limit you set. You set the refund cap on day one. We expand only when the hold rate and the wrong-order rate say so.