SMS Template | Fyno Documentation

Overview

The SMS External Templates page provides a centralized view of all SMS templates registered on the TRAI Distributed Ledger Technology (DLT) platform and linked to your workspace.

IMPORTANT NOTE: Under the Telecom Commercial Communications Customer Preference (TCCCP) Regulations implemented by the Telecom Regulatory Authority of India (TRAI) in April 2021, all SMS messages sent by Principal Entities (PEs) must have their templates registered on the DLT platform, a blockchain-based system designed to monitor and prevent unsolicited commercial communications.

From this screen, you can:

View all templates across connected DLT providers.
Check template details such as approval status, type, category, and last synced time.
Search and filter templates by name, provider, status, or type.
Create a new SMS template and submit it for approval.
Save templates as drafts before submitting them.
Sync templates that already exist in your DLT account.

Each row in the list represents a single DLT template and shows its current status in Fyno.

Once approved, the template can be used to create a Fyno Template, which can then be used in Notification Events, Workflows etc.

Variables

Variables are dynamic placeholders used within templates to insert personalized or context-specific information at runtime. Instead of hardcoding values, variables allow you to reuse the same template while populating it with different data for each user or transaction.

Variables can represent different types of values, such as:

Numeric values (e.g., OTPs, transaction amounts).
Alphanumeric values (e.g., order IDs, usernames).
Text values (e.g., customer names, locations)

Mandatory Variable Tagging

All variable fields used in an SMS template must be pre-tagged with a defined data type and purpose. Only the data permitted by the respective tag can be populated at runtime.

Approved Variable Tags:

- {#numeric#} – OTPs, amounts, numbers.
- {#alphanumeric#} – Reference IDs, ticket numbers.
- {#url#} – Website links.
- {#urlott#} – OTT / App download links.
- {#cbn#} – Callback numbers.
- {#email#} – Email addresses.

All existing templates must be reviewed and updated to comply with these mandatory variable tagging norms.

Examples OTP (Numeric Variable): Your OTP is {{OTP}}. Do not share it with anyone. (Example value: 483921). Numeric Value (Transaction/Amount): Your payment of ₹{{amount}} has been successfully processed. (Example value: 1500). Alphanumeric Value (Order ID / Reference ID): Your order {{order_id}} has been shipped and will arrive soon. (Example value: ORD12345XYZ).

All the SMS providers are listed here:

How SMS External Templates work

Create in Fyno and submit to DLT You create the template in Fyno and send it to the selected DLT provider for approval. After approval and sync, it becomes available for sending SMS.

Sync from DLT If templates already exist in your DLT platform, use Sync to import them into Fyno. These templates are immediately available for use if already approved.

Manage lifecycle from one place Fyno acts as the control layer for managing your DLT SMS templates. You can create templates, submit them for approval, sync them with your DLT providers, and monitor their approval status from a single interface.

Change logs

The Change logs panel shows the history of updates made to a template.

It helps you track:

What was modified.
When it was modified.
Why a template went for re-approval.

A new entry appears when:

Message text is edited.
Variables are added or removed.
Buttons or links are updated.
Media is changed (image, video, document, etc.)

A new language is added.

The template is resubmitted after rejection.
This is useful when multiple team members work on the same template.