Get a Quote +852-58013888
A2P Messages

A2P messaging for business conversations

Send application-to-person messages for notifications, verification, support and opt-in campaigns—connected to your numbers and business systems.

Overview

What is A2P messaging?

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.

APIBusiness integration
2-wayCustomer replies
Opt-inConsent-based programs
Message Types

Messages your customers expect

Choose the message flows that fit each stage of the customer journey.

Alerts and notifications

Order updates, reminders, delivery alerts and service notices.

One-time passcodes

Verification and account-security messages where the use case permits.

Customer support

Two-way conversations for questions, scheduling and account help.

Marketing and promotions

Opt-in campaigns, offers and re-engagement messages with clear consent.

How It Works

Connect your systems and start sending

01

Connect your system

Use an API or business platform to trigger messages.

02

Choose numbers and channels

Select the number type and channel that fit each market.

03

Send messages

Deliver notifications, codes, updates or campaigns.

04

Handle replies and opt-outs

Process responses, STOP/HELP requests and delivery events.

Features

Built for reliable, two-way communication

API integration

Connect messaging to your product, CRM or service platform.

Two-way messaging

Let customers reply, ask questions and continue the conversation.

Delivery reporting

Track message status and operational performance.

Number choice

Use 10DLC, toll-free or mobile numbers where available.

Consent management

Collect, record and honor opt-in and opt-out preferences.

Scalable sending

Support growing volumes across teams and use cases.

Compliance

Build consent, opt-outs and registration into every program

A2P messaging depends on clear consent, accurate sender identity and carrier-compliant content. These checks apply before and after launch.

Express opt-in

Collect consent before the first message. Record the number, date, source and the exact wording the recipient agreed to.

Clear disclosures

Explain what will be sent, how often, that message and data rates may apply, and how to opt out.

Opt-out handling

Honor STOP, UNSUBSCRIBE, CANCEL, END and QUIT promptly. Support HELP and keep suppression lists in sync.

Sender registration

Complete the registration required by the number type: 10DLC brand and campaign, toll-free verification or local rules.

Content rules

Avoid prohibited or restricted content, including SHAFT categories (sex, hate, alcohol, firearms, tobacco) where carrier rules apply.

Quiet hours

Respect local quiet-hour and time-of-day rules, especially for marketing and non-urgent messages.

Message frequency and disclosures

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.

Records and suppression lists

Keep the records that support your program:

  • Opt-in and opt-out records, including date, source and consent wording.
  • Campaign content, templates and registration details.
  • Delivery logs, complaints and suppression-list changes.

Filtering and throughput

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.

International programs

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.

Compliance Checklist

Registration and content checklist

Use this checklist before launch, then review it whenever your program changes.

Before launch

  • Business identity and registration details.
  • Campaign use case and sample messages.
  • Opt-in description and source.
  • Opt-out and HELP handling.
  • Volume estimates and throughput.
  • Privacy policy and terms links.

Ongoing

  • Monitor delivery, opt-outs and complaints.
  • Keep registration and content aligned.
  • Update templates when use cases change.
  • Retain consent and message records.
  • Review carrier policy changes.
  • Investigate filtering or reputation issues.

Requirements vary by market, carrier and number type. This checklist is a starting point, not a substitute for carrier or legal review.

Compliance FAQ

Consent, records and complaint questions

Practical answers for the operational side of an A2P compliance program.

What should an opt-in disclosure include?

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.

What should the first message include?

Identify the sender, confirm the program or purpose, include opt-out and HELP instructions, and link to your privacy policy where required.

How do I document consent?

Record the phone number, date, time, source, campaign and the exact wording the recipient agreed to. Keep the record for as long as required.

How quickly must I honor opt-outs?

Honor opt-outs promptly and apply them across all campaigns and systems. Confirm the timing required for each market and number type.

What is a suppression list?

A list of numbers that must not receive messages, including opt-outs, complaints and invalid numbers. Keep it synchronized across systems.

How do I handle consent withdrawal?

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.

What records should I keep for an audit?

Consent records, campaign registration, message templates, opt-out logs, delivery reports and complaint handling. Retention periods vary by market.

What should I do when message content changes?

Review whether the change affects your registration, opt-in disclosure or carrier review. Update templates and registration before sending materially different content.

How do I handle complaints?

Investigate the source, stop messages if needed, respond to the recipient and correct the program. Track patterns and report abuse where required.

How do international consent rules differ?

Consent, opt-out and content rules vary by country and channel. Confirm local requirements before launching and keep market-specific records.

Security

Security and fraud controls

Protect your sender identity, API credentials and recipients.

API and account security

Use strong credentials, rotate keys and restrict access by role.

Velocity and anomaly monitoring

Watch sudden spikes, repeated failures and unusual destinations.

Number reassignment checks

Reconfirm consent for high-risk programs and remove stale numbers.

Link and content review

Use recognizable domains and avoid misleading or unexpected links.

Complaint handling

Track opt-outs, HELP requests and carrier feedback; investigate spikes.

Incident response

Have a plan for compromised accounts, abuse reports and service interruptions.

Security requirements depend on your systems, providers and market.

International

International compliance considerations

Rules vary by market. Confirm these areas before launching in a new country.

Sender registration

Some markets require sender IDs, local registration or pre-approval.

Consent and opt-out

Consent wording and opt-out rules may differ by country and channel.

Quiet hours

Respect local time-of-day and holiday restrictions.

Content restrictions

Some categories are restricted or require age gating.

Data retention

Keep records for the period required by local law and your contracts.

Local language

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.

FAQ

Common questions about A2P messaging

Practical answers about consent, registration, content, security and delivery.

What is the difference between A2P and P2P messaging?

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.

Which number types can I use for A2P messages?

Common options include 10DLC, toll-free and mobile numbers, depending on the market, use case and carrier rules.

Do I need registration?

Some number types, including US 10DLC, require brand and campaign registration. We can confirm the requirements for your target markets.

What information is needed for 10DLC registration?

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.

What is the difference between 10DLC and toll-free verification?

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.

Can customers reply to A2P messages?

Yes, where the channel and number type support two-way messaging. Replies can be routed to your team or business system.

How is A2P messaging priced?

Pricing depends on numbers, registration, channels and message volume. Contact our team for a quote based on your use case.

How do I handle opt-outs?

Honor STOP, HELP and other requests promptly, and keep suppression lists in sync with your messaging platform.

Which opt-out keywords should I support?

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.

How do I handle STOP across multiple campaigns?

Maintain a central suppression list and apply opt-outs across all campaigns and systems, unless the recipient explicitly opts back in.

What is express opt-in, and what records should I keep?

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.

How do I collect consent for SMS?

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.

Can I message customers who opted in on another channel?

No. Consent is channel- and program-specific unless your opt-in clearly covers SMS and the specific messages you send.

Do I need a double opt-in?

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.

What is SHAFT content?

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.

Do quiet-hour rules apply to my messages?

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.

What is message throughput?

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.

Do I need a separate registration for each country?

Registration is market-specific. US 10DLC, toll-free and other number types have different requirements; confirm the rules for every country before launch.

What should I do if carriers filter my messages?

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.

Can I import or purchase a contact list?

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.

Can I use shortened URLs?

Use recognizable domains and avoid misleading links. Some carriers filter shortened or mismatched URLs, so confirm current rules.

What is smishing, and how do I avoid it?

Smishing is phishing by SMS. Identify your brand, avoid unexpected links, keep content consistent with your registered campaign, and monitor complaints.

What happens if a phone number is reassigned?

Numbers can be reassigned. Reconfirm consent for high-risk programs, honor opt-outs and avoid relying on stale lists.

What if my campaign is rejected or suspended?

Review the rejection reason, correct registration or content issues, and resubmit. Work with your provider to address carrier concerns.

Can I use A2P messages for healthcare, financial or debt collection?

These are sensitive use cases with additional rules. Confirm content, consent and registration requirements with your legal and compliance teams before launch.

How do I monitor complaints and delivery?

Track opt-outs, HELP requests, delivery failures and carrier feedback. Investigate spikes and adjust content, frequency or targeting.

Do I need a privacy policy link?

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.

Can I send abandoned-cart messages?

Only if your opt-in covers cart reminders and the channel. Confirm local rules and include clear opt-out instructions.

Can I use affiliate or third-party lists?

No, unless you can document consent for your brand and program. Purchased or affiliate lists are not a substitute for your own consent records.

Can I send age-restricted or regulated content?

Additional restrictions and age-gating may apply. Confirm carrier rules and legal requirements before launching.

Can I send political or advocacy messages?

Political and advocacy messaging is highly regulated and may be restricted by carriers or local law. Confirm requirements before launching.

Get Started

Plan your A2P messaging program

Tell us about your use case, expected volume and target markets. We will help you review numbers, registration and messaging flows.