Zyra
Zyra
Login
Conversations

SIP Telephony: Twilio, Exotel and Plivo: Keep your phone carrier. Put it behind the same inbox.

Not every call should go over WhatsApp. Connect the SIP provider you already pay — Twilio, Exotel, Plivo or a generic trunk — and Zyra bridges customer to agent over it, while the call still lands on the same contact and the same lead as everything else.

All features
Best forExisting telecom contractsOutbound diallingLandline customers
Inbound call — Exotel, sales line
1Customer dials your landline+91 80 4718 2200
2Your Exotel trunk receives itProvider: EXOTEL · last test passed
3Zyra matches the number to a contactPriya Nair · lead #1047
4Agent rings, then bridgesRINGING_AGENT → BRIDGED

The bridge state lives on the call record, not buried in a carrier dashboard.

What you get

01

Four provider shapes

Twilio, Exotel and Plivo have their own adapters. Anything else goes through the generic SIP configuration.

02

Bridged calls, tracked

Ringing the agent, ringing the customer, bridged, no answer, failed — on the call record where you can report on it.

03

A trunk per number

Each WhatsApp channel can point at its own SIP config, so a regional number uses a regional carrier.

04

Test before you trust it

The last test result, message and timestamp are stored on the config. You are not guessing whether credentials still work.

How it works

  1. 1

    Add the provider

    Settings › Integrations › SIP. Pick the provider, paste credentials, set a caller ID.

  2. 2

    Run the test

    Zyra records whether it passed, when, and what came back if it did not.

  3. 3

    Point a number at it

    Assign the config to a channel. Calls on that number bridge over your trunk.

Is this for you?

Businesses with a carrier contract they are not giving up, an outbound dialling operation, or customers who still expect a normal phone call.

If something you need isn't on this page, ask on the call. We'd rather tell you no than have you find out in month two.

The specifics

  • Twilio, Exotel, Plivo and generic SIP
  • Per-provider webhook secret and caller ID
  • Bridge state: ringing agent, ringing customer, bridged, no answer, failed
  • Credentials encrypted at rest and masked in the UI
  • Owner-only, separate from day-to-day calling
  • SIP calls feed the same Call Intelligence pipeline

Twenty minutes, and you'll know.

We'll set it up against your own number and your own questions, so you decide with something real in front of you rather than a slide.