Transactional SMS for Alerts and Updates
Deliver order confirmations, payment alerts, dispatch updates and account notifications round the clock on priority routes with your own DLT sender ID, on delivery based billing - failed messages are credited back.
Your personal support executive.
Based on 1000+ feedbacks
Technical Specification
A transactional gateway built for production alert traffic
Why Choose DV Connect for Alerts?
The messages your customers are actually waiting for, delivered round the clock
When somebody places an order, makes a payment or books an appointment, they expect a message within seconds. Transactional SMS runs on priority routes, is permitted around the clock and reaches DND registered numbers, because it is information the customer asked for rather than marketing.
Every message carries your own six character sender header, so the alert is recognisably yours the moment it arrives. Send from the panel for one-off notices, or wire the REST API into your order and billing systems and forget about it.
Our pricing includes DLT scrubbing, so the rate quoted on the plan is the rate you actually pay - there is no separate scrubbing fee, platform fee or setup charge added later. Billing is delivery based on top of that: every message our gateway reports as undelivered is credited straight back, so a failed alert costs you nothing at all.
What Our Clients Say About Our Messaging Service
Feedback from ecommerce, finance, education and service businesses
Order and dispatch alerts run entirely through the API now. It has been steady for months and the delivery report tells us exactly what landed.
Having our own sender header made a visible difference to how customers treat the messages. Fewer "is this real" calls.
DLT paperwork was handled end to end by the team. We just supplied documents and were live in a few days.
Round the clock delivery matters for us because most bookings happen at night. No complaints so far.
Alerts On Other Channels
What businesses usually run alongside transactional SMS
OTP SMS
One time passwords on priority routes, with no DLT template needed to start.
WhatsApp API
The same alerts on WhatsApp, sent from your own linked number.
Voice OTP
A spoken code for customers who did not read the SMS.
Rich RCS Messaging
Branded alerts with your logo and a verified tick in Google Messages.
Frequently Asked Questions
DLT registration, sender IDs, timings, templates and the API
Yes. TRAI requires a registered entity, a registered sender header and an approved content template for every transactional message. Nothing can be delivered without all three. Our team will help you complete the full registration.
Entity registration is usually approved within 2 to 3 working days, and header and template approval within another 1 to 2 days, depending on the operator.
Your GST certificate or business registration proof, PAN, an authorised signatory letter and a company email address. We guide you through the exact list for your entity type.
Any message sent because of something the customer did or something they hold with you: an order confirmation, payment receipt, dispatch update, appointment reminder, renewal notice or account alert. Offers and marketing must go on a promotional route.
Yes. Transactional SMS is delivered to DND registered numbers. Service traffic sent against an approved DLT template is exempt from the DND block, because the customer has an existing relationship with you, so order, payment and dispatch alerts reach your entire list rather than only the part of it that is not registered.
Yes. Unlike promotional SMS, transactional messages are permitted around the clock, so overnight order and payment alerts go out immediately.
Yes. Once your six character header is approved on DLT, every message shows your brand instead of a random ID.
A DLT template contains placeholders, for example "Your order {#var#} has shipped". You supply the values at send time through the panel or the API, and the fixed wording stays as approved.
The message is rejected by the DLT platform before it is charged. The panel shows the rejection reason so the template can be corrected and resubmitted.
No. A failed alert costs you nothing. Billing is delivery based, so any message our gateway reports as undelivered is credited straight back to your account and you pay only for alerts that actually reached a handset.
No. DLT scrubbing is already included in the per SMS rate shown on every plan. There is no separate scrubbing line on your bill and nothing is added for it later.
No. You pay for credits and nothing else. There is no setup fee, no monthly platform fee and no scrubbing fee, and because billing is delivery based you are never charged for a message that did not reach a handset.
English text is billed by length: up to 160 characters counts as 1 message, up to 306 as 2, up to 459 as 3, up to 612 as 4, up to 765 as 5, up to 918 as 6, up to 1071 as 7, up to 1224 as 8 and up to 1377 as 9. Each message in that count consumes one credit, so a 200 character alert uses 2 credits.
Non-English Unicode text is billed at 64 characters per message instead of 160, so the same wording uses more credits in a regional script than it does in English. Hindi, Marathi, Gujarati, Bengali, Tamil, Telugu, Kannada, Punjabi and other Indian scripts are supported.
Query the delivery status API with the message id returned when you sent the alert, and it responds with the current status for that message. A full delivery report is also available in your panel and can be exported. Status is pulled by your system when it needs it rather than pushed to a webhook.
No. Transactional credits stay in your account until they are used.
Comparing Transactional SMS Providers
If you are comparing DV Connect with Fast2SMS, MSG91, Twilio or the provider you use today, these are the questions worth putting to any of them. We have answered each one for DV Connect; ask the same of the others and compare the answers rather than the headline rate.
Does the rate include scrubbing, even on failed messages?
Ours does. Where a provider bills DLT scrubbing per message submitted, a message that never reaches the handset still costs you the scrubbing fee. Our published rate includes scrubbing, there is no setup or platform fee, and an undelivered message consumes nothing at all.
What happens to a message that is not delivered?
Nothing is charged. Billing is delivery based, so a message our gateway reports as undelivered does not consume a credit.
Do the credits expire?
No. Credits stay in your account until they are used, so you can buy at a volume rate and spend it across the year.
How many accounts do you need?
One. SMS, RCS, voice, IVR, WhatsApp and Telegram all run from the same login, the same balance and one set of GST invoices.
Who handles the DLT paperwork?
Our team helps with entity registration, sender header approval and template drafting, usually completed in two to three working days.
How do you reach support?
By call, ticket or WhatsApp, 24/7, from the company that runs the gateway rather than a reseller passing the message along.
What Is Transactional SMS?
A transactional SMS is a message sent because of something the customer did or something they hold with you: an order confirmation, a payment receipt, a dispatch update, an appointment reminder, a renewal notice or an account alert. The customer is expecting it, and it carries information rather than an offer.
That distinction is what TRAI regulates. Service and transactional traffic sent against an approved DLT template is delivered to numbers on the DND register and is permitted around the clock, so an overnight payment alert goes out immediately. Marketing content cannot be sent this way, and routing an offer through a transactional template breaches both the regulations and our terms.
Each message carries your own six character sender header, so the alert is recognisably yours the moment it arrives. Most businesses send these from their order or billing system through the API rather than by hand.