SMS

What is A2P vs P2P messaging?

A2P is business or application messaging to people; P2P is personal messaging between individuals.

A support agent can type a message by hand and still send business traffic. A passcode can contain no advertising and still need a sender approved for application messaging.

What makes a message A2P or P2P?

A2P covers messages sent by applications or on behalf of businesses. P2P covers individuals texting each other personally.

The label alone does not settle every carrier's classification. Twilio's classification guide treats messaging through its platform as A2P in the US and Canada.

The CTIA principles distinguish consumer from non-consumer traffic by the sender's role. Someone acting for a business remains a non-consumer sender even when typing on a phone.

For example, a friend texting your personal number is personal communication. A shop employee texting an order update on the shop's behalf is business communication. The friendly tone does not change that role.

Is every A2P message promotional?

A2P includes service messages and conversations as well as promotions.

A passcode, delivery notification or support reply can come from an application without advertising anything. Classifying it as A2P answers how the carrier treats the traffic. It does not by itself decide what permission you need for the message's content.

Keep those decisions separate in your application. SMS consent models explains matching permission to the program and destination.

What is a gray route?

A gray route carries business traffic over a path the service provider has not authorized for it.

CTIA section 5.5.3 advises senders against those routes. Confirm that your provider permits your use case on the route you buy, so cheaper transport does not bypass its controls.

A related pattern is snowshoe messaging: distributing similar messages across numbers to evade detection or limits. CTIA section 5.5.2 advises against it. Using several numbers for a legitimate program needs the provider's applicable arrangements.

Adding senders does not convert a business campaign into personal traffic. Carrier filtering explains how to investigate a blocked message.

What does registration establish?

Registration identifies the business and its intended traffic where the carrier or destination requires it.

US business messaging over local ten-digit numbers uses the 10DLC registration system. The Campaign Registry records brands and campaigns for that system.

Other sender types have their own requirements. A toll-free number does not use the same registration path as a local number. Sender registration and sender types explain the choices.

Registering the sender does not grant permission from recipients. Collect consent separately so a registered campaign does not become unwanted traffic.

How do I configure business sends in Bird?

You choose an eligible sender for each free-text request. Set the message's purpose on that request.

In the SMS send request, use from for a sender your workspace holds. Use category to identify the purpose, such as marketing, transactional or authentication. That field does not let you declare business traffic to be P2P.

Where registration is required, use a sender registered for the destination and intended use. Follow the 10DLC guide for US local numbers. The destination pages publish country-specific requirements.

For a template send, Bird derives the category. It also selects the sender. The template request rejects from and category alongside template. Inspect those values in the response to see what Bird selected.

In short

  1. A handwritten business message is still business traffic.

    The sender's role matters even when a person writes the text or the exchange is conversational.

  2. A2P includes service messages.

    Passcodes, appointment reminders and customer-support exchanges are not automatically P2P because they contain no promotion.

  3. Use a route permitted for the traffic.

    Carrier requirements depend on the destination and sender type. Registration does not replace recipient consent.

  4. Rotating numbers does not change the classification.

    Spreading similar messages across numbers to evade controls is snowshoe messaging, which CTIA advises against.

Build on the same network.

A test API key is yours immediately. Production unlocks when you add a payment method and verify a sender.

Your next idea.
Ready to connect.