10DLC Registration for SMS, Text & WhatsApp from Salesforce
Your US SMS, text and WhatsApp traffic goes through a 10-digit number. If it’s not registered under 10DLC, carriers throttle your messages, block your opt-out replies, and eventually blacklist your number. One afternoon of brand registration saves your whole messaging programme.
What 10DLC is and why it exists
You send SMS from a standard 10-digit US number, 10DLC (10-Digit Long Code) is the US carrier-enforced registration programme that applies to your traffic. You need to register your brand, register each campaign, and route your messages through a campaign-approved path.
Your carriers introduced 10DLC to cut spam and fraud. Unregistered traffic gets aggressive throttling, blocked replies, and eventually no delivery at all. Registered traffic gets higher throughput, better deliverability, and predictable pricing.
Brand registration, what you need ready
Your brand registration captures your business details for carrier verification. You’ll need:
- Legal business name, DBA if different
- US EIN (Tax ID)
- Business address and phone
- Industry classification
- Website URL
- Authorised representative contact
Your registration takes 2-3 business days to verify. Your Salesforce admin pastes the details into the messenger’s 10DLC setup panel, your messenger submits to the Campaign Registry, and your approval comes back as a status update on your org.
Campaign registration per use case
Your each messaging use case in your org is a separate 10DLC campaign. A mortgage lender might have three campaigns: marketing (new rate alerts to prospects), customer care (existing borrower updates), and two-factor authentication. Each campaign has its own approval, its own throughput tier, its own opt-in flow declaration.
Your Salesforce admin submits each campaign with the sample message content, opt-in language, and volume estimate. The Campaign Registry reviews, approves or flags. Your messenger routes the right Salesforce messages through the right campaign based on the source object and use case.
Throughput tiers that determine your bulk speed
Your registered campaigns have throughput tiers, messages per second your number is allowed to send. Standard vetting starts at 10 MPS. Vetted tiers go up to 225 MPS. Enterprise brands can get higher. If your mortgage team sends 12,000 messages in a Saturday bulk, throughput tier determines whether that takes 10 minutes or 2 hours.
Your messenger exposes the throughput tier to Salesforce admins so bulk send scheduling can be realistic. “Send 12,000 messages at 10am” is doable at 100 MPS. At 10 MPS, you’d start it the night before.
Where Agentforce AI agents fit into 10DLC
Your Agentforce AI agent responses are A2P traffic, they count against your campaign volume. When you register campaigns, declare the AI agent category (conversational support, qualification, appointment booking). Carriers have become used to AI-driven traffic and approve it under standard categories as long as the campaign description is honest.
Your team the important thing is not to hide AI traffic or misclassify it. Carriers audit. A campaign declared as “transactional appointment reminders” that turns out to be AI-driven marketing replies gets de-registered fast. Declare clearly, route cleanly, and AI-enabled 10DLC traffic runs without issue.