Answer the phone.

Pick the one that matches your stack. You can mix — managed for new lines, BYOP for the main number you already advertise.

1. From the dashboard, hit /telephony → Get a phone number.
2. Pick a country, then a city / area code. We surface real-time availability from the carrier; what you see is what's buyable.
3. Click Buy. Behind the scenes that's a single request to POST /api/telephony/managed/purchase-number which registers the number, sets the inbound webhook to point at your agent, and turns SMS on by default.
4. Attach the number to an agent. Each number can only drive one agent at a time; an agent can have multiple numbers (one per country, language, or campaign).

1. From /telephony → Bring your own carrier, paste your Telnyx API key (or Twilio account SID + auth token). We store credentials encrypted, scoped to your account.
2. We test the credentials with a no-op API call. If it fails the UI tells you exactly which scope is missing.
3. Import the existing number using POST /api/telephony/byop/import-number. We read the inbound URL, set it to point at the agent webhook, and note the previous URL so you can roll back.
4. Test the call. The number now answers on your agent; your carrier still bills you.

1. Carrier hits our webhook with the inbound call event.
2. We answer with a media stream — codec is L16 16kHz on both inbound and outbound legs, low latency.
3. STT transcribes turn-by-turn. The RV model generates a response and TTS streams it back token-by-token; the caller hears the first syllable while the rest is still being generated.
4. If the model decides to call a tool (book an appointment, send an SMS, search your knowledge base), we run it server-side and inject the result before the next reply.
5. Either party hangs up; we close the stream, finalise the transcript, charge the call to your usage meter.

Toggle these on the agent's page. Credentials come from your account, never from the model.

• Send SMS — text the caller a follow-up link or confirmation. Sender is your agent's provisioned number.
• Book appointment — Google Calendar or your CRM's scheduling endpoint.
• Search knowledge base — semantic search across documents you've uploaded; agent grounds answers in real content instead of hallucinating.
• Transfer to human — warm handoff to a number you specify, with a brief context summary spoken to the recipient first.
• Create CRM lead / update contact — Odoo, HubSpot, custom REST endpoint.

Most callers use the agent as the fallback, not the primary. Two common patterns:

• Receptionist primary, agent overflow. Forward unanswered calls (after 4 rings or when busy) from your existing line to the agent number. Customers hear a person during business hours, the agent at night and during lunch.
• Agent primary, transfer to human. All calls land on the agent; it transfers to a person for anything its system prompt flags as out-of-scope. Cheaper, more consistent.

Every call ends up under /calls in the dashboard with the full transcript, the tools the agent invoked, the handoff (if any), and the per-minute cost. Recordings are opt-in per agent; off by default for HIPAA-style use cases.