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.

Address changes

Takes the panicked "wrong address!" message, checks how far the order has traveled, and fixes what can still be fixed — on the order, the label, or with the carrier mid-route.

Book a Demo See it run ↓
01 · Problem

The customer notices in minutes
the fix takes until someone's shift starts.

The race

The order moves while the ticket waits

An address fix is trivial before the label prints and near-impossible after dispatch. The window is hours; the queue is a day.

The relay

Support can't touch fulfillment

The agent who reads the message can't edit the order; the warehouse that could, never sees the message. The fix dies in the handoff.

The aftermath

A wrong address becomes three tickets

The original ask, the 'where is my order' when it goes to the old flat, and the redelivery-or-refund fight. All from one unread message.

At 9:14 AM it was one field to edit. By 3:00 PM it was a lost parcel.

02 · Solution

The message is read at once. And the fix matches the moment.

9:14 AM · Order placed 8:50 AM
SignalSMS
Customer says the order has their old address
Memory
  • Order #3960 · placed 24 minutes ago
  • Not yet allocated — no label, no pick
  • New address captured and validated in-channel
Customer· SMS

"Just ordered and it's going to my old flat — can you change it to my new place?"

Clarwiz· Shopify

Checks fulfillment state: safe to edit directly.

9:15 AM · Act
SignalShopify
Order still editable — address swapped before allocation
Memory
  • Address updated on the order, pre-label
  • Validation passed ZIP code serviceable, format clean
Clarwiz· Shopify

Writes the new address to the order and re-confirms serviceability.

Clarwiz· SMS

Confirms the change with the full new address echoed back for a final check.

9:16 AM · Close
SignalSMS
Customer confirms the new address is right
Memory
  • Customer confirmed address in writing
  • Closed in-channel — 2 minutes end to end
Clarwiz· SMS

Done — order #3960 now ships to the new address. You'll get tracking as usual.

Log· Run record

Old address, new address, who confirmed, when.

2:20 PM · Harder case
SignalCockpit
Same request on an order already with the carrier
Memory
  • Already in transit — direct edit impossible
  • Options drafted: carrier redirect ($15) or a hold at the local depot
You· One tap

Approve the redirect fee or the hold — cost and odds of each attached.

Outcome· Run record

Redirect filed with the carrier; customer told the honest new ETA.

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

Same mistake. Different ending.

MomentBefore ClarwizOn Clarwiz
Reading the messageWhenever the queue gets there.Within a minute of it arriving.
Pre-dispatch fixPossible, if anyone acts in time.Done in the same conversation.
In-transit fix"Sorry, nothing we can do."Redirect or hold, priced and offered.
The wrong-address returnStandard outcome, full round-trip cost.The exception, and a signed decision.
ConfirmationAssumed.New address echoed back, confirmed in writing.
04 · Outcome
83%
of address-change requests fixed before the label printed.
2min
median time from message to corrected order, pre-dispatch.
100%
of paid redirects approved by a named person before the fee is spent.
Numbers from one pilot, counted to the unit. Your log will differ — that's why it's a log.
05 · FAQs
What happens if the order has already shipped?
The case shifts from editing to negotiating: carrier redirect, hub hold, or — worst case — an intercepted return-to-sender turned into a fresh dispatch to the right address. Each option comes priced, and paid ones wait for your approval.
Does it validate the new address?
Yes — format, ZIP code serviceability against your carrier coverage, and an echo-back the customer must confirm in writing. A change is only as good as the address it changes to.
Can a customer abuse this to redirect someone else's order?
The conversation must come from the channel identity on the order — same phone number or email. Anything else routes to a person with a flag, and high-value orders can be set to always require your sign-off.
Does this cover changing items or cancelling, too?
Address and contact changes are this process. Item edits and cancellations are neighboring processes with their own limits — same pattern: fix what's fixable now, escalate what isn't.
What do we need to integrate before a demo?
Nothing. The demo runs read-only on your real orders and conversations in thirty minutes. Going live connects your store, carriers and channels — Shopify, 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