Twilio Voice logo

Twilio Voice

The building block every other dialer is built on, sold to you raw

Twilio Voice is a programmable voice API rather than a phone product: developers buy phone numbers from about $1.15 a month, place and receive calls at published per-minute rates from $0.0140 outbound and $0.0085 inbound in the US, and control call behaviour with TwiML, REST APIs, and WebRTC SDKs for JavaScript, iOS, and Android, with metered add-ons for recording, transcription, answering machine detection, branded calling, and conversational AI, all self-serve on pay as you go with no contract.

Visit website

Overview

Twilio Voice is not a product a sales team can use. It is the layer underneath the products a sales team uses. When a dialer vendor tells you they have local presence, answering machine detection, and call recording, there is a meaningful chance that what they actually have is a Twilio account, an application layer, and a markup. That is worth stating plainly at the top of a directory aimed at small businesses, because Twilio's pricing looks dramatically cheaper than every dialer in this category and the comparison is not a fair one.

What Twilio sells is telephony as a programmable resource. You buy a number, you point it at a URL, and when someone calls that number Twilio sends an HTTP request to your application, which responds with TwiML telling Twilio what to do: say something, gather a keypress, dial another number, record, transcribe, bridge into a conference. Outbound is the same in reverse. The Voice SDKs put the same capability inside a browser, an iOS app, or an Android app over WebRTC, which is how a web application ends up with a click-to-call button that actually places a real PSTN call.

The commercial model is pure metering and it is honest about it. US outbound to local numbers is $0.0140 a minute, inbound to a local number is $0.0085, inbound to toll-free is $0.0220, browser or SDK legs are $0.0040, and SIP interface legs are $0.0040 in both directions. Local numbers rent for $1.15 a month and toll-free for $2.15. Recording is $0.0025 a minute plus $0.0005 a minute per month of storage, transcription is $0.0500 a minute, answering machine detection is $0.0075 a call, and branded calling is $0.12 a call. Every one of those is a line on your bill and every one scales with usage.

Twilio itself is a public company (NYSE: TWLO) founded in 2008 by Jeff Lawson, Evan Cooke, and John Wolthuis, with a customer base running from two-person startups to Uber and a compliance and carrier footprint in over 100 countries. It is not going anywhere, the documentation is the best in the industry, and the free trial credit lets you build something real before spending money. The catch is the one this entire dossier keeps returning to: buying Twilio means committing to build and maintain software. If nobody on your team writes code, the correct entry in this category for you is a dialer or a phone system, not an API.

Best for

Software teams building calling into their own product: a SaaS company adding click-to-call and recording, a marketplace masking phone numbers between buyers and sellers, an agency building a bespoke IVR, or a technical startup that has outgrown a boxed dialer and wants control over routing, concurrency, and data.

Not the right fit for

  • Any small business without a developer. There is no dialer interface, no agent console, no CRM integration, and no admin panel for a non-technical user; buying Twilio without engineering capacity means buying a bill and no product.
  • Sales teams who want to start calling next week. Everything a dialer gives you out of the box (call lists, dispositions, local presence rotation, voicemail drop, coaching, reporting) is something you would be building, and building it properly takes months.
  • Budget buyers who read the per-minute rate and stop there. Fully loaded with recording, storage, transcription, AMD, and branded calling, a heavy outbound minute costs several times the headline $0.0140, and none of that includes your engineering time.
  • Teams that need predictable monthly costs. Everything is metered, so a bad month of dialing produces a bad invoice with no ceiling, unlike a per-seat plan where domestic minutes are free.
  • Buyers who want a single vendor to hold accountable for call quality and compliance. With Twilio you are the telephony provider from your customers' point of view, which means TCPA exposure, consent capture, DNC scrubbing, and recording notification are entirely your engineering problem.

How it works

  1. 1

    You sign up self-serve, receive trial credit, and buy a phone number from the console or the API. Local, toll-free, and international numbers of more than 230 types are available, with local numbers at $1.15 a month and toll-free at $2.15 in the US.

  2. 2

    You point that number at a webhook URL. When a call arrives, Twilio POSTs the call details to your application and expects TwiML in response: an XML document saying play this audio, gather these digits, dial this number, record this call, connect to this conference. Your application decides everything, which is both the power and the labour.

  3. 3

    For outbound, your application calls the REST API to create a call, supplying a from number, a to number, and either a TwiML URL or inline instructions. This is the primitive that a power dialer is built from: your code decides who to call next, how many concurrent calls to place, whether to drop a voicemail, and what to do when a human answers. Twilio supplies none of that logic.

  4. 4

    The Voice SDKs for JavaScript, iOS, and Android put a WebRTC endpoint in your own application so an agent can talk through a browser rather than a handset, at the cheaper $0.0040 per minute SDK leg rate. Around all of this sit metered services: call recording and encrypted storage, real-time and post-call transcription, Conversational Intelligence for extracting insights from calls, Voice Insights for call quality monitoring, answering machine detection, Trust Hub for STIR/SHAKEN and CNAM registration, and Branded Calling for displaying your name, logo, and call reason on supported mobile devices.

Feature breakdown

24 features in 4 modules

Programmable calling

The core primitives, and the reason the whole category exists.
TwiML call control
An XML instruction set returned by your webhook that tells Twilio what to do on a live call: say, play, gather, dial, record, enqueue, conference, redirect. Simple enough to learn in an afternoon and expressive enough to build a full IVR.
REST Voice API
Create, modify, and terminate calls programmatically, which is the primitive underneath every power dialer and parallel dialer. Concurrency, pacing, and retry logic are yours to write.
Voice SDKs for browser and mobile
JavaScript, iOS, and Android SDKs put a WebRTC softphone inside your own application, billed at the cheaper $0.0040 per minute SDK leg rate rather than a PSTN leg on both sides.
Elastic SIP Trunking
Connect an existing PBX or contact centre to Twilio's global PSTN with elastic capacity and no channel commitments, at $0.0040 a minute in each direction, which is the cheapest way to move minutes if you already own the call control layer.
Conferencing
Multi-party conferences up to 250 participants with per-participant per-minute billing from about $0.0018, plus moderation, muting, and recording controls.
Number masking and proxy calling
Connect two parties without revealing either number, which is the standard pattern for marketplaces, delivery platforms, and any business that brokers contact between strangers.
230-plus number types in 100-plus countries
Local, national, toll-free, and mobile numbers across a very wide footprint, with regulatory address and documentation requirements enforced per country.

Recording, transcription, and intelligence

Available, powerful, and metered on every axis.
Call recording
$0.0025 per minute to record plus $0.0005 per minute per month to store, with encryption at rest available. Cheap per unit and easy to forget about until a year of recordings is accruing storage charges every month.
Transcription
$0.0500 per minute, which is twenty times the cost of the recording itself and is the single line most likely to surprise a first-time buyer. On a 12,600 minute month, transcribing everything costs $630.
Conversational Intelligence
Extracts summaries, sentiment, entities, and custom operators from call transcripts at scale, priced separately per minute. This is the layer that competes with dedicated conversation intelligence products.
ConversationRelay
Connects a live call to a large language model with low-latency streaming speech in both directions, which is the supported path for building an AI voice agent on Twilio rather than gluing services together yourself.
Answering machine detection
$0.0075 per call to determine whether a human or a machine answered, which is the primitive behind voicemail drop and predictive dialing. Note that it bills per call attempt, so a low-connect outbound campaign pays for it on every dial.
Voice Insights
Real-time and historical call quality metrics (jitter, packet loss, MOS) so you can diagnose why a specific call sounded bad, which is something almost no boxed dialer exposes.

Trust, deliverability, and caller reputation

Genuinely strong, and the part most buyers underestimate.
Trust Hub and STIR/SHAKEN
Register your business identity and numbers so outbound calls carry proper attestation rather than travelling through a wholesale route unsigned. This is the difference between calls that get answered and calls that show up as Scam Likely.
CNAM registration
Register the caller ID name displayed on US calls so recipients see your business rather than a bare number.
Branded Calling
$0.12 per call to display your company name, logo, and stated call reason on supported mobile handsets. Expensive per call, and on a 6,300-call month it is $756, so it belongs on high-value calls rather than on a cold list.
Voice Integrity and spam remediation
Monitoring of how carriers are labelling your numbers plus a remediation path when a number gets wrongly flagged, which is a real operational service rather than a checkbox.
Regulatory compliance tooling
Regulatory bundles for number provisioning in countries that require local address or business documentation, enforced at purchase time so you do not accidentally buy an unusable number.

Developer platform and operations

The best documentation and tooling in telephony, by a distance.
Helper libraries in every mainstream language
Official SDKs for Node.js, Python, Java, C#, PHP, Ruby, and Go, plus a CLI, which is why a competent engineer can place their first programmatic call within an hour of signing up.
Twilio Functions and Studio
Serverless functions for hosting TwiML logic without running your own server, and Studio, a visual flow builder for IVRs that a technical non-developer can operate.
Webhooks and event streams
Call status callbacks, recording callbacks, and an event streaming product for piping call events into your own data warehouse.
Subaccounts
Isolated subaccounts with their own numbers, usage, and billing rollup, which is the standard pattern for agencies and platforms reselling calling to their own customers.
Console, logs, and debugger
Per-call logs, error debugging, and usage dashboards, which matter enormously when a call fails at three in the morning and you need to know whether it was your code or the carrier.
Twilio Flex
A separately licensed programmable contact centre built on the same voice platform, for teams that want an agent interface without building one, priced per hour or per seat rather than per minute.

Use cases

4 documented

SaaS product team adding calling to their application

Customers want to call contacts from inside the product, with recording attached to the record, and no engineer wants to become a telecom carrier to make it happen.

The JavaScript Voice SDK puts a softphone in the app at $0.0040 per SDK leg, the REST API places the PSTN leg at $0.0140, recordings attach to the customer record, and the whole thing ships in weeks rather than quarters.

Marketplace masking numbers between two parties

Buyers and sellers need to speak, neither should get the other's real number, and the platform needs a record that the conversation happened.

Proxy numbers bridge the two parties, the platform holds the mapping, recordings and call logs stay on the platform's side, and the numbers are recycled when the transaction closes.

Technical sales operations team that outgrew a boxed dialer

The dialer vendor charges per seat, will not expose the data the team needs, and cannot implement the specific pacing and routing logic the business runs on.

The team rebuilds the dialing layer on the Voice API with their own concurrency and pacing, uses answering machine detection at $0.0075 a call for voicemail drop, and pays metered rates instead of per-seat, accepting that they now own the maintenance.

Agency building a bespoke IVR for a client

The client's routing rules are too specific for an off-the-shelf phone system: routing by account balance, by language, by time zone, and by data pulled live from a back-office system.

Studio and TwiML express the flow, Functions host the logic without a server, and the agency bills the build rather than reselling a subscription.

Pricing

from $1.15 per month per local US number, plus $0.0140 per outbound minute

Pure pay as you go metering with no subscription and no contract: monthly rental per phone number, per-minute rates per call leg that vary by direction, number type, and whether the leg is PSTN, SIP, or SDK, plus separate per-minute or per-call charges for recording, storage, transcription, answering machine detection, branded calling, and AI services.

PlanPriceIncludes
Pay as you goMetered
per minute, per number, per event
  • US outbound to local numbers: $0.0140 per minute
  • US inbound to a local number: $0.0085 per minute
  • US inbound to a toll-free number: $0.0220 per minute
  • Browser and mobile SDK legs: $0.0040 per minute
  • Local number: $1.15 per month; toll-free number: $2.15 per month

The default and only self-serve tier. No minimum spend, no contract, and no seats.

Elastic SIP Trunking$0.0040 per minute in each direction
metered
  • Connect an existing PBX or contact centre to the PSTN
  • No channel commitments and elastic capacity
  • Cheapest per-minute path if you already own call control

This is the rate that makes Twilio attractive as a wholesale minute supplier rather than as an application platform.

Committed use and volume pricingNegotiated
annual commitment
  • Volume discounts on minutes, numbers, and add-on services
  • Committed-use agreements for predictable large spend
  • Enterprise support and account management

Not published and not relevant to a small business; this is where large customers land after their metered bill becomes a budget line.

Add-ons

  • Call recording ($0.0025 per minute): Plus $0.0005 per minute per month for storage, which accrues indefinitely.
  • Transcription ($0.0500 per minute): Twenty times the cost of recording; the most common bill shock on the platform.
  • Answering machine detection ($0.0075 per call): Billed per attempt, including calls nobody answers.
  • Branded Calling ($0.12 per call): Displays name, logo, and call reason on supported handsets. Reserve for high-value calls.
  • Conferencing (From $0.0018 per participant per minute)
  • Alaska outbound ($0.0945 per minute): A reminder that within-US rates are not uniform.
  • Conversational Intelligence and ConversationRelay (Separately metered per minute): The AI layers are priced on their own product pages and are not included in the voice rate.

Billing notes

  • Everything is metered and nothing is bundled. There is no seat price, no included minute pool, and no monthly ceiling, so a runaway loop in your own code produces a real invoice.
  • Rates differ by leg. A browser-to-PSTN call bills the $0.0040 SDK leg and the $0.0140 PSTN leg, so the true per-minute cost of a call is the sum of its legs rather than one published number.
  • US rates are not uniform: Alaska outbound is $0.0945 a minute, roughly seven times the standard rate, and international destinations vary by orders of magnitude with mobile termination usually far above landline.
  • Recording storage accrues every month for as long as you keep the audio. It is $0.0005 per minute per month, which is trivial in month one and a standing line item by year three unless you set a retention policy.
  • Transcription at $0.0500 per minute is the outlier. Transcribing 12,600 minutes a month costs $630, which is more than most per-seat phone systems would charge the same team for everything.
  • Volume and committed-use discounts exist but are negotiated, so the self-serve price is the list price and small buyers pay it.
  • None of these figures include your engineering cost, which for a production dialing application is by far the largest number in the total cost of ownership.

Value assessment: Twilio is extraordinarily cheap as telephony and expensive as a product, and confusing the two is the single most common mistake buyers make. Work the numbers for the three-person team in this category's standard scenario: 6,300 calls a month at two minutes each is 12,600 outbound minutes, which is $176.40 at $0.0140, plus three local numbers at $3.45, plus recording at $31.50, plus answering machine detection at $47.25 on 6,300 attempts. That is roughly $259 a month before transcription, which would add $630 if you transcribed everything. Against a per-seat dialer at $65 a seat, or $195 for three, Twilio is not obviously cheaper once you turn on the features a dialer includes, and it comes with none of the interface, the CRM integration, or the reporting. The real value of Twilio appears when calling is a feature of software you already sell, or when your call volume and routing logic are strange enough that no vendor's product fits. For a small business that simply wants its reps to make calls, this is the wrong purchase at any price.

Strengths & limitations

Strengths

  • The best developer experience in telephony: TwiML is genuinely simple, the documentation is exemplary, helper libraries exist for every mainstream language, and a competent engineer places their first programmatic call within an hour.
  • Complete transparency on price. Every rate is published per minute, per number, and per event, with no seat pricing, no minimum, no contract, and no sales conversation required.
  • Carrier footprint and redundancy in over 100 countries with 230-plus number types, which is a scale of global reach no small-business phone vendor approaches.
  • A serious trust and deliverability stack: Trust Hub, STIR/SHAKEN attestation, CNAM registration, Voice Integrity monitoring, and Branded Calling with logo and call reason on supported handsets.
  • Elastic SIP Trunking at $0.0040 a minute in each direction is one of the cheapest legitimate ways to move minutes if you already own the call control layer.
  • Voice Insights exposes per-call quality metrics that boxed dialers hide, which turns call quality complaints from an argument into a diagnosis.
  • A public company with more than fifteen years of operation, an enormous customer base, and an ecosystem large enough that hiring an engineer who already knows Twilio is easy.
  • ConversationRelay gives a supported path to building a real AI voice agent rather than stitching a speech pipeline together yourself.

Limitations

  • It is not a product. There is no dialer, no agent console, no CRM integration, no call list management, no dispositions, and no reporting a sales manager would recognize.
  • Costs are unbounded and unbundled. Every feature is a separate meter and a coding error can produce an invoice with no ceiling.
  • Transcription at $0.0500 a minute is dramatically more expensive than recording and prices whole-corpus transcription out of reach for high-volume teams.
  • You become the telephony provider in your own product, which means TCPA compliance, consent capture, DNC scrubbing, recording notification, and call quality are your engineering responsibility rather than a vendor's.
  • Answering machine detection bills per attempt at $0.0075, so a cold campaign with a low connect rate pays for detection on every unanswered dial.
  • Twilio's price increases and product deprecations over the years have been real, and building a business on a metered platform means accepting future rate changes you do not control.
  • Support at the self-serve tier is documentation and tickets; genuinely responsive support is a paid plan, which is a meaningful cost for a small team running production calling.
  • Regulatory number provisioning in many countries requires local address and business documentation, which is a real administrative burden when expanding internationally.

Head-to-head comparisons

5 alternatives

Twilio Voice vs Telnyx

from $0.002 per minute on Call Control plus SIP trunking, with numbers from $1 per month

Telnyx is the closest architectural equivalent and competes primarily on price and network ownership: it operates its own private IP network and licensed carrier infrastructure rather than aggregating other carriers, and its published elemental rate of $0.002 a minute plus a SIP trunking fee undercuts Twilio's $0.0140 for comparable US calling. Twilio wins decisively on documentation, ecosystem, tooling, and the number of engineers who already know it. Choose Telnyx if minute cost and network control dominate; choose Twilio if developer velocity and hiring do.

Full Twilio Voice vs Telnyx comparison

Twilio Voice vs Plivo

from $0.50 per month per US local number, plus $0.0115 per outbound minute

Plivo is the deliberate value alternative: $0.0115 outbound and $0.0055 inbound in the US against Twilio's $0.0140 and $0.0085, local numbers at $0.50 against $1.15, free call recording against $0.0025 a minute, and transcription at $0.0095 against $0.0500. On a high-volume US calling workload Plivo is meaningfully cheaper across the board. Twilio counters with a far broader platform, better documentation, deeper AI and trust products, and a much larger ecosystem. For pure US voice minutes, Plivo. For building a product, Twilio.

Full Twilio Voice vs Plivo comparison

Twilio Voice vs Kixie

from About $35 per user per month (reported; not published by the vendor)

These are not the same kind of thing, which is exactly why the comparison matters. Kixie is a finished sales dialer with power dialing, local presence, CRM integration, and a manager's dashboard, sold per seat. Twilio is the raw material such a product is built from. If your team wants to start dialing on Monday, buy Kixie. If your team wants to build the dialing experience into your own software and control the data, buy Twilio and budget engineering time, because you are choosing to build what Kixie sells.

Full Twilio Voice vs Kixie comparison

Twilio Voice vs CloudTalk

from 19 euros per user per month billed annually (27 euros monthly)

CloudTalk sells numbers in 160-plus countries, four dialer modes including a ten-line parallel dialer, branded caller ID, and spam remediation, from around 19 euros a seat with dialers as paid add-ons. Twilio gives you cheaper minutes and total control but no dialer modes, no agent interface, and no spam remediation service you do not configure yourself. CloudTalk is a product for a sales team; Twilio is infrastructure for an engineering team.

Full Twilio Voice vs CloudTalk comparison

Twilio Voice vs Aircall

from $30 per licence per month billed annually, three-licence minimum

Aircall is a per-seat cloud phone and sales calling platform with over 100 integrations, a Power Dialer, and a clean agent interface, at around $30 a seat with a three-licence minimum. Twilio has no interface, no integrations in the CRM sense, and no seats. The genuine decision point is whether calling is something your team does or something your software does. Aircall for the former, Twilio for the latter.

Full Twilio Voice vs Aircall comparison

Implementation & onboarding

Setup time
An hour to place your first programmatic call and a day to build a working IVR with Studio. A production-grade dialing application with call lists, pacing, dispositions, retry logic, recording management, and reporting is a multi-month engineering project and should be budgeted as one.
Learning curve
Gentle for a developer and impassable for anyone else. TwiML is learnable in an afternoon and the console is well designed, but there is no path through this product for a non-technical buyer, and the telephony concepts underneath (SIP, call legs, attestation, regulatory bundles, carrier filtering) take longer to learn than the API does.
Onboarding
Entirely self-serve with trial credit. Support at the free tier is documentation and ticketing; paid support plans are available and are worth budgeting for any production calling workload. Twilio's documentation, quickstarts, and CodeExchange samples do most of the onboarding work.
Migration notes
Numbers port in and out normally, so you are not locked to Twilio at the numbering layer. What does lock you in is your application code: TwiML, the REST API shapes, and the SDK integrations are Twilio-specific, and moving to Telnyx or Plivo means rewriting the call control layer even though the underlying telephony concepts transfer. Recordings should be exported before you leave, since storage is billed monthly and deletion is permanent. If you are moving off a boxed dialer onto Twilio, budget for rebuilding call list management, dispositions, and reporting, which are the parts vendors give away and the parts nobody remembers to scope.

Platform, API & security

Platforms
REST API over HTTPSTwiML webhook call controlJavaScript, iOS, and Android Voice SDKs (WebRTC)Elastic SIP TrunkingTwilio CLI and serverless FunctionsStudio visual flow builder
API
Programmable Voice REST API with helper libraries for Node.js, Python, Java, C#, PHP, Ruby, and Go, plus webhooks, status callbacks, event streams, and subaccounts for multi-tenant use. This is the product; there is no non-API surface.
Compliance
SOC 2 Type IIISO 27001GDPR with data processing termsHIPAA-eligible configuration with a business associate agreement for supported productsPCI DSS support for payment flows over voiceSTIR/SHAKEN attestation and Trust Hub identity registrationRegulatory bundles enforcing per-country number provisioning requirements
Data residency
Regional infrastructure in the United States, Ireland, Australia, Japan, Brazil, and Singapore, with data residency selectable for supported products so calls and recordings can be pinned to a region.
SSO
SAML single sign-on and role-based access control available on the account, with subaccount isolation for multi-tenant deployments.
Security notes
TLS for signalling, SRTP for media, and optional encryption at rest for stored recordings using your own public key. Because you build the application, most of the practical security surface (webhook signature validation, credential storage, recording access control) is your responsibility rather than Twilio's, and Twilio documents this clearly rather than pretending otherwise.

Support & resources

Channels
Documentation and self-service at the free tierPaid support plans with ticket, chat, and phone escalationEnterprise support with named contacts and SLAsA large partner and consultancy ecosystem
Documentation
twilio.com/docs, widely regarded as the best technical documentation in the communications industry, with quickstarts in every supported language, TwiML references, and runnable code samples.
Community
Very large developer community, an active Stack Overflow presence, CodeExchange sample applications, and the annual SIGNAL conference. Hiring an engineer who has already shipped on Twilio is straightforward, which is a real and underrated advantage.

Company

Founded
2008
Headquarters
San Francisco, California, United States
Ownership
Publicly traded (NYSE: TWLO)
Founders
Jeff Lawson, Evan Cooke, John Wolthuis
Employees
Roughly 5,000 to 5,500 (public filings, 2026)
Funding
Raised approximately $614M in venture capital before its 2016 IPO, with backers including Union Square Ventures, Bessemer Venture Partners, and Redpoint; subsequently funded by public markets, and the acquirer of SendGrid in 2019 for about $3B and Segment in 2020 for about $3.2B.

Funding history

RoundAmountYearNotes
Venture rounds (Seed through Series E)Approximately $614M2009 to 2015Backers included Union Square Ventures, Bessemer Venture Partners, Redpoint Ventures, and Fidelity.
IPOAbout $150M raised2016Listed on the NYSE under the ticker TWLO.
SendGrid acquisitionAbout $3B in stock2019Added transactional email to the platform.
Segment acquisitionAbout $3.2B in stock2020Added a customer data platform, later repositioned as Twilio Segment.

Timeline

  1. 2008Founded by Jeff Lawson, Evan Cooke, and John Wolthuis on the premise that telephony should be an API call rather than a carrier contract.
  2. 2009Launches Programmable Voice with TwiML, establishing the webhook-and-markup model that the entire CPaaS category subsequently copied.
  3. 2016Goes public on the NYSE under the ticker TWLO.
  4. 2019Acquires SendGrid for about $3B, broadening from communications APIs into a multi-channel platform.
  5. 2020Acquires Segment for about $3.2B and launches Twilio Flex, a programmable contact centre built on the voice platform.
  6. 2023Ships Voice Intelligence and expands Trust Hub, Branded Calling, and Voice Integrity as carrier spam filtering becomes the dominant threat to answer rates.
  7. 2024Khozema Shipchandler becomes chief executive, and the company narrows its focus toward customer engagement and AI-driven communications.
  8. 2026Published US voice rates stand at $0.0140 outbound and $0.0085 inbound to local numbers, with local numbers at $1.15 a month, recording at $0.0025 a minute, transcription at $0.0500 a minute, and Branded Calling at $0.12 a call.

Integrations

  • Helper libraries for Node.js, Python, Java, C#, PHP, Ruby, and Go
  • JavaScript, iOS, and Android Voice SDKs
  • Elastic SIP Trunking to existing PBX and contact centre platforms
  • Twilio Studio and Functions
  • Twilio Flex programmable contact centre
  • Salesforce and other CRMs via Twilio-built or partner connectors and the API
  • Event Streams into data warehouses
  • Large partner and ISV ecosystem, including many products in this directory that run on Twilio underneath

Frequently asked questions

10 questions

What is Twilio Voice?

Twilio Voice is a programmable voice API. You buy phone numbers and pay per minute, and your own software controls what happens on each call using TwiML instructions, a REST API, and WebRTC SDKs for browser and mobile. It is infrastructure rather than a finished product: there is no dialer interface, no agent console, and no CRM integration out of the box. Many of the dialers and phone systems sold to small businesses are built on top of it.

Can a small business use Twilio Voice without a developer?

No, and this is the most important thing to understand before comparing its prices with anything else in this category. Without engineering capacity you would be buying a phone number, a set of API endpoints, and a metered bill, with nothing that resembles a product a salesperson can open and use. Studio, the visual flow builder, lets a technical non-developer build a basic IVR, but building a dialer, a call list, dispositions, or reporting requires real software development.

How much does Twilio Voice cost?

It is pure pay as you go with no subscription. In the US, outbound to local numbers is $0.0140 per minute, inbound to a local number is $0.0085, inbound to toll-free is $0.0220, and browser or SDK legs are $0.0040. Local numbers rent for $1.15 a month and toll-free for $2.15. Recording is $0.0025 a minute plus $0.0005 a minute per month of storage, transcription is $0.0500 a minute, answering machine detection is $0.0075 a call, and Branded Calling is $0.12 a call.

What would a three-person team making 100 calls a day actually pay?

6,300 calls a month at two minutes each is 12,600 outbound minutes, which is $176.40. Add three local numbers at $3.45, recording at $31.50, and answering machine detection on 6,300 attempts at $47.25, and you are at roughly $259 a month. Transcribing all of it would add $630. And none of that includes building the software that decides who to call, when to call them, and what to record against which record, which is the actual work.

Is Twilio cheaper than a per-seat dialer?

Sometimes on paper, rarely in practice. The comparison people make is $0.0140 a minute against $65 a seat, which ignores that the dialer includes the interface, the call list, the local presence pool, the CRM logging, the recordings, the reporting, and a vendor to hold accountable. Once you add recording, detection, and transcription meters and then add the engineering cost of building everything a dialer gives away, Twilio is usually more expensive for a small sales team and cheaper for a software company embedding calling into its own product.

What does international calling cost on Twilio?

It varies enormously by destination and by whether the number is a landline or a mobile, from fractions of a cent to well over a dollar a minute. Twilio publishes per-country rate tables rather than a single international rate. Within the US, rates are not even uniform: Alaska outbound is $0.0945 a minute, about seven times the standard $0.0140. Always check the specific destination before assuming the headline rate applies.

How does Twilio handle spam labelling and caller ID?

Better than almost anyone in this category, which is a genuine reason to build here. Trust Hub registers your business identity so outbound calls carry proper STIR/SHAKEN attestation rather than travelling unsigned, CNAM registration sets the name displayed on US calls, Voice Integrity monitors how carriers are labelling your numbers and provides a remediation path, and Branded Calling displays your name, logo, and stated call reason on supported handsets for $0.12 a call. The catch is that all of this is configuration you perform, not a service that happens automatically.

Who is responsible for TCPA compliance when I build on Twilio?

You are, entirely. Twilio provides the transport and a set of acceptable use policies; it does not scrub the National Do Not Call Registry, maintain your internal do-not-call list, capture or store consent records, enforce calling hours, or add recording announcements. If you build an outbound dialing application, consent capture, DNC scrubbing, opt-out handling, calling-window enforcement, and one-party or two-party recording notification are all features you must build and maintain. Boxed dialers in this category often handle several of these for you, which is a large and frequently overlooked part of their value.

How is call recording billed and where is it stored?

Recording is $0.0025 per minute and storage is $0.0005 per minute per month, billed for as long as you retain the audio. That storage charge is trivial in the first month and becomes a standing line item over years, so set a retention policy from day one. Encryption at rest with your own public key is available, and recordings can be downloaded and stored in your own infrastructure. Transcription is separate and, at $0.0500 a minute, far more expensive than the recording itself.

How does Twilio compare to Telnyx and Plivo?

All three sell the same shape of product and Twilio is the most expensive of the three on raw US minutes: $0.0140 outbound against Plivo's $0.0115 and Telnyx's published $0.002 elemental rate plus a SIP trunking fee. Twilio is also the most complete platform, with the best documentation, the widest ecosystem, the deepest trust and AI products, and the largest pool of engineers who already know it. If your workload is high-volume US voice and cost dominates, look hard at Plivo or Telnyx. If you are building a product and developer velocity matters more than a fraction of a cent, Twilio is still the default.

Editorial verdict

Twilio Voice belongs in this directory as a building block, not a product, and buyers should read its pricing with that firmly in mind. As infrastructure it is exceptional: transparent metered rates, the best documentation in the industry, carrier reach in over 100 countries, WebRTC SDKs for browser and mobile, and a trust stack covering STIR/SHAKEN, CNAM, spam remediation, and branded calling that most boxed vendors cannot match. Buy it if calling is a feature of software you sell, if your routing logic is too specific for any vendor's product, or if you have engineers and a genuine reason to own the layer. Do not buy it because $0.0140 a minute looks cheaper than $65 a seat, because that comparison is missing the dialer, the interface, the CRM logging, the compliance handling, and the months of engineering you would spend rebuilding all four. For a small business that just wants its salespeople to make calls, the right answer is a dialer, and there is a reasonable chance that dialer is running on Twilio anyway.

Written by the SaaSTracker editorial team. Awards, when shown, are judged against the published criteria in our methodology.