Use these as message drafts, then map them to your DLT portal
The bracketed labels below describe the information to insert. They are editorial placeholders, not universal DLT variable syntax. Replace [Brand] with your actual brand wording, then use your registrar's current variable tags and validation rules.
Jio TrueConnect's content-template guide shows a workflow for choosing the communication type, category and header, entering message content, adding variable tags and reviewing sample values before submission. Its current guide also distinguishes tag types such as numbers, URLs and contact details. Follow the options available to your entity. Read the registrar's guide.
For the registration process, use MetaReach DLT support. This page focuses on wording, variable mapping and test preparation. Once your template is live, send it through MetaReach's SMS API — see the SMPP vs HTTP SMS API guide if you're still choosing an integration method.
12 SMS template examples for business workflows
Copy a draft, replace its fields and prepare realistic sample values for review. Keep the final fixed wording consistent with the version approved for sending.
01. Login code
Your [Brand] login code is [OTP]. It expires in [Minutes] minutes. Do not share this code.
Customer-requested authentication; choose the category approved for your entity and use case.
02. Order confirmation
[Brand]: Order [OrderID] is confirmed. Your order total is Rs [Amount]. We will notify you when it is dispatched.
An existing order; keep promotional offers out of this notification.
03. Dispatch update
[Brand]: Order [OrderID] has been dispatched. Expected delivery: [Date]. Track your order: [TrackingURL]
An existing shipment; use the permitted, registered tracking link.
04. Appointment reminder
[Brand]: Your appointment is scheduled for [Date] at [Time]. For changes, contact [SupportNumber].
A booked appointment; insert only the details needed by the recipient.
05. Fee reminder
[Brand]: Fee payment of Rs [Amount] for reference [Reference] is due on [Date]. Please ignore if already paid.
A current account or student relationship; reconcile payments before sending.
06. Payment received
[Brand]: We received Rs [Amount] for reference [Reference] on [Date]. Thank you.
A confirmed payment event; do not send before reconciliation.
07. Renewal reminder
[Brand]: Your subscription [Reference] expires on [Date]. Review renewal details in your account.
An existing subscription; additional promotional content changes the purpose.
08. Support update
[Brand]: Support ticket [TicketID] is now [Status]. View the update in your account or contact [SupportNumber].
A real support case; limit the status variable to approved operational wording.
09. Service appointment
[Brand]: Your vehicle service appointment is confirmed for [Date] at [Time]. Reference: [Reference].
A booked service visit; avoid putting sensitive identifiers in the text.
10. Sale announcement
[Brand]: Our [EventName] sale runs until [Date]. View eligible offers at [OfferURL]. Terms apply. Manage preferences: [PreferenceURL]
Marketing content; use the appropriate promotional/consent setup and a working preference route.
11. Event invitation
[Brand]: Join our [EventName] on [Date] at [Location]. Details: [EventURL]. Manage preferences: [PreferenceURL]
Check audience permission and the approved communication category.
12. Hindi appointment
[Brand]: आपकी अपॉइंटमेंट [Date] को [Time] बजे है। बदलाव के लिए [SupportNumber] पर संपर्क करें।
A Hindi service-message draft; confirm Unicode support and final segment count.
Prepare a variable map before submission
| Field | Illustrative value | What to check |
|---|---|---|
| Brand | Example Store | Use the brand wording associated with your entity |
| OrderID | ORD7824 | Choose the permitted variable type; preserve the order-reference format |
| Amount | 1499 | Use sample values that follow the selected tag rules |
| Fixed wording | Order … is confirmed. | Keep the purpose and surrounding text consistent |
Use actual test values rather than leaving every variable as "test". Include a long but realistic name or reference in preflight testing. Review the fully substituted message in the SMS character and segment counter.
For links or callback numbers, follow the current registration and whitelisting requirements shown by your registrar. A copied URL placeholder does not make a destination approved.
Find the difference between an approved template and a failed message
Compare the approved fixed text, variable order, actual values and selected identifiers. Copying from a document editor can introduce curly quotes, extra line breaks or invisible characters. Review the actual request payload, not only the text shown in your campaign editor.
| Change | Why it needs review |
|---|---|
| Adding a discount sentence to an order update | Changes the message purpose and fixed content |
| Sending a full URL in a numeric variable | Does not fit the selected variable type |
| Using an old template ID with new wording | The request and approved version may not match |
| Changing the brand or header | Entity/header/template association needs checking |
Use the rejection explanation from your registrar or sending provider to decide what to correct. Avoid repeatedly submitting unchanged content. The SMS delivery failure guide helps distinguish a template check from another delivery problem.
Keep an approved-message record your team can use
For each use case, record the owner, approved text, template ID, header, variable map, sample message and latest approval status. When wording changes, update the record and the application together.
- Confirm the intended recipient group and communication purpose.
- Prepare the draft and realistic sample substitutions.
- Submit through the registrar and check the actual outcome.
- Map the approved configuration into your SMS platform.
- Run a small controlled test, then inspect its delivery report.
Use service and transactional SMS support for operational alerts and promotional SMS services for campaign planning. Consent-template registration is a separate workflow described in Jio's consent-template guide.
Frequently asked questions
Can I send these drafts without template approval?
These are illustrative drafts, not pre-approved templates. Use your entity's registrar workflow and the configuration required by your sending provider before launch.
Should I paste the bracketed labels into the DLT portal?
No. The labels describe fields to replace. Insert your real fixed brand text and use the variable tags offered by your registrar for the changing values.
Are all OTPs and order updates in one universal category?
Do not infer the category from the short example alone. Confirm the appropriate communication type for your entity, message purpose and recipient relationship.
Can I change fixed words after a template is approved?
Review the change against the approved version and registrar requirements. Update approval and application mapping where necessary before sending the revised content.
Discuss your SMS setup with MetaReach
Share your use case, current platform and expected message volume. Our team can help you define the configuration and next steps.
Discuss DLT template setupSales: +91 7669990407 · Send an enquiry
Technical references
- Jio TrueConnect — content template registration guide
- Jio TrueConnect — consent template registration
Examples on this page are illustrative. Confirm provider-specific settings against your current account documentation.
