Published because a support tool asking you to trust it with your customers should be honest about what it can do today. Anything marked shipped is running in production, answering real customers for a real store — not demoed.
One login, many companies, instant switching. Owner, admin and agent roles. Isolation enforced by the database itself, with a test suite that proves one company cannot read another's data through any route.
Catalogue, orders, customers and shipping zones synced, live on change and re-read on a schedule underneath. A companion plugin for the parts the WooCommerce API cannot reach — your real checkout shipping calculation, full attribute data, and pushes the moment something changes.
Sites with no shop answer from their pages and posts. Capabilities follow the platform, so the assistant is never offered a lookup it cannot perform.
Your catalogue and pages indexed and searchable. Replies cite what they used, and a reply with nothing behind it becomes a handoff instead of being sent.
Checks stock, quotes your policies, reads a customer's whole order history, rates shipping through your real checkout, builds orders. Never refunds, never cancels, never quotes freight, and never answers something your own content does not cover.
“Is this in stock?” is the commonest thing a chat widget receives. The assistant reads the page the customer opened the chat from, and the pages before it, rather than asking which product they mean.
A handoff with no search behind it is refused and handed back to try again. Refunds, cancellations, freight, discounts and a customer who asks for a person are never delayed by that.
One line of script. Customers always see whether they are talking to a machine or a person, and asking for a human always works, immediately. Unread replies badge the bubble while it is closed.
Your team sees whether a customer is still on the site and which pages they have walked through. If they have gone, the reply is emailed to them instead of sitting in a browser tab nobody will open again.
Forward the address your customers already use. Replies go out through your own mail server, so they arrive from your domain and pass your SPF and DKIM. Several addresses, each replying under its own name. Messages render as the customer wrote them, with the quoted thread folded away.
Grounded replies go out immediately, with the assistant's working attached — which tools ran, how long they took, what they returned. Reject one and say why, and that sentence joins its instructions for your company.
When a person answers something the assistant handed over, closing the conversation keeps that answer in your knowledge base — visible, editable, and with the customer's details left out.
Built in the conversation on your own catalogue prices and your own shipping rates, attached to the customer's account with their addresses on it. Short payment links on your address, and a thank-you when the money actually arrives. Small orders can finish themselves; freight never can.
Conversations, counts and presence update themselves. Chrome notifications when a customer writes while the tab is in the background.
Your timezone and your country's statutory holidays, detected rather than typed in, with separate replies for out-of-hours and for a holiday.
Invite colleagues by email rather than creating their account for them. Roles and permissions are already there; the invitation is not.
Datasheets indexed alongside the products they belong to, so a technical answer can come from the document you already publish.
When the assistant repeatedly cannot answer something, it tells you what page your site is missing — and drafts it.
What the assistant handled, what it handed over, and what it was sent back for — which is the number that tells you whether to trust it more.
A native Mac app and an iPhone app with push for approvals and handoffs. The design is done; the build has not started.
Products, orders and customers, through the same platform seam WordPress and WooCommerce already use.
Per seat, per company. Pricing published before anyone is asked to pay.
Run the customer-facing side on your own domain instead of a Relay Panel subdomain. Certificates issued automatically.
Calls alongside chat and email, on the same customer record, so a conversation that started on the phone is not invisible to everyone else.
One email when signups open. Nothing else.