Feature map
The feature map is a second way into the handbook. Start from a feature family when you know what the product should do but not where the setting lives. Start from the configuration finder when you know the level, such as a team setting or a container variable. The glossary explains product terms, and the A–Z index lists every feature by name.
Availability: Next. Features that need an optional deployment feature, a role or a module say so in their entry.
Feature families
| Family | What it covers |
|---|---|
| Calls and call lifecycle | How an inbound call is answered, how long it may run, what ends it, how the end reason is reported over SIP and where the finished call is recorded. |
| SIP signalling and telephony edge | The SIP edge that carriers connect to, the methods, transports, timers and responses it supports, how it hands calls to the voice service and how SIP traffic is captured for diagnosis. |
| SIP trunks, numbers and routing | Connecting carriers through inbound and outbound SIP trunks, choosing outbound routes, managing base numbers and extensions, and keeping trunks healthy and in maintenance when needed. |
| SIP headers and call data | Which SIP headers arrive with a call, how flows and bots read them, how the edge rewrites them and which headers the application can send when it ends or transfers a call. |
| Call transfers | Handing a live call to another number or SIP destination, with the transfer method, target rules, headers, notifications and the result the application sees. |
| DTMF | Keypad input on voice calls, from how digits travel over SIP to collecting them in a flow, forwarding them to a bot and sending them onward. |
| Media, audio and speech | How call audio is encoded, cleaned and detected, which prepared audio plays to callers, how synthesized speech is cached and which speech providers, voices and languages a call uses. |
| AI providers and models | Which speech, language and realtime AI services a flow can use, how their credentials are supplied, and which choices depend on the plan or on optional deployment features. |
| Resilience, retries and fallbacks | How a call survives slow or failing AI services, from provider retries and alternate speech providers to caller feedback while waiting and ordered final actions, with defaults that teams and flows can override. |
| Flows and the flow builder | How applications and their conversation flows are built, from steps, transitions and data to templates, tools, the AI-assisted builder, drafts and publication. |
| Browser and SDK | Connect browser text and voice clients, issue session tokens, recover connections and use the matching SDK contract. |
| HTTP API | The TelAPI HTTP interface for integrations, from team API keys, scopes and request limits to authentication, errors, paging, health probes and the OpenAPI description. |
| Recordings, transcripts and data privacy | What a call leaves behind and how it is protected, from choosing recording outputs and storage to retention, transcripts, sensitive-turn protection and deleting stored audio. |
| Accounts, teams and access | Who can sign in and what they may do, covering sign-in methods, sessions and passwords, platform and team roles, user provisioning, team setup, shared variables and secrets, personal preferences and interface languages. |
| Plans, usage, notifications and SMS | How a team subscribes, what its plan includes and how usage is billed, from self-service registration and Stripe payments to usage alerts, in-app notifications, email delivery and SMS. |
| Logs, traces and monitoring | How the platform records what happened on a call or in a service, where logs and traces are collected, how operators search them, and which dashboards, alerts and health checks watch the deployment. |
| Scaling, capacity and high availability | How voice, API and edge capacity is grouped, scaled, limited and balanced, how services are drained for maintenance, and how the platform stays available when an instance or edge fails. |
| Security, TLS and network | How signaling, media, web traffic and internal connections are encrypted, where certificates and secrets live, which outbound traffic leaves through the proxy and which ports and sources the platform accepts. |
| Deployment and operations | What a self-hosted deployment needs, how hosts are provisioned and configured, which variables each service reads, and how operators update, schedule, back up and recover the platform. |
| Quality, dashboards and analytics | How teams judge and measure their apps, from automatic conversation scoring and reviewing single conversations to dashboards, reporting periods, satisfaction metrics and platform-wide usage figures. |
Other ways to browse
- Configuration finder: every control grouped by level and by reader role, to see what you can change from where.
- Glossary: product terms, to understand a word in a setting or log line.
- A–Z index: all features alphabetically, to jump straight to a known name.
- The task sections Use Delphi, Administer, Operate and Integrate, to follow a complete procedure from start to verification.