SIP providers that allow auto dialers fall into two camps. Usage-priced platforms such as Twilio and Skyetel permit the traffic but push compliance onto you. Wholesale carriers built for it, like SIPNEX, vet the traffic and then approve it. Unlimited-seat UCaaS plans, such as RingCentral RingEX and 8x8’s Unlimited PSTN plans, ban auto dialing outright. Telnyx and voip.ms restrict it.
If you’re typing this search, a provider has probably already rejected your trunk or flagged your account. The traffic itself isn’t the problem. You’ve been shopping in a product category whose terms of service were written to exclude it.
SIPNEX is an FCC-licensed carrier that carries dialer traffic on purpose, so we sit inside the “allow” column below — bias disclosed. Every policy claim that follows comes from the named vendor’s own published terms, linked in the table and re-checked on September 24, 2026.
The allow/ban landscape, provider by provider
Whether a provider tolerates an auto dialer is not a support-ticket lottery. Nearly every major provider has put its position in writing. It’s just buried in an acceptable use policy nobody reads until after suspension.
| Provider | Auto dialer policy | Source (checked 2026-09-24) |
|---|---|---|
| RingCentral RingEX | Banned on RingEX. AUP prohibits customers from performing “auto-dialing or ‘predictive dialing’” and states RingEX is “intended for regular business use between individuals,” not call center calling. RingCentral sells predictive dialing separately, in its RingCX contact-center product | RingCentral Acceptable Use Policy |
| 8x8 | Banned on Unlimited PSTN plans — no autodialing, telemarketing, or call center operations; 8x8 “reserves the right to immediately terminate.” 8x8 sells a separate contact-center dialer | 8x8 Business Terms, §15 |
| Telnyx | Restricted. AUP lists “auto-dialing or predictive-dialing” among improper uses, with an extra clause for unlimited packages. But Telnyx publishes CPS limits and surcharges, and reserves the right to answer violations with surcharges rather than termination — a restriction in practice | Telnyx Acceptable Use Policy |
| voip.ms | Pre-authorization required for “automated dialers, call centers… dialer traffic,” arranged through sales; unauthorized use can be suspended “without prior notice” | voip.ms Terms of Service |
| Flowroute | No published stance on dialers either way; terms require compliance with telemarketing, do-not-call, and TCPA rules | Flowroute Terms of Use |
| Twilio | Allowed. AUP contains no autodialer prohibition — it requires compliance with consent and opt-out law and leaves TCPA responsibility with you | Twilio Acceptable Use Policy |
| Skyetel | Allowed. Terms assign TCPA and Telemarketing Sales Rule responsibility to the customer, with consent records kept at least five years and full indemnification | Skyetel Terms of Service, §7.2 |
| SIPNEX | Allowed after vetting. FCC-licensed carrier that approves dialer traffic through KYC and a traffic review, then bills it 12/6 | Us — bias disclosed |
Three patterns emerge. Seat-priced UCaaS plans ban the traffic, even where the same vendor sells a dialer in its contact-center line. Usage-priced platforms allow it but hand you the entire compliance burden. In Twilio’s case, that comes with per-minute billing that rounds against you. Wholesale carriers that vet traffic are the only category where “allowed” is the design intent rather than a loophole.
What the ban wording actually covers
Read the quoted clauses again. RingCentral bans “auto-dialing or ‘predictive dialing.’” 8x8 bans “autodialing.” Neither limits the ban to predictive mode. A power dialer places one call at a time, but software still places it. Read literally, that is auto-dialing under this wording, whether the vendor calls the mode power or progressive.
Manual dialing is the only mode these clauses clearly leave alone. An agent keys ten digits, the phone system sends the call, and nothing automated touched the attempt. It is also the mode that spends most of an agent’s hour on ringback, voicemail, and wrap-up. That trade-off is the whole reason dialers exist.
Telnyx’s wording has the same shape, but its enforcement differs. It publishes the limits and prices what crosses them. voip.ms names the traffic and asks you to request approval first. Those two make up the “restricted” column. The door is not shut, but you have to knock.
How to read a provider’s policy in five minutes
You do not need to read the whole acceptable use policy. Open it and search for six strings: “auto-dial,” “autodial,” “predictive,” “call center,” “telemarketing,” and “reasonable business use.” A ban usually contains at least two of them. A restriction usually pairs one of them with approval or surcharge wording, such as voip.ms’s “pre-authorized” or Telnyx’s “surcharges.” No hits at all is not a yes. It means the provider has not written its position down, and Flowroute is the example in the table above.
Then check which document you are reading. 8x8, for example, puts its Unlimited PSTN restriction inside §15 of its Business Terms, under “Prohibited Uses.” Pricing pages do not lead with it.
Why “unlimited” plans ban auto dialing
The ban is arithmetic, not hostility. An unlimited seat is priced against how much a human being talks in a month. An auto dialer places thousands of short attempts per agent per day. One dialer seat can generate the minutes of an entire office, and the flat price collapses instantly.
That’s why the ban language looks so similar from vendor to vendor. 8x8 limits its Unlimited PSTN plans to “reasonable business use.” Telnyx’s AUP adds a separate clause for any unlimited calling package that bars auto-dialing, telemarketing, and predictive dialing. Every flat-per-seat plan we checked carries a clause like this, so assume yours does until you have found it.
The practical rule: if the pricing page says “unlimited,” expect the terms page to say “no auto dialing.” Dialer traffic has to run on usage-priced trunks. There, the carrier makes money on the traffic instead of losing it.
The fine print that catches dialer operators
“Allowed” and “restricted” both come with mechanics that decide your real costs. Telnyx is the clearest example. Its CPS surcharge article sets the default outbound limit for standard SIP trunking at 20 calls per second per source IP or SIP username. Excess calls are rejected with SIP 503. New accounts start at 2 concurrent outbound calls, rising to 10 after Level 2 verification.
Telnyx also bills a monthly Outbound Peak CPS surcharge. It is computed from the 95th percentile of hourly peak CPS. The first 5 CPS are free, then $12–$30 per CPS by tier. Telnyx’s own worked example prices a 163 CPS peak at $2,448 per month. Its AUP separately reserves the right to treat a violation with “additional charges or surcharges” instead of termination.
voip.ms adds a second gate most operators miss. Beyond telemarketing pre-authorization, calls carrying signal for less than 6 seconds count as “Short Calls” and need their own separate approval. If short calls reach 10% of a day’s completed outbound calls, voip.ms may also add a $0.01 surcharge per short call.
On Twilio, voice is billed per minute — 60/60 on standard pay-as-you-go pricing, including Elastic SIP Trunking. A 12-second dialer call bills as a full minute. Twilio’s A-level attestation also requires KYC: a Trust Hub Business Profile plus the SHAKEN/STIR Trust Product, with your numbers assigned to both.
Skyetel prices traffic shape instead of banning it. Its surcharge policy defines a “Short Call” as one under 6 seconds. Autodialer traffic may run up to 40% short calls and 40% zero-second calls. Cross a limit and the fee is $0.03 per call across the month’s full short-call percentage, not just the calls above the line. The first 1,000 calls are exempt.
60/60 versus 12/6 at cold-calling call lengths
Cold calling produces a lopsided call-length curve. Unanswered and busy attempts bill nothing under either scheme. Many connected calls still end in seconds: voicemail pickups the dialer drops, wrong numbers, and quick hang-ups. A minority run for minutes when a prospect engages. Billing increments decide what the short calls cost you. The per-minute rate decides what the long ones cost.
The table shows billable seconds only. It uses no rate at all, because the increment effect is the same at any rate.
| Actual call length | Billed under 60/60 | Billed under 12/6 |
|---|---|---|
| 5 seconds | 60 seconds | 12 seconds |
| 12 seconds | 60 seconds | 12 seconds |
| 20 seconds | 60 seconds | 24 seconds |
| 45 seconds | 60 seconds | 48 seconds |
| 90 seconds | 120 seconds | 90 seconds |
| 3 minutes | 180 seconds | 180 seconds |
Read the top rows. A 12-second connect bills five times longer under 60/60 than under 12/6. A 20-second call bills two and a half times longer. Only in the last row, at a whole number of minutes, do the two systems meet. On a floor where most connected calls never reach 30 seconds, the increment is the price.
That is why the headline per-minute rate is the wrong number to compare. Pull 30 days of CDRs. Sort them by duration. Apply the increment rule of the trunk you are considering to each call. Then compare totals. Our SIP trunk pricing comparison explains the increment and fee structures providers publish.
A worked example makes it concrete. Take 1,000 connected dialer calls in one hour. Say 700 end under 12 seconds, 200 last about 20 seconds, and 100 become three-minute conversations. Under 60/60 those calls bill 1,200 minutes: 700 full minutes for the short connects, 200 more for the 20-second calls, and 300 minutes of conversation. Under 12/6 the same hour bills 520 minutes: 140 for the short connects, 80 for the 20-second calls, and the same 300 for the conversations.
The conversations cost the same either way. The short connects cost about four times as much on 60/60. That gap is why a lower headline rate on a 60/60 trunk can still produce the larger bill.
What a carrier that allows auto dialer traffic asks for
A carrier that says yes to dialers isn’t skipping the questions the banners ask. It’s asking better ones up front. At SIPNEX the vetting looks like this, and answering it is what gets traffic approved rather than tolerated:
- KYC — who you are, your business, your FCC registrations where applicable. voip.ms applies the same logic to resellers, requiring an RMD registration number and FRN before US outbound calls.
- Traffic profile — expected volume, average call length, CPS pattern, campaign type. Honest short-ALOC dialer traffic is fine; we just need to route and price it as what it is.
- DNC and consent process — how lists are scrubbed and consent is recorded. Our TCPA compliance checklist covers what regulators expect.
- Number rights — proof you’re entitled to your caller IDs. Under the SHAKEN standard (ATIS-1000074), A-level attestation means the carrier knows the customer and their right to the number, which is exactly what vetting establishes. The mechanics are in our A-level vs B-level attestation explainer.
Vetted traffic then runs on terms built for it. SIPNEX signs at A-level, on a STIR/SHAKEN certificate of our own. Dialer traffic bills 12/6, meaning a 12-second minimum with 6-second increments after that, instead of the 60/60 rounding Twilio and Telnyx apply. What the rest of a purpose-built setup looks like is on our predictive dialer carrier page. We don’t publish a termination rate table here; send us your actual CDRs and we’ll quote against them.
VoIP for telemarketing and cold calling: what changes
Telemarketing is the use case the retail policies were written against, so name it honestly when you shop. voip.ms requires pre-authorization for “telemarketing purposes of any nature,” including polls and collections. 8x8’s Unlimited PSTN terms bar telemarketing “including without limitation charitable or political solicitation or polling.” Describing a cold-calling floor as ordinary business use just converts a sales conversation into a future suspension.
The second change: a carrier’s permission is not legal cover. Twilio and Skyetel allow the traffic, and their terms make you responsible for TCPA, consent, and opt-out compliance. Skyetel requires consent records kept at least five years and full indemnification. The carrier decides whether your calls route. The law decides whether they were lawful. Both answers have to be yes.
Ask these before you sign
These are the allow/ban questions specifically. For general trunk diligence, use our SIP trunk provider vetting questions guide.
- Is auto dialer traffic permitted in writing, on my specific plan — not just “usually fine” from a sales rep?
- What CPS and concurrent-call limits apply, and what happens at the ceiling — rejected calls, surcharges, or both?
- What are the billing increments? At dialer call lengths, 60/60 versus 12/6 changes the effective rate more than the headline price does.
- What ASR, abandon-rate, or short-call thresholds trigger review, and who decides them?
- What does enforcement look like — notice and a conversation, or suspension first? If you’ve already lived the second one, our dialer account suspension guide covers the recovery path.
A provider that answers all five without flinching is a provider that actually wants your traffic.
Frequently asked questions
Which SIP providers allow auto dialer traffic?
Twilio and Skyetel permit it under their published terms, and wholesale dialer-built carriers like SIPNEX approve it after vetting. Twilio’s AUP has no autodialer prohibition — it requires consent-law compliance instead. Skyetel’s terms assign TCPA responsibility to the customer rather than banning the traffic. On the other side, RingCentral’s RingEX and 8x8’s Unlimited PSTN plans prohibit auto dialing in their use terms. Telnyx lists it among improper uses, and voip.ms requires pre-authorization through sales before any dialer traffic runs.
Why do unlimited VoIP plans ban auto dialers?
Because the pricing model breaks. An unlimited seat is priced against human talk time, and a dialer generates an office’s worth of minutes from one seat. 8x8 limits Unlimited PSTN plans to “reasonable business use,” with the right to terminate immediately for autodialing or call center operations. Telnyx’s AUP bars auto-dialing and predictive dialing on any unlimited calling package. The ban is how flat-rate pricing survives. Dialer traffic belongs on usage-priced trunks, where the carrier earns on volume instead of losing on it.
Does Twilio allow auto dialer traffic on its SIP trunks?
Yes. Twilio’s Acceptable Use Policy contains no autodialer prohibition; it requires you to comply with consent and opt-out law and carry the TCPA risk yourself. The operational catches are elsewhere. Voice is billed per minute (60/60) on standard pay-as-you-go pricing, which rounds every short dialer call up to a full minute. A-level attestation requires completing Trust Hub KYC and attaching the SHAKEN/STIR Trust Product before your calls are signed. Allowed, in other words — but priced and provisioned for app traffic, not dialer traffic.
What do carriers ask before approving auto dialer traffic?
Four things: identity (KYC), your traffic profile, your DNC and consent process, and proof of number rights. The profile covers volume, average call length, and CPS. Number rights are what make A-level attestation possible — under the SHAKEN standard, A-level means the carrier knows the customer and their right to the number. A carrier that asks these questions up front is underwriting a yes. A carrier that asks nothing usually enforces its terms after the fact instead.
Will running an auto dialer get my VoIP account suspended?
Eventually, yes, if the provider’s terms prohibit or restrict it — automated traffic patterns are easy to detect. voip.ms, for example, reserves the right to suspend unauthorized telemarketing use “without prior notice,” DIDs included. The fix is not hiding the traffic. It’s moving it to a provider whose terms permit it, declared as what it is. If you’re mid-suspension right now, start with our dialer account suspension guide, then rebuild on a carrier that approved the traffic in writing.
If a retail provider just told you no, the answer isn’t a workaround. It’s a carrier whose yes is in writing. SIPNEX runs dialer-grade trunks with A-level attestation and 12/6 billing. Send us your CDRs for a quote or call (833) 665-2220.
Keep reading.
The carrier built by operators, for operators.
FCC-licensed carrier with its own STIR/SHAKEN SP certificate. Operator-owned. SIP trunks built for operators who dial at volume.