DLT details in one place
Your Principal Entity ID, sender IDs (headers) and content templates, each with its current approval status.
Documentation
Bulk SMS · DLT
A bulk SMS service provider in India sends high-volume text messages on operator networks under TRAI’s DLT rules, so every sender ID and template must be registered. Slovio sends OTPs, alerts and promotional SMS on your DLT-registered sender IDs and templates, from campaigns, workflows and the API. SMS is send-only, with delivery reports.
SMS at a glance
In India, every business SMS runs on the DLT framework. Slovio checks it before anything is sent.
Side by side
Every SMS in India goes out on a DLT template registered for its purpose. The category decides who it can reach and when.
| Compare | OTP | Transactional | Promotional |
|---|---|---|---|
| Used for | One-time passwords for sign-in and payments | Order, booking, delivery and account updates | Offers, launches and reminders to buy |
| Numbers on DND | Delivered | Delivered | Not delivered |
| Sending hours | Any time | Any time | 9 am to 9 pm |
| Sent from Slovio | The API or a workflow step | Workflows and the API | Scheduled campaigns to a CRM segment |
Used for
Numbers on DND
Sending hours
Sent from Slovio
Slovio queues an SMS only when its sender ID and template are both approved on DLT for that category.
SMS capabilities in Slovio
Registration details, sending and reporting in one place, so a message on an unregistered header or template is never queued.
Your Principal Entity ID, sender IDs (headers) and content templates, each with its current approval status.
A message is sent only when both its header and its content template are registered and approved.
Choose a sender ID and an approved template, fill in the variables, preview the message and schedule the send.
Search every message by recipient number or sender ID, with its delivery status and the amount charged.
Send SMS from a workflow step, or through the API for OTPs and alerts from your own systems.
Messages go only to countries your account is permitted to reach, and each send is charged to your wallet.
How it works
Add your DLT details once, automate the sends, then check every message in the delivery log.
Enter your Principal Entity ID, sender IDs and content templates, each with its approval status.
Schedule campaigns to segments, add SMS steps to workflows, or send OTPs and alerts through the API.
Search the delivery log by number or sender ID, and see sent, delivered and failed totals in Analytics.
Use cases
SMS reaches every mobile phone. Slovio keeps each message on a registered, approved template.
Send one-time passwords and account alerts from your application through the API, on an OTP template.
Automation texts the customer on a transactional template when an order ships or a ticket changes status.
Schedule a campaign on an approved promotional template for a CRM segment.
Payment and appointment reminders sent from the workflows your team already runs.
Part of the platform
What happens on SMS joins the same contact record as every other Slovio channel, so your team sees one history per customer.
DLT (Distributed Ledger Technology) is the registration framework for commercial SMS in India. A business registers as a Principal Entity, then registers its sender IDs, known as headers, and its message templates with an operator. Slovio lets you record all three and sends only on approved header and template combinations.
Transactional SMS carries information a customer needs, such as order updates and account alerts, while promotional SMS carries offers and marketing. OTPs are a separate category. In Slovio, each content template is recorded as Transactional, OTP or Promotional, so every campaign and automated message is sent on a template registered for its purpose.
Yes. Under TRAI’s rules, every business that sends commercial SMS in India must register on an operator’s DLT platform as a Principal Entity, together with its sender IDs and message templates. Operators block messages that do not match a registered header and template. Slovio records your DLT details and refuses to queue any SMS whose header and template are not both approved.
No. SMS in Slovio is send-only: it delivers OTPs, alerts and promotions, and replies to those messages are not received in Slovio. For two-way conversations, use a channel such as WhatsApp or RCS, where replies reach the Slovio Team Inbox and can be answered by AI Agents or your team, with the history kept in Slovio CRM.
Yes. You can send one-time passwords and account alerts through the Slovio API or from a workflow step in Slovio Automation. Each message uses a sender ID and an OTP or transactional template registered for that purpose, and every send is recorded in the SMS delivery log with its status and charge.
In Slovio you choose a sender ID and an approved template, fill in the template variables and preview the final message. You then select your audience, such as a CRM segment, and choose whether to send immediately or at a scheduled time. Delivery status for each message appears in the SMS delivery log.
Slovio charges each SMS to your account wallet at the time of sending. Rates depend on the destination country, and your account can send only to the countries it is permitted to reach. The delivery log shows the amount charged for every message. See the pricing page, or contact our team for current rates.
Add your DLT details once, then send campaigns, OTPs and alerts that are validated before they leave.