Telephony Roadmap
This content is not available in your language yet.
Everything on this page is planned, not available, unless it says otherwise. The order is rough and no dates are promised. For what works today, see the overview.
Making calls feel faster
Section titled “Making calls feel faster”| Item | Status | Needs |
|---|---|---|
| Faster language-model and speech providers | Planned | Provider accounts. Could bring replies toward about 1.7 to 2.0 s (today about 3 to 5 s). |
| Streaming workflow path (first words before the workflow finishes) | Planned | A backend change so replies stream instead of arriving per turn. |
| A media server nearer Malaysia | Planned | None is offered to our project in LiveKit Cloud today (we use India South). A self-hosted server in Malaysia was measured, not offered: from a Malaysian laptop, the round trip through the media server was about 12 to 20 ms in our tests vs about 73 to 77 ms for LiveKit Cloud in India. About 60 ms saved per round trip, small next to today’s reply time. |
The target for a human-feeling call is about 1.5 s. None of these is promised to reach it.
Running it for you
Section titled “Running it for you”| Item | Status |
|---|---|
| Permanent, always-on hosted voice workers (today Wetel runs one for arranged test sessions) | Planned |
| Self-service enable switch per workspace | Planned |
| Per-key daily call caps (one limit per environment, the same for every key) | Done (2026-10-21) |
| A one-time handle instead of a readable session credential in the join token | Planned |
| Cleanup of sessions that were started but never joined | Done (2026-10-21) |
| Call records and per-call reports | Planned. Partly built on the server side, not running for anyone yet |
| Per-call spending limits (longest call, calls at once per workspace, daily and monthly spend) | Planned. Partly built on the server side, not running for anyone yet |
| Live transfer of a call to a person (today the agent offers a callback) | Planned |
Authoring and languages
Section titled “Authoring and languages”| Item | Status |
|---|---|
| Voice-safe workflow starter template | Planned |
| Malay, Chinese, and Malay/English code-switching, on live calls | Planned. Speech for these languages exists for voice messages; live calls have been tested in English only. |
More ways to call
Section titled “More ways to call”| Item | Status |
|---|---|
| WhatsApp calling through your own WhatsApp Business number (Cloud API) | Planned, the agreed direction, in preparation. Not available. |
| Ordinary phone calls over SIP, inbound first, through a licensed telecom provider, including Malaysian (+60) numbers | Planned. Research and planning only: no number, carrier connection or phone-call service exists. Not available. |
| Follow-ups and callbacks for people who have a relationship with you and agreed to be called | Planned, specification stage, after inbound calls. Not available. |
| An AI participant in Google Meet, Zoom or Teams meetings | Research and design only. Platform rules on bots and the consent of everyone in the meeting come first. Not available. |
| A US test phone number for inbound trials | Available for internal trials only: US-only, inbound-only, not offered as a product. |
What we will not build
Section titled “What we will not build”Cold outbound sales calling (calls to people who did not ask to hear from you) and voice cloning of real people. This is a policy, not a gap in the list above. See controls and compliance.
Tell us what to do first
Section titled “Tell us what to do first”The order above changes with what pilots show. Request a test session and tell us which item would block you.