Sender identity & delivery reporting
Provide the destination, message use case, sender identity and expected volume. Sender registration, delivery reporting and country requirements must be confirmed before launch.
A2P messaging
The right message. Delivered.
Transactional and promotional messaging for customer communications.
Discuss your requirementsDESIGNED AROUND YOUR BUSINESS
The right message. Delivered.
Connect applications and customer communications through A2P messaging. Discuss your transactional or promotional use case, destinations and delivery requirements.
- Transactional messages
- Customer notifications
- Promotional campaigns
Define the details. Connect with confidence.
Availability and specifications are subject to confirmation in your proposal.
Throughput & monitoring
Share your peak messages per second and reporting needs. Throughput, monitoring scope, escalation and any alternate delivery arrangements require confirmation.
Message profile & launch preparation
Share sample templates, destination mix, sender identity, expected language and peak messages per second. Review sender-registration steps, consent requirements, opt-out handling and delivery-report meanings for the proposed destinations before launch.
Understand the billable unit
Request pricing per destination and clarify whether billing is per submitted message, delivered message or segment. Ask how encoding and long messages affect segment counts, and how expiry, retries and failed delivery are treated. Confirm throughput and commercial terms in the written proposal.