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.
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 itemBefore any of the plans, here is what actually runs right now. The band below is current state, not roadmap.
Filter by area on the left. Each item carries a horizon instead of a date.
Telephony is already built and key-gated. The direction is opening it per deployment; it is not carrying production phone calls today.
Voice engine
The screens are complete and the backend integration is in progress. Next is carrying that integration all the way through.
Care operations
Records and status already collect on one screen. The direction is letting the work that follows finish there too.
Operator console
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
Stepping a capability down with a flag already works. The direction is making it plainer which flag affected which call.
Reliability
Both surfaces read the same pipeline. What remains is reducing the places where they still present differently.
Surfaces
Per-call timings are already collected. How an operator should read them so it actually helps is still open.
Operator console
The no-install browser path exists. Which other ways people genuinely use is something we are still looking at.
Surfaces
Schedules and records already sit on one data flow. Where exactly they should meet to fit real operations is unresolved.
Care operations
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.
What this page leaves out decides it more than what it includes.
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 touchThe record of what already shipped — not what is planned — is the changelog.
Read the changelogWe start from your use case and integration surface and map a path from pilot to production.
Contact sales