Bulk Messaging Best Practices: Avoid Suspension

TL;DR: Carrier suspension kills campaigns. Prevent it by respecting rate limits (200-300 per minute depending on carrier), registering DLT codes, validating opt-ins, and using compliance-first platforms like Onyx that enforce these guardrails automatically.

Why Your Bulk SMS Gets Suspended

Insurance agents lose thousands of leads to SMS carrier suspension every year. You send 500 messages to your nurture list. Three hours later: “Account suspended pending review.” No warning. No appeal process. Your campaign dies, and your leads go dark.

The carriers (Twilio, AWS SNS, Bandwidth, Custom Carriers) don’t suspend arbitrarily. They have mechanical compliance rules. Break them, and automation flags your account instantly.

Most common violations:

Sending too fast. Bulk SMS has per-minute rate limits. Most carriers cap text throughput between 200-300 messages per minute. If you hit 1,000 in 60 seconds, the carrier’s spam detection fires and your sender ID gets blocked.
Unregistered sender. Many carriers now require 10DLC (10-digit long code) or Dedicated Long Code (DLC) registration. If your sender ID isn’t registered, the carrier routes your messages to the SMS provider’s shared pool — triggering the “looks like spam” filter.
Poor opt-in hygiene. Sending to numbers with no consent record, expired consent, or contacts who’ve explicitly opted out triggers carrier violations and FCC TCPA liability.
Frequency caps ignored. Insurance regulations and carrier rules limit messaging frequency. Too many texts to the same number in 24 hours = suspension.

Onyx prevents this with built-in rate limiting and compliance checks in every automation workflow. But if you’re sending SMS outside a compliance-first platform, you need to understand the rules.

Carrier Requirements by Provider

Different carriers have different rules. If you’re using Twilio, AWS SNS, or a custom carrier, your limits change.

Twilio SMS Rate Limits

Twilio — the most popular SMS provider for CRM platforms — enforces per-minute throughput limits based on your account tier:

Standard accounts: 1 message per second (60/minute, ~3,600/hour)
Higher-tier accounts: Up to 100+ messages per second with dedicated short codes

If you exceed your tier, Twilio throttles your queue (messages delay) or suspends the account if the violation is severe.

Registration requirement: Twilio requires 10DLC registration for all US long codes. Without it, your messages route through the shared pool and carriers treat them as high-spam-risk.

Source: Twilio SMS Rate Limits Documentation

AWS SNS (Simple Notification Service)

AWS SNS caps SMS throughput at 100 messages per second by default (configurable on request). If you spike above that, messages queue and delay.

AWS also enforces daily spend limits ($1/day default) to prevent accidental bulk charges. Legitimate bulk campaigns exceed this — you need to request a limit increase.

Registration: AWS requires 10DLC or Short Code registration for production SMS. Without it, you’re in sandbox mode with severe throttling.

Source: AWS SNS SMS Pricing & Limits

Custom Carrier Connections

If you’re routing SMS through a custom carrier (common for enterprise), your limits depend on your SLA (Service Level Agreement):

Standard SLA: 100-200 messages per minute
Premium SLA: 500-1,000+ per minute
Dedicated throughput: Custom agreements for high-volume senders

Custom carriers are strict about compliance because they assume you have legal/contractual obligations. One violation can cost you the relationship.

Carrier registration in all cases requires:

Valid business entity (EIN, business registration)
Brand name and purpose (insurance agent, lead nurture, policy reminders, etc.)
Opt-in proof (forms, consent records)
Message samples (templates you’ll send)

The registration typically takes 3-7 business days.

Best Practices to Stay Compliant

Preventing suspension isn’t a guessing game. Follow these concrete steps.

1. Respect Rate Limits (The Mechanical Rule)

Calculate your per-minute capacity before launching campaigns. If your carrier allows 200/minute:

200 messages × 60 minutes = 12,000 per hour
12,000 × 8 hours (business day) = 96,000 per day

Spread your send time. If you have 5,000 leads to message, don’t queue them all at once. Distribute them over 30 minutes (167/minute — well under limit).

Onyx automations enforce this automatically. When you set up a bulk campaign, Onyx queues messages at your carrier’s rated throughput, preventing spikes.

Source: NAIC Insurance Communication Guidelines

2. Register Your Sender ID (DLT / 10DLC)

10DLC (10-digit long code) registration is now mandatory in the US for all SMS senders.

Steps to register:

1. Provide your business name, EIN, and agent credentials

2. Describe use case (“insurance lead nurture,” “policy reminders,” “annual review notifications”)

3. Submit message samples (3-5 SMS templates you’ll send)

4. Wait 3-7 days for carrier approval

Once approved, your sender ID is “branded” — carriers recognize it as legitimate insurance agent traffic, not spam.

Cost: Most carriers charge $1-3/month for DLT registration. Worth every penny.

Without registration, your messages route through the carrier’s shared SMS pool. Shared pools have aggressive spam filtering. Your legitimate insurance messages get caught in the crossfire.

3. Validate Opt-In Records (Compliance Proof)

Before sending bulk SMS, audit your contact list:

Has consent been documented? Verbal consent, web form, text message opt-in — all are valid. Email is NOT valid for SMS.
Is consent current? TCPA rules require “clear and conspicuous” disclosures. If consent is >2 years old and no recent engagement, refresh it.
Is the number still valid? Run a carrier validation check. Dead numbers and “do not call” numbers trigger violations.

Onyx stores opt-in timestamps and consent type (form, verbal, imported) for every contact. Before any bulk send, the system checks consent status.

Source: FCC TCPA Compliance Rules

4. Implement Frequency Caps

Sending 3 texts a day to the same lead = carrier violation and leads opt out.

Standard frequency rules:

New lead nurture: 1 message per day max (7-day sequence = 7 messages)
Active policy holders: 2 messages per month (policy reminders, annual reviews)
Abandoned leads: 1 message per week max

Onyx enforces these automatically. If you set a drip sequence to “daily,” Onyx caps it at 1/day per contact, preventing oversend.

5. Use Compliance-First Platforms

This is the easiest path. Platforms like Onyx handle compliance enforcement for you:

Rate limiting: Automatic queue management keeps you under carrier limits
DLT registration: Built-in or facilitated with your carrier
Consent tracking: Every contact has an opt-in record attached
Frequency enforcement: Workflows respect daily/weekly message caps
Carrier monitoring: Real-time alerts if rates drop (sign of carrier issues)

Non-compliance-first tools (manual SMS APIs, generic CRM bulk tools) leave these guardrails to you. Miss one, and you’re liable.

Onyx Angle: Built-In Compliance in Automated Workflows

Onyx CRM was purpose-built for insurance agents. Every automation workflow — Speed-to-Lead, Database Reactivation, Annual Review campaigns — includes compliance checks.

When you create a bulk campaign in Onyx:

1. The system validates contact opt-in records automatically

2. Messages queue at carrier-safe rates (200-300/minute depending on your carrier)

3. Frequency caps apply per contact (max 1 message per X hours/days)

4. Real-time monitoring alerts you to carrier issues

Example: You onboard 100 Medicare leads. Onyx’s Speed-to-Lead automation sends SMS #1 (“Getting back with you…”) at a controlled rate over 10 minutes. The system never spikes above your carrier’s capacity.

You don’t manage rate limits. You don’t monitor compliance. Onyx does it.

This is why agents using Onyx rarely face suspension. The platform enforces the rules you’d otherwise overlook.

Case Study: How One Agent Lost (and Recovered) 5,000 Leads

Mark, an independent agent running final expense campaigns, had built a list of 5,000 engaged leads. One Tuesday, he decided to launch a “annual review” SMS campaign to all of them simultaneously.

He uploaded the list to a generic SMS tool (not compliance-first). Hit send.

Within 90 minutes: account suspended. His carrier (a mid-tier provider) detected the sudden spike, flagged his account as potential spam, and locked him out.

Result: 5,000 leads went dark. No follow-up possible. Lost opportunity: ~$80,000 in potential commissions.

Mark’s solution was reactive: he switched to Onyx. The platform’s compliance-first architecture would have distributed those 5,000 messages over 4 hours (respecting rate limits), preventing the spike and the suspension.

Lesson: Suspension recovery is nearly impossible. Prevention is everything.

Pre-Launch Compliance Checklist

Before you send any bulk SMS campaign, verify:

[ ] Carrier rate limits documented. Do you know your per-minute cap? (Most: 100-300)
[ ] Sender ID registered. Is your 10DLC or DLC active with the carrier?
[ ] Opt-in records validated. Do you have documented consent for 95%+ of your list?
[ ] Frequency plan set. Are messages spaced 1+ day apart per contact?
[ ] Message templates finalized. Have you tested SMS templates for typos and compliance?
[ ] Carrier escalation contact identified. Do you have a direct contact at your SMS provider if something goes wrong?
[ ] Compliance-first platform enabled? Are you using a tool (like Onyx) that enforces these rules automatically, or doing it manually?

If you’re checking 6 out of 7, you’re at risk. If you’re relying on manual compliance without a dedicated tool, you’re at very high risk.

FAQ

Q: How long does 10DLC registration take?

A: 3-7 business days typically. Twilio and AWS handle registration through their dashboards. Custom carriers process offline (email/phone). Plan ahead if you’re launching campaigns.

Q: Can I re-register if I get suspended?

A: Re-registration is possible but difficult. Most carriers flag previously-suspended accounts. Your new registration takes longer (14-30 days). Better to prevent suspension than recover from it.

Q: What’s the difference between 10DLC and Short Codes?

A: 10DLC (10-digit long code) is a standard US phone number. Cost: $1-3/month. Short codes are 5-6 digit numbers (like 71355). Cost: $500-1000+/month. For insurance agents, 10DLC is standard. Short codes are for high-volume senders (pharma, retail).

Q: If I use a platform like Onyx, am I still liable for TCPA violations?

A: You’re liable for obtaining consent. The platform is liable for technical compliance (rate limits, carrier requirements). Use a compliance-first platform AND maintain clean opt-in records. Both are necessary.

Q: How do I recover from suspension?

A: Contact your carrier’s support team. Explain the violation (be honest). Request a review. Provide evidence of compliance changes (new DLT registration, opt-in cleanup, rate limit implementation). Recovery typically takes 5-15 days. You’ll be under heavy scrutiny for 30-60 days after.

Q: Can I switch carriers if suspended?

A: Partially. If your account is suspended due to compliance violations, the flag may follow to your new carrier (shared compliance database). Better to fix the original carrier relationship or wait 60-90 days before switching.

Q: Is there a “safe” message frequency?

A: Yes. 1 message per 24 hours per contact is universally safe. 2+ per day starts raising carrier flags. Some carriers allow 3-4 per day if you have explicit consent, but it’s edge territory. Stick to 1/day for lead nurture, 2/month for active policies.