Twilio error 30035 means your sending number is associated with a Messaging Service, but that Messaging Service has no campaign registration attached to it. This is a more specific variant of the unregistered number error: the number itself may be in a Messaging Service, but the Messaging Service is operating without a campaign, which carriers treat as an unregistered A2P sender. Resolving 30035 requires completing the campaign registration and linking it to the Messaging Service, not just the number.
What Causes This Error
The most common cause is creating a Messaging Service for organizing phone numbers but not following through with the campaign registration steps required to associate a TCR-approved campaign with that service. A second cause is a partially completed registration workflow where the brand was registered and approved, but the campaign step was never submitted, leaving the Messaging Service in a state where it has a brand but no active campaign. Using a Messaging Service that was previously working but had its campaign registration revoked or expired will also generate 30035, as the service is no longer associated with any valid campaign in the carrier lookup database. Some developers copy Messaging Service SIDs from one application environment to another without ensuring both environments have their own campaign registrations, causing the production environment to run without a campaign.
How to Fix It Step by Step
Navigate to the Twilio Console, go to Messaging, then Services, and select the Messaging Service whose numbers are generating 30035 errors. Click the Campaign Registration tab and note whether the status shows No Campaign, Pending, or Failed. If the status is No Campaign, click Register Campaign, fill out the campaign use case category, provide two sample messages that are representative of what you actually send, complete the opt-in description accurately, and submit. For a Failed campaign registration, review the rejection reason, correct the submission, and resubmit: the most common rejection reasons are sample messages that are too generic, opt-in descriptions that do not specify how consent is collected, and use case descriptions that do not match the sample messages.
How to Prevent It from Recurring
Enforce a policy that no Messaging Service is deployed to production without a confirmed Active campaign status by adding a startup check in your application that queries the Twilio API for the Messaging Service's compliance status and refuses to process outbound messages if the status is not Active. Keep staging and production Messaging Services as separate entities with separate campaign registrations, never sharing a Messaging Service SID across environments, since changes in one environment will affect the other. Document your campaign registration details including TCR campaign ID, approved use case, and approval date in your team's infrastructure records and add a quarterly review to check that the registration is still accurate relative to how you are using the service. Implement a compliance status monitor in your alerting system that checks each Messaging Service campaign status daily via the API and pages your team if any service transitions out of Active status.
When to Call a Specialist
If your campaign registration has been submitted correctly according to the TCR guidelines but is stuck in Pending status, the delay may be due to a carrier review queue backlog or a specific flagging of your use case category that requires manual review. A specialist who regularly submits TCR campaigns can identify whether your submission is likely to encounter these delays, help you prepare supporting documentation to expedite review, and escalate with Twilio's carrier compliance team if the review is stalled. For accounts with multiple Messaging Services and campaigns, a specialist can audit your entire A2P registration portfolio to identify gaps, overlapping registrations, and mismatched use cases that are creating compliance risk. A missing campaign registration on a production Messaging Service is both a delivery failure and a compliance exposure that should be resolved with urgency.
Conclusion
Error 30035 is a campaign attachment gap at the Messaging Service level that is resolved by completing and activating the campaign registration workflow. If this error is blocking your production system, contact our team and we will diagnose and fix it within the hour.
Ready to Transform Your Business Communications?
Get a free consultation with our VoIP experts and discover how we can help you save costs, improve efficiency, and scale your business.
Comments (0)
Join the discussion and share your thoughts (AI-moderated for quality)
Be the first to comment
No comments yet. Share your thoughts below.