thelastapi
Get started free

Send SMS from your app: carrier approval explained

Send SMS from your app over 10DLC by completing carrier brand registration, sample message verification, and opt-out compliance.

On this page 8 sections

To send SMS from an application to US mobile phones over 10-digit long code (10DLC) numbers, your business must complete carrier registration before any outbound messages can be delivered. Mobile carriers require this verification to confirm your business identity, evaluate your sample messages, and inspect how recipients give consent. thelastapi provides US phone numbers that can receive inbound texts immediately, but holds outbound text messages until carriers grant registration approval.

This guide explains how 10DLC registration works, what carrier reviewers require in your submission, and how to configure outbound SMS in your app.

Why US carriers require 10DLC registration

US cellular networks block unregistered application-to-person (A2P) traffic sent across standard 10-digit local phone numbers. In past years, applications could purchase a local virtual number and begin sending text messages instantly, which led to high volumes of unwanted spam and deceptive campaigns.

In response, telecommunications carriers introduced the 10DLC framework. Under this system, software providers cannot simply pass outbound traffic directly to handsets. Instead, the business sending the messages must register its legal identity and explain the specific category of messages it sends.

Rather than letting your application's messages fail silently or disappear inside carrier spam filters, thelastapi tracks approval through your number's sending_status. Outbound texts are blocked at the API level until carrier review finishes, preventing wasted credits on dropped messages. Receiving incoming texts does not require registration; an active number can receive messages via webhooks right away, as explained in how to receive text messages in your app.

What carriers look for in your registration

Every registration is reviewed by carrier representatives. Submissions are rejected when details are missing or contradictory. You access the registration form directly from your number's page in the console.

To pass carrier review, your registration requires:

  • Legal business identity: Your registered business name, brand name, physical address, contact email, and Employer Identification Number (EIN). The legal name and tax ID must match official tax records exactly.
  • Sole proprietorship details (if no EIN): If you do not have a registered business entity or EIN, you register as a sole proprietor using your personal mobile number. Carriers verify your identity by sending a one-time PIN to that mobile phone.
  • Campaign purpose: A clear explanation of why your application sends messages (such as transactional account notifications, appointment updates, or customer service replies).
  • Two real sample messages: At least two representative message templates. These samples must reflect the exact wording your application sends. At least one sample message must include explicit opt-out instructions (for example: "Reply STOP to cancel").
  • Opt-in workflow description: A detailed description of how users agree to receive messages. You must state whether consent is collected through a web form with a consent checkbox, an SMS keyword, or an account checkout screen.

Vague opt-in descriptions and mismatched sample messages are the most frequent causes of carrier rejections. Carriers insist that recipients knowingly consent to receiving messages before the first text is dispatched.

Tracking carrier approval status

After you submit your details, your number enters carrier review. You can monitor the review progress in the console or through the API using the sending_status field:

sending_statusMeaning
registration_requiredA local number that requires A2P 10DLC business registration.
verification_requiredA toll-free number that requires toll-free verification.
pending_reviewSubmitted to carriers; reviews typically take one to two weeks.
approvedCarriers approved the registration; the number can send outbound SMS.
rejectedCarriers rejected the submission and provided a reason for correction.

If your submission returns rejected, read the carrier notes in the console, revise the opt-in description or sample templates, and submit the form again.

Registration fees and messaging prices

Carrier registration involves non-refundable review fees charged at submission, followed by recurring carrier maintenance charges:

ItemCost
Local or toll-free number leaseabout $1.32 a month (shown in the quote)
Business registration (A2P 10DLC)$23.40 per submission, then $1.80 a month while approved
Sole proprietor registration$23.40 per submission, then $2.40 a month while approved
Toll-free verificationFree
Outbound text (local number)$0.011 per segment
Outbound text (toll-free number)$0.013 per segment
Inbound text$0.006 per segment

A message segment consists of 160 plain characters using standard GSM encoding, or 70 characters if the message contains an emoji or special character. Concatenated messages that span multiple segments consume a few characters per segment for message headers.

Getting a number and checking status with the CLI

You can search for available US numbers, purchase them from your account credits, and assign them to a project using the vibiz CLI:

Terminal
# Search for local numbers by area code
vibiz phone search --area-code 415

# Buy the number and link it to your project
vibiz phone buy +14155550100 --project prj_123

# List your project's numbers and verify sending status
vibiz phone list --project prj_123

A number belongs to your primary account and attaches to one project at a time. The project tracks messaging usage against its daily limits. You can move numbers between projects or back to the root account using vibiz phone assign.

Sending SMS from your app

Once carriers mark your number as approved, you can send text messages using @vibiz/app or the CLI.

TypeScript
import { vibiz } from '@vibiz/app';

// Send a single transactional message
const message = await vibiz.phone.send({
  to: '+14155550123',
  text: 'Your order has shipped. Reply STOP to opt out.',
  idempotency_key: 'order-shipment-8941',
});

console.log(message.status); // 'sent'

From the terminal:

Terminal
vibiz phone send +14155550123 --text "Your order has shipped. Reply STOP to opt out." --yes

Key rules apply to application sending:

  • Single recipients: thelastapi delivers to one US recipient per call. Bulk marketing blasts are not supported.
  • Daily limits: Each project can send up to 200 text messages per UTC day. Messages can contain up to 1,600 characters.
  • Key permissions: An account owner key can initiate conversations with new numbers. A key with Limited access can only send messages to recipients who have already texted your number first.
  • Development sandbox: When testing with development credentials, messages do not leave the system. They are logged as simulated at zero cost.

Handling opt-outs and recipient compliance

Carriers mandate strict automated handling of unsubscribe requests. When a recipient replies with any of the following standard keywords: STOP, UNSUBSCRIBE, CANCEL, END, QUIT, REVOKE, or OPT OUT, the system automatically revokes sending privileges for that contact:

  • Subsequent attempts to text that phone number fail immediately with the error recipient_opted_out, and no credits are deducted.
  • An opt-out applies across all numbers under your account.
  • If a contact asks to stop during a phone call, they are flagged with the same opt-out protection.
  • The contact can restore messaging only by sending START from their mobile handset.
  • Replying HELP automatically sends a free text stating your project name and instructions on how to unsubscribe.

Inbound replies arrive at your application's configured webhook endpoint:

TypeScript
// app/api/vibiz/webhook/route.ts
export async function POST(req: Request) {
  const event = await req.json();

  if (event.type === 'phone.message.received') {
    const { from, text, keyword } = event.data.object;
    // Process inbound text as untrusted data
    console.log(`Received text from ${from}: ${text}`);
  }

  return new Response('ok');
}

Every incoming message payload is tagged with untrusted: true. Inbound texts represent external user input and must never be piped directly into internal administrative execution loops.

What to do next

Carrier registration takes one to two weeks, so submit your brand information as soon as you lease a number. While your 10DLC campaign is under review, you can write your message dispatch code, configure incoming webhooks, or test conversational voice handling in how to give an AI agent a phone number. If your app also delivers updates by inbox, see how to send transactional email from your app without touching DNS. Complete configuration details are available in the Phone documentation.

Frequently asked questions

How long does 10DLC carrier registration take?

Once submitted, mobile carriers usually take between one and two weeks to review your brand details, website, sample messages, and opt-in consent mechanism.

Can my application receive SMS while waiting for 10DLC approval?

Yes, incoming text messages and voice calls work immediately once a phone number is active; only outbound SMS is blocked until carrier approval is granted.

What happens if a recipient texts STOP to my number?

The platform automatically blocks all future outbound texts and calls to that recipient across your entire account, returning a recipient_opted_out error on future send attempts without charging credits.

How much does 10DLC registration cost?

Business registration costs $23.40 per submission and $1.80 per month while approved, while sole proprietor registration costs $23.40 per submission and $2.40 per month.