Book a Demo

Product overview

Business orchestration that runs on your business context.

See how it works
Build
PlaybooksModel a process once — a team of agents runs it in parallel, end to end. IntegrationsPlugs into the store, helpdesk, and carrier tools you already use.
Orchestrate
BrainGive every agent one memory of your customers, policies, and past decisions. CockpitWatch every run live and sign the calls that matter.
Optimize
Simulation & A/B testingRehearse changes on real cases, then run two versions and keep the winner. InsightsSee what agents saved, what they refused, and where runs stall.
Scale
ChannelsMeet customers on text, email, voice, and chat — one process behind all of them. Trust & ReliabilityDeploy with an audit trail, autonomy limits, and a stop that lands.

Refund approvals

Processes refunds within your limit automatically; anything above it waits for your approval. The customer gets an answer in seconds — and the money above your line never moves without a signature.

Book a Demo See it run ↓
01 · Problem

The refund isn't expensive
the eleven minutes around it are.

The queue

11 minutes per refund

Policy lookup, order history, payment path, PSP console, a reply written from scratch — at 40 refunds a week, a full working day spent on cases the policy already decided.

The deadline

Refunds wait. Chargebacks don't.

Dispute evidence has a filing window, and it closes whether or not your inbox is caught up. Late evidence is a lost dispute.

The lottery

The answer depends on who's online

Tuesday's agent and Saturday's agent settle the same case two different ways — and nobody's name is on either decision.

The policy already made the call. Someone still has to run it.

02 · Solution

The small one closes itself. The big one finds you.

7:42 PM · Tuesday
SignalSMS
Customer asks where the refund for order #8841 is
Memory
  • Order #8841 · paid by Visa 4421
  • Return scanned Thursday, warehouse in
  • One failed refund attempt on record
Customer· SMS

"Where is my refund for order #8841? It failed on my card last week."

Clarwiz· Policy

Checks the window, item receipt and payment path — inside policy.

7:43 PM · Act
SignalPolicy
Refund is inside policy and under the auto-approve limit
Memory
  • Your limit: $200 per refund, set per process
  • This case: $38.00 — inside the line
Clarwiz· Stripe

Re-issues $38.00 to the original card.

Clarwiz· Evidence

Packs the chargeback evidence in parallel: delivery scan, return scan, policy text.

7:44 PM · Close
SignalSMS
Refund issued — the customer is still waiting for an answer
Memory
  • Texted in at 7:42 PM
  • Closes in-channel — no ticket, ever
Clarwiz· SMS
Clarwiz Agent
Your $38.00 refund for #8841 is re-issued to your Visa ending 4421 — reference RF-8841-2. It lands in 3–5 business days.
Customer
Perfect, thank you!
Log· Run record

Closed in channel. No ticket created.

8:10 AM · Next day
SignalCockpit
$412.00 refund request overnight — above the limit
Memory
  • Money never moved — held at the limit
  • Whole run attached: order, policy clause, draft reply
You· One tap

Approve or hold — from your phone, with everything the system saw.

Outcome· Run record

Refunded, packed and closed — 40 seconds after your tap.

Every action above is logged — who, what, when, on which system.
03 · What changed

Same refunds. Different week.

MomentBefore ClarwizOn Clarwiz
First replyNext morning, if the inbox is caught up.Under a minute, in the customer's channel.
Refund inside policyWhoever is online decides, eleven minutes each.The limit decides. Money moves in seconds.
Above the limitSame queue, same eleven minutes, more nerves.Stops at the money. Waits for a named signature.
Chargeback evidenceAssembled later, if the deadline is remembered.Packed in parallel with every refund.
Tickets createdOne per case, plus the follow-ups.None. The run log is the record.
04 · Outcome
94%
of refund cases closed without a person touching them.
48s
median time from customer message to money moved, inside the limit.
100%
of cases above the limit signed by a named person. No exceptions.
Numbers from one pilot, counted to the unit. Your log will differ — that's why it's a log.
05 · FAQs
Who sets the auto-approve limit, and can it change?
You do, per process — not per account. Set it at $0 on day one if you like: every refund then waits for a signature and Clarwiz just does the lookups and drafting. Raise it when the log has bored you for a few weeks. Changes take effect on the next run.
What happens with a failed or partial refund?
The payment path check is step one, before anything moves. A refund that already failed is retried on the original path; if the path is dead (expired card, closed account) the case stops and routes to a person with the failure attached — it never silently picks a different way to send money.
What about refunds to an expired card, or as store credit?
A refund to a card that no longer exists follows the card network's rules — it usually still lands on the successor account, and the case says so. Where the customer prefers store credit, that's offered inside the same limit; a payout to any NEW destination always holds for approval — a new destination is a decision, and decisions are yours.
Will it create tickets in our helpdesk?
No. The case closes in the channel the customer wrote in, and the run log is the record. If your team lives in Zendesk or Gorgias, Clarwiz writes the closed run back onto the customer's timeline so history stays in one place — but it never opens a ticket for a case it already closed.
What do we need to integrate before a demo?
Nothing. The demo runs end to end on your real conversations and orders, read-only, in thirty minutes. Going live afterwards connects your store, PSP and channels — Shopify, Stripe, Zendesk and about 3,000 others.

See this run on your own data.
Thirty minutes, nothing connected.

We take this process, connect nothing, and show you the run end to end on your real conversations and orders. When you're ready, go live at the autonomy level you choose.

Book a Demo
30 minutes · One process · SOC 1 · SOC 2 · ISO 27001 · PCI DSS · GDPR