Everything here is shaped by one rule: the software does the reading and the drafting, and a person does the deciding. The parts that look like restrictions are the reason it can be trusted with your customers at all.
The assistant answers what your site covers and hands over everything else. A customer asking for a person gets one on the first tap, at any hour. And once a person joins, the assistant is finished with that conversation for good.
Those are not configuration. You can choose whether replies send immediately or wait for approval — you cannot make it answer something your site does not support, or keep a customer from a person.
Products, attributes, stock, prices, orders, customers and shipping zones. Live availability, a customer's order history, and shipping rated by your own store.
No shop needed. Answers from your pages and posts. Tools that need a catalogue are hidden rather than failing when a customer asks.
Platform is a first-class concept in the product, not a WooCommerce assumption with holes cut in it — so this is a new adapter, not a rewrite.
Connect your site and it indexes your catalogue and your pages. That index is the assistant's entire world — you can read it, search it, and exclude anything you would rather it never quoted.
Every reply carries the tools it ran, how long each took, and the pages it quoted. An agent deciding whether to send needs to see that, and an answer that turns out to be wrong has to be traceable to whatever caused it.
Build an order inside the conversation, priced from your catalogue and shipped on a rate your own store returned. It is created unpaid, with a link to your own checkout, and the customer pays through the gateway you already use.
yourstore.com/checkout/order-pay/1102/?key=wc_order_…Matched on email, so a guest checkout and a support email are the same person. One history rather than two columns: orders, conversations and site visits interleaved, because a return asked for three days after a delivery reads nothing like the same request three months after.
The app tells you whether an edit will reach your store before you save it, because for a guest there is no record there to update.
Nobody changes the address their customers already use. Forward it in; reply out through your own mail server so answers arrive from your domain and pass your SPF and DKIM.
northwind-supply-a83f19c204@in.relaypanel.iosmtp.yourprovider.com : 587Chat and email in one thread per customer, with their orders beside it. Assign, snooze, close, and leave notes your customers never see.
Your real checkout calculation, so carrier accounts and table-rate plugins are included. Parcel rates are quoted; freight is a person, always.
Run several stores, or support a client's. Each company's data is isolated in the database itself, not just in the app.
A price change reaches the assistant in seconds; a customer's reply reaches your inbox without a reload. A scheduled re-read underneath, for the day a plugin gets switched off.
Your timezone and your country's statutory holidays, detected rather than typed in. Somebody writing at midnight gets an honest answer instead of silence.
Sales, support, warranty — each forwarded in, each replying under its own name, each tagged so you can see which department a conversation belongs to.
Warm, plain or specification-first. Name the assistant whatever you like — it will still tell customers it is one.
Run it on your own server if you would rather. Same product, your infrastructure.
The roadmap is kept honest — everything under Shipped is answering real customers today.