Roadmap

These are intentions, not commitments

There are no dates on this page — no quarters, no target releases. An item may be reordered, moved to another horizon, or dropped entirely, and nothing written here will have been untrue. For what has actually landed, read the changelog.

See every item

What works today

Before any of the plans, here is what actually runs right now. The band below is current state, not roadmap.

  • Now

    Realtime voice in the browser

    A full realtime voice session opens in the browser over WebRTC — no install, and the same pipeline the mobile app runs against.

  • A smartphone resting on a table by a window
    Now

    Native mobile voice

    The mobile app runs the same realtime voice stack, so a change to turn-taking or failover lands on both surfaces.

  • Now

    Korean turn-taking

    Backchannel handling means a listening 네 does not count as the caller handing their turn back.

  • The agent list screen of the operations console
    Now

    Redacted records in the console

    PII redaction runs inline during the call, so what reaches the operations layer is already redacted.

By horizon and area

Filter by area on the left. Each item carries a horizon instead of a date.

  • Next

    Opening the telephony transport per deployment

    Telephony is already built and key-gated. The direction is opening it per deployment; it is not carrying production phone calls today.

    Voice engine

  • Next

    Finishing the backend integration behind the care apps

    The screens are complete and the backend integration is in progress. Next is carrying that integration all the way through.

    Care operations

  • Next

    Carrying post-call follow-up further into the console

    Records and status already collect on one screen. The direction is letting the work that follows finish there too.

    Operator console

  • Next

    Widening what Korean normalization covers

    Numbers, units, and mixed-script text are normalized for Korean speech. Widening that coverage is our layer's work, not a new model.

    Voice engine

  • Next

    Sharpening the tooling around feature flags

    Stepping a capability down with a flag already works. The direction is making it plainer which flag affected which call.

    Reliability

  • Next

    Continuing to close behaviour gaps between web and mobile

    Both surfaces read the same pipeline. What remains is reducing the places where they still present differently.

    Surfaces

  • Exploring

    How an operator retraces the shape of a call

    Per-call timings are already collected. How an operator should read them so it actually helps is still open.

    Operator console

  • Exploring

    Other ways a family joins a call

    The no-install browser path exists. Which other ways people genuinely use is something we are still looking at.

    Surfaces

  • Exploring

    Where regular call schedules meet the operations flow

    Schedules and records already sit on one data flow. Where exactly they should meet to fit real operations is unresolved.

    Care operations

  • Exploring

    How to surface the moment a capability stepped down

    The pipeline degrades a feature rather than dropping the call. When and how to tell an operator that happened is still being worked out.

    Reliability

There are no dates in this list. We cannot say when any of it lands, and we would rather not write down something we cannot say.

How this roadmap is written

What this page leaves out decides it more than what it includes.

  1. No datesWe cannot say when any of this lands. No date is better than one that will not hold.
  2. Built and open are different wordsA capability that is built but key-gated is not live, and the roadmap says so too.
  3. Only the layer we buildThe speech and language models are vendors'. Only what we actually build goes on this page.
  4. The production gate staysNo item on this page moves in the direction of removing the human gate before production.

If what you need is not on this page

Tell us the workflow you have in mind. Deployments are scoped one at a time, so if what you need is missing from this list, that is where the conversation starts.

Get in touch

Want what has actually landed?

The record of what already shipped — not what is planned — is the changelog.

Read the changelog

Want to talk about a deployment?

We start from your use case and integration surface and map a path from pilot to production.

Contact sales