Alerts and notifications
Order updates, reminders, delivery alerts and service notices.
Send application-to-person messages for notifications, verification, support and opt-in campaigns—connected to your numbers and business systems.
Jump to the sections you need.
A2P stands for Application-to-Person. A2P messaging lets software send messages to customers at scale, instead of relying on individual person-to-person chats.
Businesses use A2P messages for time-sensitive alerts, verification codes, service updates and permission-based marketing.
A2P programs are built around consent, sender verification and carrier rules, so messages reach the right person with a clear business identity.
Choose the message flows that fit each stage of the customer journey.
Order updates, reminders, delivery alerts and service notices.
Verification and account-security messages where the use case permits.
Two-way conversations for questions, scheduling and account help.
Opt-in campaigns, offers and re-engagement messages with clear consent.
Use an API or business platform to trigger messages.
Select the number type and channel that fit each market.
Deliver notifications, codes, updates or campaigns.
Process responses, STOP/HELP requests and delivery events.
Connect messaging to your product, CRM or service platform.
Let customers reply, ask questions and continue the conversation.
Track message status and operational performance.
Use 10DLC, toll-free or mobile numbers where available.
Collect, record and honor opt-in and opt-out preferences.
Support growing volumes across teams and use cases.
A2P messaging depends on clear consent, accurate sender identity and carrier-compliant content. These checks apply before and after launch.
Collect consent before the first message. Record the number, date, source and the exact wording the recipient agreed to.
Explain what will be sent, how often, that message and data rates may apply, and how to opt out.
Honor STOP, UNSUBSCRIBE, CANCEL, END and QUIT promptly. Support HELP and keep suppression lists in sync.
Complete the registration required by the number type: 10DLC brand and campaign, toll-free verification or local rules.
Avoid prohibited or restricted content, including SHAFT categories (sex, hate, alcohol, firearms, tobacco) where carrier rules apply.
Respect local quiet-hour and time-of-day rules, especially for marketing and non-urgent messages.
State the expected frequency in your opt-in and keep actual sending consistent. Include your business name and opt-out instructions in the first message or at a reasonable interval.
Keep the records that support your program:
Carriers may filter or throttle traffic that does not match registration, consent or content rules. Monitor delivery, investigate sudden changes and keep throughput aligned with your registered use case.
Rules differ by country, carrier and number type. Confirm local requirements, sender registration and content restrictions before launching in a new market.
This page provides general guidance, not legal advice. Requirements vary by carrier, country and use case; confirm your program with your legal and compliance teams.
Use this checklist before launch, then review it whenever your program changes.
Requirements vary by market, carrier and number type. This checklist is a starting point, not a substitute for carrier or legal review.
Use these examples as a starting point, then adapt them to your program and local requirements.
By providing your mobile number, you agree to receive [program name] messages from [business name] at that number. Message frequency varies. Message and data rates may apply. Reply HELP for help or STOP to opt out. See [privacy policy link].
[Business name]: Your verification code is 123456. It expires in 10 minutes. Do not share this code. Reply HELP for help or STOP to opt out.
Examples only. Adapt the language to your use case, market and legal requirements.
Practical answers for the operational side of an A2P compliance program.
Identify the business and program, explain the message purpose and expected frequency, note that message and data rates may apply, and explain how to opt out and get help.
Identify the sender, confirm the program or purpose, include opt-out and HELP instructions, and link to your privacy policy where required.
Record the phone number, date, time, source, campaign and the exact wording the recipient agreed to. Keep the record for as long as required.
Honor opt-outs promptly and apply them across all campaigns and systems. Confirm the timing required for each market and number type.
A list of numbers that must not receive messages, including opt-outs, complaints and invalid numbers. Keep it synchronized across systems.
Treat a withdrawal as an opt-out, stop non-essential messages, and update your suppression list. Do not require the recipient to take extra steps.
Consent records, campaign registration, message templates, opt-out logs, delivery reports and complaint handling. Retention periods vary by market.
Review whether the change affects your registration, opt-in disclosure or carrier review. Update templates and registration before sending materially different content.
Investigate the source, stop messages if needed, respond to the recipient and correct the program. Track patterns and report abuse where required.
Consent, opt-out and content rules vary by country and channel. Confirm local requirements before launching and keep market-specific records.
Protect your sender identity, API credentials and recipients.
Use strong credentials, rotate keys and restrict access by role.
Watch sudden spikes, repeated failures and unusual destinations.
Reconfirm consent for high-risk programs and remove stale numbers.
Use recognizable domains and avoid misleading or unexpected links.
Track opt-outs, HELP requests and carrier feedback; investigate spikes.
Have a plan for compromised accounts, abuse reports and service interruptions.
Security requirements depend on your systems, providers and market.
Rules vary by market. Confirm these areas before launching in a new country.
Some markets require sender IDs, local registration or pre-approval.
Consent wording and opt-out rules may differ by country and channel.
Respect local time-of-day and holiday restrictions.
Some categories are restricted or require age gating.
Keep records for the period required by local law and your contracts.
Provide disclosures and opt-out instructions in the required language.
This is general guidance, not legal advice. Confirm local requirements with your legal and compliance teams.
Practical answers about consent, registration, content, security and delivery.
A2P messaging is sent by an application or business to customers at scale. P2P messaging is a person-to-person conversation. A2P programs usually require consent, sender verification and carrier review.
Common options include 10DLC, toll-free and mobile numbers, depending on the market, use case and carrier rules.
Some number types, including US 10DLC, require brand and campaign registration. We can confirm the requirements for your target markets.
Brand and business identity, campaign use case, sample messages, opt-in description and opt-out handling are commonly required. Exact requirements vary by carrier and campaign type.
10DLC uses local 10-digit numbers with brand and campaign registration. Toll-free messaging uses 800-style numbers with a separate verification process. Throughput and content rules differ.
Yes, where the channel and number type support two-way messaging. Replies can be routed to your team or business system.
Pricing depends on numbers, registration, channels and message volume. Contact our team for a quote based on your use case.
Honor STOP, HELP and other requests promptly, and keep suppression lists in sync with your messaging platform.
At minimum, support STOP and HELP; many carriers also expect UNSUBSCRIBE, CANCEL, END and QUIT. Confirm the keyword set for each market and number type.
Maintain a central suppression list and apply opt-outs across all campaigns and systems, unless the recipient explicitly opts back in.
Express opt-in is clear consent to receive messages at a specific number. Keep the number, date, source and exact wording the recipient agreed to, and make sure the consent matches the messages you send.
Use a clear opt-in mechanism such as a web form, keyword, IVR or in-app prompt. Record the number, date, source and exact wording of the consent.
No. Consent is channel- and program-specific unless your opt-in clearly covers SMS and the specific messages you send.
Double opt-in asks the recipient to confirm by reply or link. It is not always required, but it can strengthen consent records and reduce abuse.
SHAFT refers to sex, hate, alcohol, firearms and tobacco. Carrier rules often restrict or require additional review for these categories; some use cases may not be permitted at all.
Quiet-hour and time-of-day rules vary by market and message type. They are most relevant to marketing and non-urgent messages; transactional alerts may be treated differently.
Throughput is the rate at which messages can be sent. It depends on the number type, registration and carrier rules. Keep expected volume aligned with your registered use case.
Registration is market-specific. US 10DLC, toll-free and other number types have different requirements; confirm the rules for every country before launch.
Review consent, registration details and content, then check for sudden volume or template changes. Work with your provider to investigate delivery and adjust the program.
Purchased or scraped lists are not a substitute for consent. Only message recipients who have agreed to receive your messages, and keep records of how consent was collected.
Use recognizable domains and avoid misleading links. Some carriers filter shortened or mismatched URLs, so confirm current rules.
Smishing is phishing by SMS. Identify your brand, avoid unexpected links, keep content consistent with your registered campaign, and monitor complaints.
Numbers can be reassigned. Reconfirm consent for high-risk programs, honor opt-outs and avoid relying on stale lists.
Review the rejection reason, correct registration or content issues, and resubmit. Work with your provider to address carrier concerns.
These are sensitive use cases with additional rules. Confirm content, consent and registration requirements with your legal and compliance teams before launch.
Track opt-outs, HELP requests, delivery failures and carrier feedback. Investigate spikes and adjust content, frequency or targeting.
Many programs should include a privacy policy link or reference in the opt-in flow or messages. Confirm local requirements and your own privacy obligations.
Only if your opt-in covers cart reminders and the channel. Confirm local rules and include clear opt-out instructions.
No, unless you can document consent for your brand and program. Purchased or affiliate lists are not a substitute for your own consent records.
Additional restrictions and age-gating may apply. Confirm carrier rules and legal requirements before launching.
Political and advocacy messaging is highly regulated and may be restricted by carriers or local law. Confirm requirements before launching.
Tell us about your use case, expected volume and target markets. We will help you review numbers, registration and messaging flows.