AI customer service for online stores
Automate Customer Service Answer Every Customer
bonedesk answers your customers on chat, email, and SMS in your brand's voice, from live order and shipping data, and hands the conversation to your team the moment a human should step in.
Every question in, every answer out. Automatically, in your voice
24/7
Always answering
34.2h
Agent hours saved
0
Questions left behind
How it works
Automation that answers, acts, and knows when to hand off
bonedesk sits on every channel your customers already use. It answers what it can prove, turns requests into tickets your team can act on, and steps aside the moment a person should take over. Then it measures all of it.
- 01
A customer asks
On your store's live chat, by email, or by text. In chat they introduce themselves once; from then on everything bonedesk looks up is bound to that customer.
- 02
bonedesk answers
In your brand's voice, from your knowledge base and live order, shipping, and payment data: the shortest complete answer, with nothing invented.
- 03
It acts, safely
Cancellations, refunds, address changes, replacements: the customer confirms on a card, bonedesk re-checks the live order and files a typed ticket. Nothing changes an order without your team.
- 04
It hands off when it should
When a human is needed, the ticket is filed and the chat moves to your team in real time. When they solve it, the bot picks back up.
Channels
Every channel, one assistant
The same knowledge, the same voice, the same rules, whether a customer writes on your site or in their inbox.
Live chat on your store
A WordPress plugin or one script tag. Customers verify with an email code or their store login, attach photos and files, and get answers in seconds.
Email, SMS, and Zendesk tickets
Every inbound message is classified, tagged, and prioritised the moment it lands, with a reply drafted in your voice for the team to send.
Live hand-off
While a ticket is open the conversation belongs to your team: agents' replies appear in the customer's chat as they're written, and solving the ticket hands the chat back to the bot.
Connected to your store
Answers from real data, not guesses
bonedesk reads from the systems you already run, plus your knowledge base and the approved pages on your own site, and never writes to them. The only thing it ever creates is a ticket for your team.
- WooCommerce
Orders, customers, products, coupons, certificates of analysis
- ShipStation
Tracking, delivery estimates, stalled shipments
- Zendesk
Ticket history, typed tickets, live hand-off
- Payments
NMI and Stripe confirmations
- Affiliates
SliceWP, AffiliateWP, Affiliate Pirate
- Fraud Shield
Risk decisions and blocklists, read-only
The merchant portal
See the value it delivers, every day
Value delivered
Tickets solved by the bot, split into confirmed and presumed; assists where your team used its prep or its drafts; agent hours saved with a conservative floor; median speed against your own Zendesk baseline.
Live conversations
Every chat as it happens: the transcript, what the bot looked up behind each reply, ratings, tickets filed, and your team's replies. Searchable and exportable.
Knowledge and capabilities
Upload documents, approve compliance wording, test with “ask the bot”. Switch tools on and off one by one, write playbooks and forms, set reply length and chat mode: admin, agent, or customer.
Team and activity
Admin, agent, and viewer roles; an audit log of everything the bot and the team did; CSV out of anything.
Automation with judgment
It knows the difference between a question and a problem
Before every reply, typed judgments on intent, tags, frustration, and compliance decide what the bot may do. Routine questions get answered. Problems that need a person (a disputed charge, an upset customer, something the knowledge base can't settle) become a ticket with everything the agent needs already written up.
Prepared hand-offs
The ticket carries what the customer asked, what the bot looked up, and a drafted reply, in reading order: what to do, the facts, where they came from.
Your rules, enforced
Which tools the bot may use, what it may promise, how long it may write, and what it must never discuss are settings in the portal, enforced by the system, not by prompt-wording alone.
Trust
Built to be trusted with your customers
Locked behind sign-in
Every console and portal request carries a verified identity: your team signs in with Google or GitHub. Without one, bonedesk fails closed.
Scoped to the customer
In customer mode every lookup is bound to the signed-in customer and your store. Internal notes, risk flags, and business figures never reach the chat.
Read-only by design
No integration can change an order. Actions become typed tickets that your team acts on.
Guardrails on regulated topics
Questions you mark off-limits get your approved wording, exactly that and nothing improvised, and are never escalated into tickets.
Audited end to end
PII redaction, scanned uploads, and an activity log of everything the bot and the team did.
Apply
Bring bonedesk to your store
Three short steps, about a minute. We read every application ourselves and reply by email.
We look at the fit
Your store, the channels your customers use, and how much support you handle today.
We set you up together
Your workspace, the connections to your store and help desk, and a knowledge base built from what your team already knows.
You go live
The widget on your store, the inbox channels you choose, and the portal for your team, with the value delivered on the dashboard from day one.
The application is locked
Slide to unlock it. Three short steps, about a minute.
Already a merchant?
Sign in to your workspace to see today's conversations, what the bot answered, and the value it delivered.