Skip to main content
AI Voice Agents run through the existing Ringee backend, database, Redis and Temporal worker. There is no separate agent service to deploy.

​
Required infrastructure

Set BACKEND_URL and PUBLIC_BACKEND_URL to the same externally reachable API origin. Ringee writes callback and tool URLs under:
Do not document or manually call the tokenized webhook URLs. Ringee provisions their authorization material and verifies it on every callback.

​
Environment variables

The voice leg also uses TELNYX_API_KEY, normal call margin settings and Ringee’s storage configuration for recovered recordings. Set TELNYX_OUTBOUND_VOICE_PROFILE_ID to pin calls to an explicit Telnyx billing route; if it is omitted, Ringee leaves the provider’s default route in place.

​
Models and BYOK

Self-hosters control the concrete model behind each stable UI choice. Changing a model setting changes what is used the next time an agent is synchronized; the stored agent keeps the provider family, not a user-selected arbitrary model id. OpenAI, Anthropic and Google keys are supplied per agent. Ringee verifies the key, hands it to the voice provider’s secret store and persists only the reference.

​
Cost and artifact reconciliation

The provider can publish call cost, recording and transcript data after the call has ended. Ringee’s scheduled sweep therefore:
  1. binds any missing provider conversation id;
  2. repairs a stalled call timeline from usage records;
  3. settles the AI and telephony costs exactly once;
  4. retries recording and transcript recovery for up to 6 hours.
Keep the Temporal worker running in production. An API-only deployment can place calls but cannot reliably finish cleanup and reconciliation.

​
Production checklist

  • BACKEND_URL and PUBLIC_BACKEND_URL contain the same public HTTPS origin.
  • Telnyx can reach /api/call/webhook and the generated voice-agent callback URLs.
  • When set, TELNYX_OUTBOUND_VOICE_PROFILE_ID belongs to the same provider account.
  • PostgreSQL, Redis and Temporal are reachable by both backend and worker.
  • At least one Ringee number is eligible for AI voice agent outbound use.
  • The maximum call and test-session durations match your risk policy.
  • Credit and call margins are set deliberately.
  • Recording storage and retention follow your consent and compliance policy.

​
Next steps

Configuration reference

All Ringee environment categories

API reference

Build an authenticated integration