01
Confirm local-number availability
Review country and carrier coverage for the specific destination. A local long number, two-way capability, or sender type may not be available for every use case.
API Messaging for Local Long Numbers
Connect a local long-number workflow to your application. A guided path from sender identity to API-enabled messaging.
Explore the local long-number messaging workflow for teams that need to connect a supported sender to their own application through the documented ProTexting API capabilities.
Available in the platform Human setup support Free trial available
How it works
International messaging is never one universal configuration. Sender type, number availability, registration, carrier rules, destination, and use case must be confirmed before an API integration or campaign is designed.
Start with the workflow that fits your team today, then use shared audiences, inbox activity, and reporting as your messaging program grows.
02
Complete sender requirements
Registration, verification, and other carrier processes may apply. Treat them as managed approval steps rather than assuming immediate activation or throughput.
03
Build against the documented API
Use the public API documentation and implementation guidance for the supported messaging, contact, delivery-report, keyword, or data-feed capabilities your application needs.
04
Plan the customer interaction
Once a sender and workflow are approved, use permissioned messaging for relevant notifications, replies, reminders, surveys, or keyword journeys—and measure the actual outcome.
Start with your real workflow
Bring the conversation into one place
Try the full platform free, then add the tools and integrations your team needs.