Roadmap

What exists, what is being built, and what is not going to happen

This is the working list, not a brochure. Everything under Shipped is running on a real store answering real customers today. The rest is named plainly — including three things that are never getting built, because a roadmap you cannot plan against is worth less than none.

19Shipped
2Being built
9Next
Shipped

Running today, on a live store

Each of these is in daily use. What they do for you is on the features page; this is the checklist.

Being built

In progress right now

Push, seen arriving

The server half is built and verified — the key signs, the route works, tokens register. What is left is watching one land on a phone from a TestFlight build rather than a cable, and the difference between those two is a real one worth checking.

Sending mail as Relay Panel

Every sender today is a merchant's own verified domain, which is right for replies and means the platform itself has nowhere to send from. Needed before the waitlist can be written to, and it needs an unsubscribe link, which for commercial mail to Canadian addresses is the law rather than a nicety.

Next

In the order it would be done

Spec sheets and PDFs

Indexing datasheets alongside the product they belong to. The single biggest gap for a technical catalogue — the answer is often only in the PDF.

Learning without being closed

Distillation fires when somebody presses Close, so a thread nobody ever closes teaches nothing, and on a busy desk that is most of them. A sweep over quiet handed-over threads closes the last hole in the loop.

Reporting

Handled, handed over, and sent back for correction. The last number is the one that says whether to trust it more. SLA reporting of the kind Zendesk does is not here and is not close.

Text messages

voip.ms publishes a webhook for SMS — unlike voice — so a text would arrive as a conversation like any other and be answered from the same knowledge.

Instagram, WhatsApp and Messenger

Planned, and after text messages rather than instead of them — a direct message is the same shape of work: a conversation on a channel, answered from the same knowledge, in the same inbox. Each one is somebody else's API and its own approval to get, so this is several pieces of work rather than one. Not started, and it is a real gap today.

Voicemail, pushed

Voicemail-to-email fires the moment somebody hangs up, which turns “a missed call appears within ten seconds of the next poll” into “a voicemail appears as it is left, with the audio”.

Self-serve signup and billing

The point at which a merchant nobody has met can sign up on their own.

Custom domains

support.yourstore.com instead of a Relay Panel subdomain. The certificate handling and the domains table are already built for it.

Shopify

Store platform is already a first-class concept internally, so this is an adapter rather than a rewrite. Not started.

Not happening

Three things we are not going to build

Each one is somebody's deciding factor, so it is better said here than found out later.

A screen-pop while the phone is ringing

voip.ms publishes no webhook for voice and no live-call endpoint — the only way to learn a call happened is a log written after the caller hangs up. That makes this very good at “you missed a call from a real customer” and structurally incapable of ringing your screen. It would take a different provider, not more work here.

An AI that closes conversations on its own

Deflection is not the goal. The assistant exists so your team answers in two minutes instead of two hours, not so your team answers less.

Want one of the next ones sooner?

The order is not fixed. Join the waitlist and say which one matters to your store — that is most of how this list gets reordered.