Roadmap
A roadmap is only worth reading if it admits what is missing. This one is a list of gaps, not ambitions, and each gap is also named where it matters on the rest of this site: the security page, the quickstart and the integrations page. There are no dates, because a date invented to make a page look decisive is worse than an order we can defend.
Next
Being worked on now.
-
Signed visitor identity
So a custom tool can safely return one person's details. Today a shopper's signed-in state comes from the store unsigned, which is why order lookups ask for an order number and an email or phone.
-
Live stock and an in-chat cart on Shopify
Shopify is not available yet; it is next on the roadmap. When it lands it will do what WooCommerce does today: live stock, options and a cart handed to your checkout.
-
Automatic retention
Conversations older than your retention setting are removed when you press purge; this will run on its own.
-
Per-role server-side enforcement
Roles are recorded and shown throughout the console, but enforcement lands with SSO. Until then an admin should treat editor access as trusted.
-
An OpenAPI document
The API reference is specified as generated from one. Writing the reference by hand instead would drift within weeks.
Later
Committed, not started.
-
External penetration test
Named as absent on the security page. Scheduled before general availability, and we will publish the summary letter.
-
SOC 2 Type II
Named as absent on the security page. Planned once the platform leaves early access. We will publish the observation window when an auditor is engaged, rather than announcing an intention.
-
A VPAT
None of the ten platforms we assessed publishes one, but public sector procurement asks for it and its absence is a gap regardless of company.
-
The remaining comparison pages
Seven of ten platforms are not yet written up, because we have no verified facts for them and would rather publish nothing than a template.
Not planned
So you can rule us out quickly.
-
Inventing proof
No customer counts, resolution rates or revenue figures until the product measures them.
-
Multi-channel
No email, WhatsApp, voice, SMS or social. This is a website widget, and platforms built as help desks do that job better.
-
Ticketing
No ticket creation in Zendesk, Freshdesk or Intercom. A handover is a person replying in the console.
-
Magento, BigCommerce
The commerce work here is WooCommerce-specific. A crawl still answers content questions on any platform, but there is no live price, no stock and no cart.
-
Self-hosting
Not supported, and not documented for that reason.
Recently done
Items leave this page when they ship, and the changelog records the date. Recently that included the conversation following a shopper across pages, the chat filling the screen on phones, sign-up, log-in and plan buttons inside the chat, and the ability to delete a single conversation from the console. Each was on a list like this one before it was built.
What does not appear here
Features we have not committed to building, and anything we would only build for one customer. A roadmap that lists everything anyone has asked for tells you nothing about what will happen next. This one lists only what is missing from the product as it stands, and in the order we intend to build it, so that you can plan around it.
Asking for something
Tell us what is missing and what it would change for your store. The more specific the example, the easier it is to judge where it belongs in the order.
How this list is ordered
By what stops a store from putting the assistant live, then by what stops it working well. If something missing here is blocking your decision, tell us: requests from stores that would go live move items up.
Something here decides your purchase?
Tell us which. It changes the ordering more reliably than anything else does, and shipped items move to the changelog with the reason behind them.