Summary

  • A Twilio Sole Proprietor campaign can register one 10DLC number. If its selected Messaging Service already contains several, Twilio documents a random choice of the verified route.
  • Campaign approval and individual-number registration with US carriers are separate stages. Adding numbers to the same service does not expand the one-sender allowance.
  • A CSV status report can take up to 24 hours to generate. That is a reporting interval, not a registration deadline; number-specific events offer another way to follow progress.

A business should probably choose its customer-facing number with more care than a raffle prize. Twilio’s Sole Proprietor documentation describes a configuration in which the choice can nevertheless be random. If the Messaging Service selected for a campaign already contains several 10DLC numbers, Twilio picks one as the verified route. There is one seat. The inventory supplies the candidates.

The owner may have deliberately bought every number in that inventory. That does not mean the owner deliberately chose the number that won registration. A reused service can quietly promote an old list of resources into a decision about which identity the business will present to customers.

This is a specific US messaging arrangement. Direct Sole Proprietor registration serves eligible customers in the United States and Canada without the relevant business tax identifier. Businesses with such an identifier, and businesses outside those countries, are directed towards Standard or Low-Volume Standard registration. The scheme concerns application-originated messages to US recipients over ten-digit long codes. Its convenience comes with an eligibility boundary and a capacity boundary.

One seat is not a slow second seat

Twilio’s warning 30125 describes an attempt to add a number to a Messaging Service associated with a Sole Proprietor campaign that already has a registered sender. The underlying limit is one campaign per Sole Proprietor Brand and one number for that campaign. Another number in the inventory does not create another registered place.

This turns an apparently technical delay into a purchasing question. Does the business want to keep the current sender, replace it, or operate several senders? Waiting can help a registration that is genuinely in progress. It cannot turn a one-number product boundary into a two-number entitlement.

The warning documentation sets out the corresponding choices. Keep the existing number if one sender is sufficient. To replace it, remove the existing sender from the associated service, add the replacement and let registration finish before sending to US recipients. For multiple numbers or greater scale, use an appropriate Standard or Low-Volume Standard Brand and campaign.

A team that puts all three situations into an “awaiting approval” bucket has postponed the commercial decision without naming it. There may be plenty of activity on the ticket and no realistic route to the capacity the business wants.

The lottery has an entrance condition

Random selection is the documented consequence of choosing a service already holding several numbers. The newer direct-customer Console flow starts somewhere more sensible: at the number the customer wants to use. Its setup checklist takes the customer through a profile, a Messaging Service, a Brand and a Campaign. The number is already in the campaign’s service. The guide describes the normal completion state as Messaging enabled against that number in inventory after campaign approval.

That path puts the intended identity first. Reusing an older service can put its accumulated contents first instead. Numbers left there for previous work become candidates for the new campaign’s single registration. Reuse saves configuration work while carrying configuration history into the decision.

Before registering a campaign, Twilio tells customers who want a particular number to remove the other numbers from the service. The customer can therefore determine the selection set even though there is no choice of winner within the documented multi-number lottery. Leaving only the intended candidate is a much better moment to exercise control than discovering the wrong winner after approval.

For an existing multi-number pool that needs correction, the troubleshooting guide describes removing all its numbers from the service and adding back only the desired number. These are changes to service associations. Releasing ownership of the number and closing a subaccount are different operations. “Clean up the numbers” is an impressively vague instruction for work with such different possible meanings.

The public documents do not quantify how often random selection conflicts with a customer’s intended sender; actual pool and number-registration histories would establish its incidence. The documented mechanism already identifies where that choice can be made deliberately.

Approval needs a noun attached

Brand, Campaign, Messaging Service and number can easily collapse into one reassuring sentence: registration is approved. They represent different objects. The Brand identifies the sender. The Campaign describes the messages and how recipients opt in or out. The service groups sender configuration. The individual number has its own registration state.

Twilio’s number-troubleshooting documentation says that, after TCR approves a campaign, individual numbers still need approval by the respective US carriers. That process is asynchronous. A green campaign status cannot answer for every row in its service’s inventory.

The distinction has particular force under the Sole Proprietor limit. Additional numbers remain unregistered. The fact that the service can contain a resource is not evidence that the campaign has acquired another usable sender. The purchasing unit and the operational unit need to meet before the launch date does.

The individual states help assign the next job. UNREGISTERED denotes the missing required verified association. PENDING_REGISTRATION means the request has arrived but the necessary configurations with ecosystem partners have not finished. REGISTERED identifies a number registered and ready for US sending. FAILURE requires investigation through support.

A number moving between campaigns may also pass through registered, pending deregistration, unregistered and registered again. The previous approval does not complete the new association by inheritance. A sender-change plan needs to account for that transition rather than treating the old green state as permanent property.

Tomorrow’s report is not tomorrow’s launch

Twilio offers a CSV report connecting numbers with their registration states and their campaign and service identifiers. Depending on the volume of numbers and accounts, generation can take up to 24 hours; a small inventory may be available sooner. The interval belongs to production of the observation.

Turning it into a promise that every number will be registered within a day would invent a deadline for a different process. “We should have the report tomorrow” and “we can start sending tomorrow” require different evidence. A commercial schedule that merges them becomes more certain than the source material.

Event Streams provides another observation route. Customers configure a receiving sink and subscriptions for changes to Brands, campaigns and numbers. A number-registration pending event and a successful-registration event describe distinct stages. Subscribing only to campaign approval leaves the final intended sender outside that same level of monitoring.

The events associate the number with its account, campaign and service. On 28 August 2025, Twilio announced the Messaging Service association in the 2.0 schema for the listed pending and successful number-registration and deregistration events. That small addition has a practical business use: a message about success can be attached to the correct piece of work, rather than merely applauded in an inbox.

An inventory report helps find omissions. Events help follow transitions. Both need to be compared with the senders the business actually decided to use, and somebody needs to own that comparison. A notification endpoint is not an organisational handover by itself.

RIPE NCC’s primary membership record identifies Twilio Inc. as the organisation. Twilio’s own operating documents supply the capacity, selection and registration rules discussed here. Those rules ask a concrete question of the buyer: which sender identity is being purchased, and what evidence will show that this particular identity is ready? With only one seat available, the answer deserves a decision before the celebration.

Primary sources