Some of what we set up for retailers
Order questions
Order status emails get a reply drafted from live order data for your team to send.
Returns
Return requests are checked against your policy before a refund is drafted.
Reorders
Reorders are drafted when stock runs low, for your team to approve.
Payout matching
Payouts are matched to orders and fees are coded for your bookkeeper.
Product questions
Product questions are answered from your own catalog.
Customer segments
Customer segments are updated from purchase history for your campaigns.
Some of the software we connect for retailers
All platforms
Questions retailers ask us
Do customers talk to an AI?
Only if you want them to, and replies can wait as drafts for your team to send.
Does this work with our store and support tools?
In most cases, yes. We confirm what your plan allows, then connect through the official API first, scheduled reports or exports next and browser steps your team approves last.
Who approves refunds and replies?
Your team, until you decide a step can run on its own.
How is customer data protected?
Each workflow gets only the access it needs, your data stays out of model training, every action is written to an action log, and you own everything we build.
What happens if a draft is wrong?
Your team edits or rejects it from the approval email, and every action stays in the action log.
Will this replace anyone on our team?
The workflows take over the copying, chasing and retyping, and your team keeps every decision and every customer relationship.