If you were kicked off Twilio, Blackleaf may be able to support your business through a separately reviewed texting program. Blackleaf works with regulated businesses, including cannabis and firearms businesses, and reviews the actual company, message purpose, destination and recipient permissions before onboarding. Start with the exact Twilio notice. A rejected registration, suspended campaign, restricted account and filtered message each call for a different response.
What did Twilio stop?
Check the email or dashboard notice and record its date, exact wording and any error code. Determine which workflows stopped receiving messages before changing your integration or paying for a new provider.
| What you see | What it means | What to check first |
|---|---|---|
| An account suspension notice | Twilio has restricted account access or activity. The notice determines the scope and next steps. | Follow the instructions in the notice. Ask Twilio Support which services and numbers are affected and which records you can still access. |
| Error 30990 | Twilio suspended the affected U.S. A2P 10DLC campaign and halted messaging for that campaign. | Read the campaign or brand notice. Keep the affected workflow paused while the reason is being reviewed. |
| Error 30860 or 30883 | A verification request was rejected for cannabis or CBD under 30860. An A2P 10DLC campaign was rejected during content vetting under 30883. | Check the stated reason. If the business or use case was misclassified, raise the discrepancy through Twilio’s official process. |
| Error 30007 | Twilio or a carrier filtered an individual message. | Compare the status of the affected messages and ask Twilio to investigate if you believe the traffic meets its policies. |
See Twilio’s account suspension guidance, 30990, 30860, 30883, and 30007.
For a category-related rejection, read the guide to Twilio error 30860 for cannabis and CBD businesses or the Twilio rejection guide for firearms account and service texts.
What makes a Twilio alternative a fit for regulated texting?
Ask the provider to confirm support for your legal business and the exact workflow you need, including the destination country, sender type, message samples, websites and opt-in process. A general SMS API can have category restrictions of its own. For example, Telnyx’s published messaging guidance lists cannabis-related traffic and firearms-related messaging among its restrictions. Request a written decision for your use case before spending time on registration or integration. Telnyx forbidden messaging use cases
| Ask the provider | What to confirm |
|---|---|
| Can you support our business and this workflow? | The decision identifies the legal entity, recipient destinations and specific message purpose. |
| What must be approved before sending? | The provider identifies the required sender registration, message review and any approval dependencies. |
| How do you handle permission records and opt-outs? | You can verify who may receive each workflow and whose number must stay suppressed after the move. |
| What can our team see when messages fail? | You can distinguish an accepted API request from an eventual message status, and you know where to investigate or escalate a failure. |
| Do we need a new number? | The providers confirm whether the current number is eligible to move and what remains to finish before it can send. |
Keep the records your team will need
- Save the notice and map the impact. Note which reminders, replies and automations depend on the affected sender. Pause automatic retries and use a staffed, permitted channel for time-sensitive support where customers can already reach you.
- Preserve permission and suppression together. Where you still have authorized access, retain the original SMS disclosure, the customer’s opt-in source and date, the purpose they agreed to and any later opt-out. Keep withdrawn contacts suppressed during the cutover. Put records with missing or uncertain permission aside.
- Document the workflow customers actually receive. Bring a representative message, its trigger, expected frequency, who answers replies and any linked destination. Use fictional customer details in review samples.
- Plan the integration after the eligibility review. Confirm who maps message status, replies and opt-outs into the system your team uses. If an old send has an uncertain result, reconcile it before initiating another message. Review the Blackleaf Regulated SMS API and the developer guide for current messaging operations.
- Confirm readiness before activating a live workflow. Check the approved sender, current permissions, opt-out handling and ownership of the support inbox. Keep activation limited to the scope that was reviewed.
Can Blackleaf take over a Twilio number or contact list?
Phone number. Ask both providers about number eligibility, account status and authorization to move the number. Separately confirm how the number would be approved for messaging on the new service. Build your cutover around a confirmed result.
Contact list. Copying contact data carries over the address book. Eligibility to send depends on the original permission, whether it covers the proposed workflow and sender, and any later withdrawal. If you lack proof, leave the number out of the texting audience until eligibility can be established. Use the Texting data migration checklist to plan the handoff.
Ask Blackleaf to review your use case
Contact Blackleaf with your industry, website, recipient country, the workflow that stopped and the Twilio notice or error code. Include one or two examples with fictional names and contact details. Blackleaf can tell you what it would need to review and whether there is a supported path forward. Onboarding, sender approval and eventual message delivery each depend on their own checks.