MICROSIVE

Telnyx voice integration for software that places calls

When your reps call from a browser and your software decides who gets dialed, the phone line becomes part of the build. Our own dialer runs its US lines on Telnyx.

Reviewed by: Rahul Jaiswar, founder

What Telnyx is

Telnyx is a telephony provider with phone numbers, programmable voice, SIP trunking and browser calling over WebRTC. Software starts and controls the calls through its API, and Telnyx reports every call event back by webhook.

Do you need a voice API, or just a phone system?

A voice API is worth it when your own software decides what happens on a call: which lead is dialed next, what the rep sees while they talk, where the notes and the recording end up, what a call cost. If your team only needs extensions, voicemail and a call queue, an off-the-shelf business phone service is simpler and cheaper.

How we use it

Microsive Dialer, the calling system our own sales team uses, runs its US numbers on Telnyx, including call recording and the provider’s cost for each call. Reps call from the browser and the server connects both sides.

When it fits

  • Reps working from laptops with no desk phones, in an office or at home.
  • Calling that is driven by your own data: a call list, a follow-up date, a load that needs covering.
  • Managers who want each call’s provider cost sitting next to its outcome.

When it doesn’t

  • A handful of phones and no custom software: an off-the-shelf business phone service does that job.
  • AI calls with no reps involved: start from the voice agent build and choose telephony after (AI voice agents).
  • Numbers outside the United States: which provider fits depends on the country, and that is decided per project.

Who owns the numbers

Phone numbers and calling accounts sit in a provider account. Before a build, agree whose account that is and what happens to the numbers if you change vendors. For our dialer, numbers are bought in the client’s own provider account, and an existing number can be ported, with the timing in the carriers’ hands rather than ours.

Four questions for your build team

  1. How is cost per call worked out from the provider’s events?
  2. Where are recordings stored, and who can play them?
  3. What happens when an inbound call gets no answer?
  4. How are Telnyx webhooks checked before the app acts on them?

Telnyx signs its webhooks. Verify that signature before a call event changes any record, because anyone who finds the webhook address can send fake events.

Planning inbound calls

Decide what happens when a customer calls back and no rep answers: another rep’s browser rings, the caller leaves a message, or the call becomes a callback task for whoever owns that account. Decide too which rep owns a returning caller. Test inbound calls from a real phone on another carrier, not only outbound ones.

Pitfalls

  • Cost arrives late and in parts. Telnyx sends cost as its own event after hangup, one per billed leg. A bridged call has two legs, so the costs are added together, never overwritten.
  • Billed time differs from talk time. Minimum billing increments mean a report should label the two separately.
  • SIP URI calls to browser users are off by default. A credential connection rejects calls to a browser user until SIP URI calling is enabled, and the hangup reason can read like a busy line. Check the raw SIP response before debugging the browser.

Related

Building calling into your own software?

Say how many reps call, and whether calls go out, come in or both. Someone from our team replies within one business day.