Three baskets instead of quarterly dates. The order inside each is set by questions from deployments, so signing up for a notification is also a vote.
No dates · no promises we cannot keep · order decided by customer votes
Things we are building now. We give no dates, because we would have to invent them.
An AI coworker inside the company, for the team rather than for end customers. Slack has been running in our own workspace since 2 September 2026, and Teams is built and waiting to be switched on. Before we open either one to customers, we give at least thirty days notice of a new subprocessor.
See the Ada previewWe know we will build these. We do not yet know in which order, and this is where your votes weigh most.
The channel customers reach for first, wired into the same conversation inbox.
Notify me about WhatsAppMessages from your company page arriving in the shared queue, without a separate tool.
Notify me about MessengerThis basket is real, not decorative. A vote here can move an item up, but by itself it is not a commitment on our side.
Direct messages served from the same knowledge base as every other channel.
Vote for InstagramReady connectors to common shop platforms and support tools, instead of writing your own.
Vote for integrationsTelephony. The channel has been working since 1 September 2026, confirmed by a real call in both directions, so it is no longer in the closest basket. The description and the caveats now sit with the channels. We write it here instead of quietly taking the card down.
A basket says how close the decision and the work are, not which month something appears in.
Signing up is a sign up for one specific thing. That tells us not only how many are waiting, but who is waiting for what.
An item that entered the closest basket does not drift back to considering in silence. If we change our mind, we will say so.
One sentence from you weighs more than an hour of our guessing. Tell us what would unblock a deployment on your side.