Admin tools
Platform-wide reusable JavaScript tools — same surface as team tools but available to every team.
Platform-wide reusable JavaScript tools — same surface as team tools but available to every team.
An AI-powered panel on top of the Flow Designer that drafts and edits flows from natural-language briefings.
API keys for external systems — primarily WebRTC call tokens. Feature-gated and only visible when API access is enabled for the team.
API server instance scaling and platform-wide request rate limiting.
The /apps/{appId} workspace — a slim overview screen with version history and recent conversations. Most of the app's configuration lives in the Flow Designer.
An app is the top-level container for a Delphi voice product. Almost all of its surface is rendered in the Flow Designer; this page covers what an app is, how to create one, and how to manage the list.
Platform-registered phone numbers — the foundation for PSTN endpoints. Assigned to teams; mapped to server groups; optionally extension-enabled.
The primary tool for debugging and analysing calls — log timeline, recording playback, transfers, token usage, and cost.
Recurring background jobs run by the Tasker service — backups, billing, cleanup, scoring, notifications.
Customizable per-team analytics overview — widgets, timeframe toolbar, and edit mode.
How flows move from a testable draft to a published version that handles live conversations.
Outbound SIP trunks used for transfers — carrier routing, authentication, caller ID, and base-number linking.
Where a session starts — phone (PSTN), web voice (WebRTC), and web chat. Conceptual reference; endpoints are created and edited inside the Flow Designer.
The visual editor where you author every part of a Delphi app — endpoints, providers, conversation nodes, and the AI behaviour that ties them together.
Platform-wide administration — users, teams, base numbers, server groups, SIP trunks, TLS materials, cron schedules, job history. Requires SUPERUSER.
Per-team configuration — members, variables and secrets, header manipulation, API keys, team tools, subscription, notifications. Requires team ADMIN or SUPERUSER.
Platform-wide control of SIP header manipulation — default global configs plus all team-specific configs.
Team-scoped SIP header rules applied to your team's base numbers, separate from platform defaults.
The right-panel editors that open when you click something on the Flow Designer canvas — node inspector, endpoint inspector, flow settings, provider editor, variable catalogue, and version history.
Read-only history of background jobs — status, attempts, results, and errors.
Plan, usage, billing, plan management, overage limits, and legal documents.
The sidebar, header bar, global search, and user-settings drawer that frame every TelWeb page.
Every node type rendered on the Flow Designer canvas — conversation nodes that run at call time and virtual nodes that explain the surrounding plumbing.
Email notification types, templates, recipients, severity, and rate limits used for operational alerting.
System-generated team notifications — usage thresholds, subscription lifecycle, billing, and account events.
TLS certificates and keys for mTLS on SIP trunks — CA certs, client certs, client keys stored in AWS Secrets Manager.
Provider concept reference — what providers are, where they live, and the catalogue of supported services.
Two-level role model — system role on the user, team role per membership — and the permission matrix that flows from it.
Pools of voice processing servers — load balancing and auto-scaling controls.
Log in, register, reset your password, and complete welcome setup.
Inbound SIP trunks — identification, authentication, media, TLS / mTLS, and how trunks run in parallel.
View and edit the flow definition as JSON. The same definition is portable across apps and environments.
The Team tab — team identity, base numbers, AWS Secrets Manager, and call recording configuration.
Reusable JavaScript tools shared across multiple agents in the team, with versioning and centralized updates.
Manage who belongs to the team and what role they have.
Platform-wide user and team management. Distinct from per-team Settings → Users.
Team-scoped key/value pairs — PLAIN_TEXT in Postgres or SECRET in AWS Secrets Manager — referenced from agent instructions and tool code.
Find your way around the Delphi user guide. Pick the persona that matches what you're doing — first-time user, day-to-day builder, team admin, or platform admin.