Send us your destinations, traffic type, sample content, expected volume and preferred sender ID.
We confirm sender requirements, any required registration, and the appropriate route for your traffic.
Once the setup is complete, you can start sending through the agreed didlogic messaging setup.
| Traffic type | Examples | What to expect |
|---|---|---|
| Transactional SMS | Order updates, delivery notices, appointment reminders, account alerts | Supported across relevant destinations, subject to destination-specific requirements |
| Verification and OTP SMS | One-time codes, login confirmation, account recovery | Supported across relevant routes and destinations, subject to local restrictions |
| Customer-service messages | Service updates, user notifications, account communication | Availability depends on destination and message content |
| Promotional and marketing SMS | Offers, product announcements, campaign sends | Supported where the destination and available route permit promotional traffic |
Customers rely on didlogic for global telecom services across markets. Here’s what they say about working with us, from setup and support to service reliability.
A2P (application-to-person) SMS is messaging sent from a business application or system to an individual. Common examples include OTP codes, order updates, account notifications, appointment reminders and promotional messages.
A2P SMS is sent by an application or business system to an individual.
P2P SMS is person-to-person messaging, normally sent from one phone number to another.
The two can use different routing, sender formats and compliance processes.
No.
A DID is not required for standalone outbound A2P SMS. Messages can be sent using an approved alphanumeric sender ID instead.
If you want messaging tied to a didlogic phone number, that is a separate SMS-enabled DID setup.
The sender ID is the name or number shown in the message sender field.
For standalone A2P SMS, an alphanumeric sender ID can display your company, product or service name instead of a phone number where supported.
No.
The sender should clearly relate to your company or service. Misleading or inappropriate sender IDs are not accepted.
Some countries additionally require sender registration before the selected sender can be delivered unchanged.
Where a destination requires formal mobile-network registration, didlogic can support the registration process as part of the setup.
Not every destination requires sender registration.
An approved sender ID also has to be assigned to the customer’s didlogic account before it is used for sending.
didlogic provides A–Z A2P coverage.
What varies is the traffic type, sender format and content that can be supported in each destination.
Send us your countries and use case and we will confirm the applicable setup.
Yes.
OTP and verification SMS are supported use cases, subject to destination-specific routing and restrictions.
Yes.
Transactional messaging such as notifications, account alerts and service updates is supported across relevant destinations.
Yes, where the destination and route support promotional traffic.
Promotional messaging can have more restrictions than transactional or OTP traffic, so availability must be checked for the countries involved.
Yes.
In some destinations, local network or regulatory requirements can overwrite the submitted sender ID.
In some destinations, yes.
Local requirements or network behaviour can result in content being modified or supplemented before it reaches the recipient.
Pricing depends on the destination and the number of SMS segments sent.
A long message can consist of multiple segments, and each segment is charged separately.
Because SMS is billed by segments.
Long messages are split into several segments. The encoding used by the message also affects the number of characters available per segment.
Unicode characters, non-Latin scripts, emoji and some special characters can therefore increase the number of segments.
Not across most destinations.
Short codes are generally specialised, high-volume messaging products available only in selected markets.
Alphanumeric sender IDs are primarily used for one-way A2P messaging.
If you require two-way SMS, discuss an SMS-enabled DID setup with didlogic.
Send us:
We will confirm the relevant setup for your traffic.