SMS and email notifications
The messages that have to arrive — OTPs, receipts, alerts — and the unglamorous configuration that decides whether they do.
Notifications
Chosen per project
Maintainable handover
Transactional messaging looks trivial and fails in specific, predictable ways. In India, SMS requires DLT registration of both sender ID and template, and an unregistered template is simply not delivered. Email needs SPF, DKIM and DMARC configured or it lands in spam, particularly when sent from a new domain.
Neither is difficult. Both are routinely skipped, which is why so many businesses believe their OTPs are slow when in fact a proportion never arrive at all.
What we build with SMS and email
One-time passwords for login and verification
Order, dispatch and payment receipts
Appointment and due-date reminders
Internal alerts to staff when something needs attention
Where it fits — and where it does not
Good fit when
Messages triggered by an event in your system
Anything where non-delivery causes a support call
Communication that must be logged for a record
Consider something else when
Bulk marketing from a transactional sender, which damages deliverability
Sending without a suppression list for bounces and unsubscribes
Why a message does not arrive
In order of how often we find each one to be the actual cause.
Template not registered
DLT rejects it silently; nothing is delivered.
No SPF or DKIM
Mail is unauthenticated and filtered.
Shared reputation
Marketing volume sinks transactional mail.
Bounces ignored
Sending to dead addresses damages the domain.
How we work with SMS and email
DLT done properly
Sender ID and every template registered before go-live, with variable fields matching what the registration allows.
Email authentication
SPF, DKIM and DMARC configured and verified, so mail is authenticated rather than merely sent.
Separated streams
Transactional and marketing sent from different subdomains, so a campaign cannot damage OTP delivery.
Status recorded
Delivery receipts and bounces written back, so failures are visible and suppression lists stay current.
Our typical SMS and email setup
| Concern | What we use |
|---|---|
| SMS | Indian providers with DLT-registered sender IDs and templates |
| SendGrid, Amazon SES or similar, with authenticated domains | |
| Auth | SPF, DKIM and DMARC verified before launch |
| Separation | Distinct subdomains for transactional and marketing |
| Feedback | Delivery receipts, bounce and complaint handling |
Frequently asked questions
Often they are not slow — a share of them never arrive, usually because of a template mismatch against the DLT registration. Recording delivery receipts makes that visible immediately.
For commercial SMS to Indian numbers, yes. Sender ID and each template must be registered, and the message must match the registered template.
For most customer-facing updates in this market, WhatsApp gets read far more. SMS remains the more reliable fallback for OTPs and for customers who do not use WhatsApp.
Topics people search for
Services built with SMS and email
Custom Software Development
Software shaped around the way your business already works, instead of a packaged product you have to reorganise around.
Web Application Development
Applications that run in the browser, handle real workloads and hold up when several departments depend on them at once.
CRM Development
A sales system your team will actually keep up to date, because it matches the way they work.
E-commerce Development
Online stores where the checkout works, the stock figures are real and the order data reaches your operations team intact.
Tell us what you are trying to build
Describe the problem in plain language and we will tell you what it would take to solve it — the approach, the moving parts and the sensible order to build them in. No obligation either way.