<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>The TextNation Blog</title>
    <link>https://textnation.in/blog/</link>
    <atom:link href="https://textnation.in/blog/feed.xml" rel="self" type="application/rss+xml" />
    <description>Guides on SMS, WhatsApp, RCS and voice messaging for Indian businesses.</description>
    <language>en-IN</language>
    <item>
      <title>CPaaS in November 2026: a $50bn market, TRAI&#39;s new anti-spam rules and the RCS climb</title>
      <link>https://textnation.in/blog/cpaas-news-november-2026/</link>
      <guid isPermaLink="true">https://textnation.in/blog/cpaas-news-november-2026/</guid>
      <pubDate>Wed, 04 Nov 2026 08:32:22 GMT</pubDate>
      <dc:creator>TextNation Product Team</dc:creator>
      <category>Industry news</category>
      <description>Business messaging this month: CPaaS forecast to pass $50bn by 2031, Twilio Q3 results, TRAI&#39;s Third Amendment on spam, RCS growth in India and WhatsApp&#39;s new…</description>
      <content:encoded><![CDATA[<p>Business messaging moved on several fronts this month: a new forecast for the whole market, quarterly numbers from its largest listed player, a tighter anti-spam rulebook in India, and more proof that RCS is going mainstream. Here is what happened and what it means if you send SMS, WhatsApp or RCS to customers in India.</p>
<h2 id="the-market-cpaas-on-course-to-pass-50-billion" class="tn-h">The market: CPaaS on course to pass $50 billion<a class="tn-anchor" href="#the-market-cpaas-on-course-to-pass-50-billion" aria-label="Link to this section">#</a></h2>
<p>On 2 November 2026, Juniper Research published its latest CPaaS forecast. It expects total CPaaS revenue to <strong>more than double over the next five years</strong>, from <strong>$21 billion in 2026</strong> to <strong>more than $50 billion by 2031</strong>.</p>
<p>Juniper names <strong>conversational AI and authentication</strong> as the main drivers. It also expects providers to &quot;capitalise on the decline of SMS&quot; by moving traffic to newer channels such as <strong>RCS</strong> and OTT apps such as <strong>WhatsApp</strong>.</p>
<p>Its 2026 vendor ranking puts <strong>Infobip</strong> first, followed by <strong>Twilio, Sinch, Vonage and Tata Communications</strong>.</p>
<p><strong>What it means for you:</strong> the growth is not in sending more plain SMS. It is in two-way conversations and in proving who a customer is (OTPs, silent authentication). Expect providers to keep adding AI and verification features on top of the message itself.</p>
<h2 id="the-bellwether-twilio-grows-20-but-guides-lower" class="tn-h">The bellwether: Twilio grows 20%, but guides lower<a class="tn-anchor" href="#the-bellwether-twilio-grows-20-but-guides-lower" aria-label="Link to this section">#</a></h2>
<p>Twilio reported its third-quarter 2026 results on 29 October. Revenue was <strong>$1.56 billion, up 20% reported and 16% organic</strong> year on year.</p>
<p>For the fourth quarter it guided to <strong>$1.595–1.605 billion</strong>, which it put at <strong>17–17.5% reported and 11–12% organic</strong> growth. Its CEO framed the opportunity around AI: &quot;Consumer AI has accelerated AI development, and its adoption demands fast, reliable infrastructure built for AI speed.&quot;</p>
<p><strong>What it means for you:</strong> demand for programmable messaging and voice is still growing at double digits globally. The lower organic guide is a reminder that growth is uneven, and that much of the new spend is tied to AI-driven use cases.</p>
<h2 id="india-trai-finalises-its-third-anti-spam-amendment" class="tn-h">India: TRAI finalises its third anti-spam amendment<a class="tn-anchor" href="#india-trai-finalises-its-third-anti-spam-amendment" aria-label="Link to this section">#</a></h2>
<p>On 18 September 2026, TRAI finalised the <strong>Telecom Commercial Communications Customer Preference (Third Amendment) Regulations, 2026</strong>. According to MediaNama&#39;s report of the final text, the main changes for businesses are:</p>
<ul>
<li><strong>Misused headers and templates:</strong> operators must suspend them &quot;immediately… but not beyond six hours&quot; after noticing the misuse, and tell the registered sender within 48 hours. A telemarketer found complicit faces a one-year disconnection and blacklisting.</li>
<li><strong>A lower complaint threshold:</strong> action against a sender drops from five unique complaints in 10 days to <strong>three</strong>, but only when the operator&#39;s AI system also flags the sender&#39;s number in the same period.</li>
<li><strong>Consent collected elsewhere:</strong> explicit consent obtained &quot;through any verifiable means&quot; outside TRAI&#39;s consent framework can count, as long as it is later registered in the Consent Register.</li>
<li><strong>Caller-ID and call-management apps:</strong> they may not tag, block or filter calls from number series TRAI designates for commercial and government calls (such as 140xx and 1600xx). Users&#39; spam reports in those apps must also be routed to the operators&#39; DLT platform.</li>
</ul>
<p>MediaNama also reports the rules come in <strong>in three steps after notification</strong>:</p>
<ul>
<li><strong>After 30 days:</strong> AI-based spam detection and the header and template suspensions.</li>
<li><strong>After 60 days:</strong> a termination charge on A2P calls of up to 5 paise a minute.</li>
<li><strong>After 90 days:</strong> the lower complaint threshold, and suspension for templates registered in the wrong content category.</li>
</ul>
<p><strong>What it means for you:</strong></p>
<ul>
<li><strong>Templates:</strong> keep your DLT templates in the right category, because a wrong category becomes a reason for suspension.</li>
<li><strong>Headers:</strong> treat every header as something that can be switched off within six hours if it is misused.</li>
<li><strong>Consent:</strong> record where and how each customer agreed to hear from you, so it can be registered if asked.</li>
</ul>
<h2 id="rcs-in-india-keeps-climbing" class="tn-h">RCS in India keeps climbing<a class="tn-anchor" href="#rcs-in-india-keeps-climbing" aria-label="Link to this section">#</a></h2>
<p>RCS (Rich Communication Services, the upgrade to SMS with branding, images and buttons) continues to grow fast in India:</p>
<ul>
<li><strong>Doubling usage:</strong> Infobip reported on 18 August 2026 a <strong>108% rise in RCS interactions in India</strong> between H1 2025 and H1 2026. <strong>Finance and fintech</strong> made up &quot;over 3/4 of all interactions&quot;, followed by marketing automation.</li>
<li><strong>Operator tooling:</strong> on 7 October 2026, Infobip launched <strong>RCS BusinessOS</strong>, a layer to help mobile operators launch, govern and charge for RCS business messaging.</li>
<li><strong>The longer view:</strong> Juniper Research forecasts global business RCS traffic to grow from <strong>125 billion messages in 2026 to more than 485 billion by 2030</strong>.</li>
<li><strong>iPhones:</strong> Jio&#39;s commercial RCS Business Messaging now reaches iPhone users too. We covered it in <a href="https://textnation.in/blog/rcs-business-messaging-iphone-india-jio">RCS business messaging reaches iPhone users in India</a>.</li>
</ul>
<p><strong>What it means for you:</strong> for banking alerts, payment reminders and offers, RCS is becoming a realistic main channel, with SMS as the fallback for phones that can&#39;t receive it.</p>
<h2 id="whatsapp-the-end-of-free-service-conversations" class="tn-h">WhatsApp: the end of free service conversations<a class="tn-anchor" href="#whatsapp-the-end-of-free-service-conversations" aria-label="Link to this section">#</a></h2>
<p>Since <strong>1 October 2026</strong>, Meta charges per message for WhatsApp Business Platform <strong>service messages</strong>, free since November 2024. It also charges for <strong>utility messages sent inside an open 24-hour customer service window</strong>, free since July 2025.</p>
<p>We explained what changes and how to plan for it in <a href="https://textnation.in/blog/whatsapp-pricing-changes-october-2026">WhatsApp pricing changes from October 2026</a>.</p>
<p><strong>What it means for you:</strong> a customer-service conversation on WhatsApp now has a per-message cost. Look at which conversations need WhatsApp, and which can move to cheaper channels or self-service.</p>
<h2 id="the-bigger-picture" class="tn-h">The bigger picture<a class="tn-anchor" href="#the-bigger-picture" aria-label="Link to this section">#</a></h2>
<p>Put together, this month&#39;s news points the same way:</p>
<ul>
<li><strong>Conversations and verification:</strong> the industry&#39;s growth is coming from these, not from plain broadcasts.</li>
<li><strong>Regulators:</strong> they are tightening the rules on misuse.</li>
<li><strong>Richer channels:</strong> RCS and WhatsApp are taking a larger share of business messages.</li>
</ul>
<p>For Indian brands, the practical response is the same on every front: clean templates and recorded consent, the right channel for each message, and a fallback when the first channel can&#39;t deliver.</p>
<h2 id="sources" class="tn-h">Sources<a class="tn-anchor" href="#sources" aria-label="Link to this section">#</a></h2>
<ul>
<li>Juniper Research, &quot;CPaaS Market Value to Exceed $50 Billion Globally by 2031&quot;, 2 November 2026 — <a href="https://www.juniperresearch.com/press/cpaas-market-value-to-exceed-50bn-globally-by-2031/" target="_blank" rel="noopener noreferrer">https://www.juniperresearch.com/press/cpaas-market-value-to-exceed-50bn-globally-by-2031/</a></li>
<li>Twilio, &quot;Twilio Announces Third Quarter 2026 Results&quot;, 29 October 2026 — <a href="https://www.twilio.com/en-us/press/releases/twilio-announces-third-quarter-2026-results" target="_blank" rel="noopener noreferrer">https://www.twilio.com/en-us/press/releases/twilio-announces-third-quarter-2026-results</a></li>
<li>MediaNama, &quot;TRAI Restricts Apps Like Truecaller From Blocking 140, 1600 Calls&quot;, 19 September 2026 — <a href="https://www.medianama.com/2026/09/223-trai-truecaller-140-1600-calls-spam-rules/" target="_blank" rel="noopener noreferrer">https://www.medianama.com/2026/09/223-trai-truecaller-140-1600-calls-spam-rules/</a></li>
<li>TRAI, Telecom Commercial Communications Customer Preference (Third Amendment) Regulations, 2026 (18 September 2026) — <a href="https://www.trai.gov.in/sites/default/files/2026-09/Regulation_18092026.pdf" target="_blank" rel="noopener noreferrer">https://www.trai.gov.in/sites/default/files/2026-09/Regulation_18092026.pdf</a></li>
<li>Infobip, &quot;India&#39;s RCS adoption surges 108%&quot;, 18 August 2026 — <a href="https://www.infobip.com/news/indias-rcs-adoption-surges-108-percent" target="_blank" rel="noopener noreferrer">https://www.infobip.com/news/indias-rcs-adoption-surges-108-percent</a></li>
<li>UNI India / Business Wire India, &quot;With RCS adoption in India up 108%, Infobip launches RCS BusinessOS&quot;, 7 October 2026 — <a href="https://www.uniindia.com/business-wire-india/with-rcs-adoption-in-india-up-108-infobip-launches-rcs-businessos-to-help-operators-scale-102112/205813" target="_blank" rel="noopener noreferrer">https://www.uniindia.com/business-wire-india/with-rcs-adoption-in-india-up-108-infobip-launches-rcs-businessos-to-help-operators-scale-102112/205813</a></li>
</ul>
]]></content:encoded>
    </item>
    <item>
      <title>Customer Journey Builder for SMS, WhatsApp and RCS: A Guide</title>
      <link>https://textnation.in/blog/customer-journey-builder-for-sms-whatsapp-and-rcs-a-guide/</link>
      <guid isPermaLink="true">https://textnation.in/blog/customer-journey-builder-for-sms-whatsapp-and-rcs-a-guide/</guid>
      <pubDate>Thu, 29 Oct 2026 13:03:19 GMT</pubDate>
      <dc:creator>TextNation Product Team</dc:creator>
      <category>Guides</category>
      <description>Learn how a customer journey builder works in a CPaaS, with Indian examples, DLT and WhatsApp rules, fallback logic and mistakes to avoid.</description>
      <content:encoded><![CDATA[<p>Most Indian brands already send the right messages. The trouble is timing and sequence: the cart reminder goes out after the customer has bought elsewhere, the EMI nudge arrives the day after the due date, and the welcome series ignores whether the user has even logged in.</p>
<p>A customer journey builder fixes that by turning one-off campaigns into flows that react to what each customer does. This guide explains how journey builders work inside a CPaaS, how to design a journey for Indian channels and rules, and the mistakes that quietly break them.</p>
<h2 id="what-a-customer-journey-builder-actually-does" class="tn-h">What a customer journey builder actually does<a class="tn-anchor" href="#what-a-customer-journey-builder-actually-does" aria-label="Link to this section">#</a></h2>
<p>A journey builder is a visual canvas where you connect blocks into a flow. Each customer who meets the entry condition moves through the flow on their own clock.</p>
<p>Most builders share the same building blocks:</p>
<div class="tn-table"><table>
<thead>
<tr>
<th>Block</th>
<th>What it does</th>
<th>Example</th>
</tr>
</thead>
<tbody><tr>
<td>Trigger</td>
<td>Starts the journey for a customer</td>
<td>Cart abandoned, KYC pending, payment failed</td>
</tr>
<tr>
<td>Message</td>
<td>Sends on a channel</td>
<td>WhatsApp template, RCS card, DLT-approved SMS</td>
</tr>
<tr>
<td>Wait</td>
<td>Pauses before the next step</td>
<td>Wait 2 hours, wait until 10 am</td>
</tr>
<tr>
<td>Condition</td>
<td>Branches on data or behaviour</td>
<td>Did they click? Did they pay?</td>
</tr>
<tr>
<td>Fallback</td>
<td>Switches channel on failure</td>
<td>RCS not delivered, send SMS</td>
</tr>
<tr>
<td>Exit</td>
<td>Removes the customer</td>
<td>Order placed, opted out, journey goal met</td>
</tr>
</tbody></table></div>
<p>The exit block matters as much as the trigger. A journey without a clear exit keeps nudging people who have already converted, which wastes money and invites complaints.</p>
<h2 id="three-journeys-indian-teams-build-first" class="tn-h">Three journeys Indian teams build first<a class="tn-anchor" href="#three-journeys-indian-teams-build-first" aria-label="Link to this section">#</a></h2>
<h3 id="cart-recovery-for-a-d2c-brand" class="tn-h">Cart recovery for a D2C brand<a class="tn-anchor" href="#cart-recovery-for-a-d2c-brand" aria-label="Link to this section">#</a></h3>
<p>Trigger when a logged-in user leaves items in the cart. Wait a short while, then send a WhatsApp marketing template with the product and a &quot;Complete order&quot; button. If the customer does not open it, follow up later with an RCS card or a DLT-approved SMS, then exit as soon as an order is placed.</p>
<h3 id="emi-and-bill-reminders-for-a-lender-or-utility" class="tn-h">EMI and bill reminders for a lender or utility<a class="tn-anchor" href="#emi-and-bill-reminders-for-a-lender-or-utility" aria-label="Link to this section">#</a></h3>
<p>Trigger a few days before the due date. Send a utility reminder, check payment status before each later step, and escalate to a voice call only for customers who are still unpaid close to the deadline. Payment confirmation is the exit.</p>
<h3 id="onboarding-for-an-app-or-fintech" class="tn-h">Onboarding for an app or fintech<a class="tn-anchor" href="#onboarding-for-an-app-or-fintech" aria-label="Link to this section">#</a></h3>
<p>Trigger on sign-up. Branch on whether KYC is complete: those who finished get a &quot;how to use&quot; sequence, those who did not get a reminder with a deep link back to the KYC screen. Exit when KYC is complete or after the last step.</p>
<h2 id="how-to-build-a-journey-step-by-step" class="tn-h">How to build a journey, step by step<a class="tn-anchor" href="#how-to-build-a-journey-step-by-step" aria-label="Link to this section">#</a></h2>
<ol>
<li><strong>Pick one goal and one metric.</strong> &quot;Recover abandoned carts&quot; measured by orders placed from the journey, not &quot;engage users&quot;.</li>
<li><strong>Define the trigger event and the data it carries.</strong> The event from your app or CRM should include the customer&#39;s phone number, consent status, language and the fields your templates need (name, amount, product).</li>
<li><strong>Map each step to a channel and a template category.</strong> Decide in advance which steps are marketing, utility or authentication. Our guide to <a href="https://textnation.in/blog/whatsapp-template-categories-explained/">WhatsApp template categories</a> explains how Meta classifies each one.</li>
<li><strong>Get templates approved before launch.</strong> WhatsApp templates need Meta approval and SMS templates need DLT registration. A journey that waits on approvals in production simply fails at that step.</li>
<li><strong>Set waits in customer time, not system time.</strong> &quot;Wait until 10 am&quot; usually beats &quot;wait 12 hours&quot;, which can land a message at midnight.</li>
<li><strong>Add conditions before every follow-up.</strong> Check whether the customer has already acted. This one check prevents most of the annoying duplicate messages.</li>
<li><strong>Configure fallback per step.</strong> Decide what happens if a rich message is not delivered and how long to wait before falling back.</li>
<li><strong>Test with real numbers across operators.</strong> Run internal numbers on Jio, Airtel, Vi and BSNL, on Android and iPhone, through every branch.</li>
<li><strong>Launch to a slice of your audience first.</strong> Compare against a holdout group so you know the journey caused the result.</li>
</ol>
<h2 id="build-compliance-into-the-journey-not-around-it" class="tn-h">Build compliance into the journey, not around it<a class="tn-anchor" href="#build-compliance-into-the-journey-not-around-it" aria-label="Link to this section">#</a></h2>
<p>Indian messaging rules apply to every automated step, and a journey builder will happily send a non-compliant message thousands of times if you let it.</p>
<p><strong>DLT templates and headers.</strong> TRAI&#39;s TCCCPR 2018 requires businesses sending bulk messages to use a registered content template and an assigned header, as MediaNama reported in its summary of the regulations. Every SMS step&#39;s text, including its variables, must match an approved DLT template. Our <a href="https://textnation.in/blog/trai-dlt-registration-guide-india-2026/">TRAI DLT registration guide</a> walks through the process.</p>
<p><strong>Registered telemarketers.</strong> In a February 2023 press release, TRAI directed access providers to ensure that all promotional messages go through registered telemarketers using approved headers and templates on the DLT platform.</p>
<p><strong>The promotional time window.</strong> Under TCCCPR 2018, promotional SMS and calls are limited to 9 am to 9 pm IST, according to Exotel&#39;s developer documentation on the regulation. Any promotional step that could fire at night needs a &quot;hold until 9 am&quot; rule.</p>
<p><strong>Consent and opt-outs.</strong> Store consent status with the customer record and check it at the trigger. An opt-out on any channel should exit the customer from every marketing journey, not just the one they replied to.</p>
<p><strong>WhatsApp&#39;s 24-hour window.</strong> Meta&#39;s documentation states that a 24-hour customer service window opens when a user messages or calls you, and resets if they do so again before it expires. Inside that window you can send free-form replies; outside it, a journey step must use an approved template.</p>
<h2 id="choosing-channels-and-fallbacks" class="tn-h">Choosing channels and fallbacks<a class="tn-anchor" href="#choosing-channels-and-fallbacks" aria-label="Link to this section">#</a></h2>
<p>Each channel plays a different role in a journey:</p>
<ul>
<li><strong>WhatsApp</strong> suits rich, two-way steps such as order updates, buttons and catalogues. See how it compares in <a href="https://textnation.in/blog/whatsapp-business-api-vs-sms/">WhatsApp Business API vs SMS</a>.</li>
<li><strong>RCS</strong> shows branded cards, carousels and suggested replies in the phone&#39;s default messaging app. Our explainer on <a href="https://textnation.in/blog/rcs-business-messaging-india/">RCS Business Messaging in India</a> covers when it fits.</li>
<li><strong>SMS</strong> reaches almost any phone and works as the fallback layer.</li>
<li><strong>Voice</strong> works for high-stakes, time-bound steps such as a final payment reminder.</li>
</ul>
<p>A sensible default is &quot;rich first, SMS second&quot;: try RCS or WhatsApp, wait for a delivery receipt, and send a DLT-approved SMS only if the first message fails. Make sure the fallback SMS carries the same offer and link, so the customer gets one consistent message rather than two different ones.</p>
<h2 id="mistakes-to-avoid" class="tn-h">Mistakes to avoid<a class="tn-anchor" href="#mistakes-to-avoid" aria-label="Link to this section">#</a></h2>
<ul>
<li><strong>No suppression check.</strong> Sending &quot;Complete your order&quot; after the order is placed.</li>
<li><strong>Too many steps.</strong> Five reminders in two days reads as spam, whatever the channel.</li>
<li><strong>Ignoring language.</strong> Send templates in the language the customer uses in your app, and register those versions too.</li>
<li><strong>Variables that break templates.</strong> A long product name can push an SMS outside its approved DLT template and get it blocked.</li>
<li><strong>Measuring clicks only.</strong> Track the business outcome and the opt-out rate side by side.</li>
<li><strong>Never reviewing live journeys.</strong> Prices, offers and rules change; a journey left running for months often promotes something that no longer exists.</li>
</ul>
<h2 id="a-quick-checklist-before-you-hit-publish" class="tn-h">A quick checklist before you hit publish<a class="tn-anchor" href="#a-quick-checklist-before-you-hit-publish" aria-label="Link to this section">#</a></h2>
<ul>
<li>Goal, metric and exit condition written down</li>
<li>Every message step mapped to an approved template and category</li>
<li>Consent and opt-out checked at entry</li>
<li>Promotional steps held inside 9 am to 9 pm IST</li>
<li>Conditions before every follow-up step</li>
<li>Fallback rules and wait times set per step</li>
<li>Tested on all major operators and both Android and iPhone</li>
<li>Holdout group set up for measurement</li>
</ul>
<h2 id="sources" class="tn-h">Sources<a class="tn-anchor" href="#sources" aria-label="Link to this section">#</a></h2>
<ul>
<li>MediaNama, &quot;TRAI consultation paper reviews 2018 spam regulations&quot; (2024): <a href="https://www.medianama.com/2024/09/223-trai-consultation-paper-review-2018-spamregulations/" target="_blank" rel="noopener noreferrer">https://www.medianama.com/2024/09/223-trai-consultation-paper-review-2018-spamregulations/</a></li>
<li>TRAI, Press Release No. 12/2023 on misuse of headers and message templates under TCCCPR-2018: <a href="https://cms.trai.gov.in/sites/default/files/2024-08/PR_No.12of2023.pdf" target="_blank" rel="noopener noreferrer">https://cms.trai.gov.in/sites/default/files/2024-08/PR_No.12of2023.pdf</a></li>
<li>TRAI, Press Release No. 11/2025, &quot;TRAI Strengthens Consumer Protection with Amendments to TCCCPR, 2018&quot;: <a href="https://cms.trai.gov.in/sites/default/files/2025-02/PR_No.11of2025.pdf" target="_blank" rel="noopener noreferrer">https://cms.trai.gov.in/sites/default/files/2025-02/PR_No.11of2025.pdf</a></li>
<li>Exotel Developer Docs, &quot;TCCCPR 2018&quot;: <a href="https://developer.exotel.com/docs/faqs/tcccpr-2018" target="_blank" rel="noopener noreferrer">https://developer.exotel.com/docs/faqs/tcccpr-2018</a></li>
<li>Meta for Developers, WhatsApp Business Platform, &quot;Send messages&quot; (customer service windows): <a href="https://developers.secure.facebook.com/documentation/business-messaging/whatsapp/messages/send-messages" target="_blank" rel="noopener noreferrer">https://developers.secure.facebook.com/documentation/business-messaging/whatsapp/messages/send-messages</a></li>
</ul>
]]></content:encoded>
    </item>
    <item>
      <title>Is RCS Available in India? Phones, Networks and Reach in 2026</title>
      <link>https://textnation.in/blog/is-rcs-available-in-india/</link>
      <guid isPermaLink="true">https://textnation.in/blog/is-rcs-available-in-india/</guid>
      <pubDate>Tue, 20 Oct 2026 15:34:33 GMT</pubDate>
      <dc:creator>TextNation Product Team</dc:creator>
      <category>Guides</category>
      <description>Is RCS available in India? Where RCS business messages reach today (Android, iPhone on Jio, operators), why some numbers miss it, and how SMS fallback helps.</description>
      <content:encoded><![CDATA[<p><strong>Short answer: yes.</strong> RCS business messages reach Android phones across India through Google Messages, and since September 2026 they have started reaching iPhones on Jio. But &quot;available in India&quot; and &quot;will reach every one of your customers&quot; are not the same thing — and the gap between the two decides how you should send RCS.</p>
<p>This guide explains where RCS works today, why some numbers still can&#39;t receive it, and how to reach everyone anyway.</p>
<h2 id="where-rcs-business-messages-arrive-today" class="tn-h">Where RCS business messages arrive today<a class="tn-anchor" href="#where-rcs-business-messages-arrive-today" aria-label="Link to this section">#</a></h2>
<h3 id="android-phones" class="tn-h">Android phones<a class="tn-anchor" href="#android-phones" aria-label="Link to this section">#</a></h3>
<p>On Android, RCS business messages arrive in <strong>Google Messages</strong>, the default messaging app on most Android phones sold in India. The customer doesn&#39;t install anything: if their phone and network support RCS and RCS chats are on, your message arrives as a rich, branded message — with your logo, a verified badge, images, carousels and buttons — in the same inbox as their OTPs and alerts.</p>
<h3 id="iphones" class="tn-h">iPhones<a class="tn-anchor" href="#iphones" aria-label="Link to this section">#</a></h3>
<p>Apple added RCS to iPhones with <strong>iOS 18</strong>, but whether an iPhone receives RCS depends on the mobile operator. In India, the big change came in September 2026: according to Inc42, <strong>Jio introduced RCS business messaging rates covering iPhone users on its network, effective 1 September 2026</strong>. We covered the details in <a href="https://textnation.in/blog/rcs-business-messaging-iphone-india-jio/">RCS business messaging now reaches iPhones on Jio</a>.</p>
<h3 id="operators" class="tn-h">Operators<a class="tn-anchor" href="#operators" aria-label="Link to this section">#</a></h3>
<p>India&#39;s operators matter because business messages travel through their networks. In March 2026, <strong>Airtel and Google announced that RCS business messages to Airtel users would pass through Airtel&#39;s network-level spam filtering</strong>, with checks on the sender, spam and Do Not Disturb preferences. TechCrunch reported that Airtel had held back deeper RCS integration until this filtering was in place. For brands, this matters because a cleaner channel is a more trusted one — Google had paused business promotions on RCS in India back in 2022 after complaints about spam.</p>
<h2 id="why-some-numbers-still-can-t-receive-rcs" class="tn-h">Why some numbers still can&#39;t receive RCS<a class="tn-anchor" href="#why-some-numbers-still-can-t-receive-rcs" aria-label="Link to this section">#</a></h2>
<p>Even where RCS is available, a particular number may not get the rich version of your message:</p>
<ul>
<li><strong>The phone doesn&#39;t support RCS</strong> — older Android phones, feature phones, and iPhones on networks without RCS business messaging.</li>
<li><strong>RCS chats are switched off</strong> in the customer&#39;s Google Messages settings.</li>
<li><strong>A different default messaging app</strong> is in use on the phone.</li>
<li><strong>No data connection</strong> at the moment you send — RCS travels over mobile data or Wi-Fi, not the SMS channel.</li>
<li><strong>The message can&#39;t be delivered in time</strong> for any other reason.</li>
</ul>
<p>None of these are under your control. That&#39;s why the right question isn&#39;t &quot;is RCS available?&quot; but &quot;what happens to the customers who can&#39;t get it?&quot;</p>
<h2 id="how-to-reach-everyone-rcs-first-sms-fallback" class="tn-h">How to reach everyone: RCS first, SMS fallback<a class="tn-anchor" href="#how-to-reach-everyone-rcs-first-sms-fallback" aria-label="Link to this section">#</a></h2>
<p>Send RCS as the <strong>first attempt</strong> and SMS as the <strong>automatic backup</strong>:</p>
<ol>
<li>Every campaign has an RCS template <strong>and</strong> a DLT-approved SMS template on a registered header.</li>
<li>Customers whose phones can receive RCS get the rich message.</li>
<li>If the RCS message can&#39;t be delivered to a number, the SMS goes out automatically.</li>
<li>Your reports show, for every number, whether it received RCS or SMS.</li>
</ol>
<p>With fallback on, RCS stops being a gamble on reach. Every customer gets the message; the ones who can see more, do.</p>
<h2 id="how-customers-turn-rcs-on" class="tn-h">How customers turn RCS on<a class="tn-anchor" href="#how-customers-turn-rcs-on" aria-label="Link to this section">#</a></h2>
<p>If a customer asks why they don&#39;t see your rich messages, RCS may simply be switched off. In Google Messages on Android:</p>
<ol>
<li>Open <strong>Google Messages</strong> and tap the profile picture (top right).</li>
<li>Tap <strong>Messages settings</strong>, then <strong>RCS chats</strong>.</li>
<li>Turn on <strong>RCS chats</strong> and wait for the status to show <em>Connected</em>.</li>
</ol>
<h2 id="how-to-find-out-your-own-rcs-reach" class="tn-h">How to find out your own RCS reach<a class="tn-anchor" href="#how-to-find-out-your-own-rcs-reach" aria-label="Link to this section">#</a></h2>
<p>Published numbers on RCS-capable devices in India vary widely. The only figure that matters is the share of <strong>your</strong> customers who receive RCS:</p>
<ol>
<li><strong>Start with one high-volume transactional message</strong> you already send — &quot;order shipped&quot; or &quot;appointment confirmed&quot; works well.</li>
<li><strong>Send it as RCS with SMS fallback</strong> for a week or two.</li>
<li><strong>Look at the split</strong> in your reports: how many numbers got RCS, how many got SMS, and how RCS read rates compare.</li>
<li><strong>Decide where RCS earns its place</strong> — usually messages where images and buttons change what customers do.</li>
</ol>
<h2 id="the-bottom-line" class="tn-h">The bottom line<a class="tn-anchor" href="#the-bottom-line" aria-label="Link to this section">#</a></h2>
<p>RCS business messaging is live in India on Android, and growing on iPhone. Because not every phone can receive it, the winning setup is RCS first with automatic SMS fallback — and measuring your own reach rather than relying on market estimates.</p>
<p>To see how RCS compares with the other channels, read <a href="https://textnation.in/blog/rcs-business-messaging-india/">RCS business messaging in India</a>, or explore <a href="https://textnation.in/services/rcs-messaging/">RCS messaging on TextNation</a>.</p>
<h2 id="sources" class="tn-h">Sources<a class="tn-anchor" href="#sources" aria-label="Link to this section">#</a></h2>
<ul>
<li>Inc42 — <a href="https://inc42.com/buzz/jio-introduces-new-rcs-business-messaging-rates-for-iphone-users-in-india/" target="_blank" rel="noopener noreferrer">Jio introduces new RCS business messaging rates for iPhone users in India</a> (9 September 2026)</li>
<li>TechCrunch — <a href="https://techcrunch.com/2026/03/01/google-looks-to-tackle-longstanding-rcs-spam-in-india-but-not-alone/" target="_blank" rel="noopener noreferrer">Google looks to tackle longstanding RCS spam in India — but not alone</a> (1 March 2026)</li>
<li>MediaNama — <a href="https://www.medianama.com/2026/03/223-airtel-spam-detection-googles-rcs-messaging-india/" target="_blank" rel="noopener noreferrer">Airtel integrates spam filter with Google RCS messaging in India</a> (March 2026)</li>
</ul>
]]></content:encoded>
    </item>
    <item>
      <title>RCS Pricing in India: How RCS Business Messaging Is Charged</title>
      <link>https://textnation.in/blog/rcs-pricing-india-how-rcs-is-charged/</link>
      <guid isPermaLink="true">https://textnation.in/blog/rcs-pricing-india-how-rcs-is-charged/</guid>
      <pubDate>Tue, 20 Oct 2026 15:34:33 GMT</pubDate>
      <dc:creator>TextNation Product Team</dc:creator>
      <category>Guides</category>
      <description>How RCS business messaging is charged in India: basic vs rich messages, conversations, SMS fallback, reported rates, and how to keep RCS costs predictable.</description>
      <content:encoded><![CDATA[<p>&quot;How much does RCS cost?&quot; is one of the most common questions brands ask before trying RCS business messaging. The honest answer is that <strong>it depends on what kind of message you send</strong> — a short text, a rich card, or a conversation are charged differently. Once you understand how RCS is billed, you can plan a mix that keeps costs predictable.</p>
<p>This guide explains the billing model behind RCS business messaging, what drives your bill in India, and the questions to ask any provider before you sign up.</p>
<h2 id="the-building-block-what-google-counts" class="tn-h">The building block: what Google counts<a class="tn-anchor" href="#the-building-block-what-google-counts" aria-label="Link to this section">#</a></h2>
<p>RCS business messaging runs on Google&#39;s RCS Business Messaging (RBM) platform. Google tracks every message as a <strong>billable event</strong>, and operators and providers price on top of those events. The main ones, according to Google&#39;s RBM billing documentation:</p>
<div class="tn-table"><table>
<thead>
<tr>
<th>Billable event</th>
<th>What it is</th>
</tr>
</thead>
<tbody><tr>
<td><strong>Basic message</strong></td>
<td>A message from your business that is <strong>text only, up to 160 characters</strong></td>
</tr>
<tr>
<td><strong>Single (rich) message</strong></td>
<td>A message with <strong>rich content</strong> — image, video, rich card, carousel — or <strong>text longer than 160 characters</strong></td>
</tr>
<tr>
<td><strong>Conversation</strong></td>
<td>For conversational agents: messages exchanged within a <strong>24-hour window</strong> that starts when one side replies to the other</td>
</tr>
<tr>
<td><strong>Customer message</strong></td>
<td>A message the customer sends to your business — operators decide whether and how these are charged</td>
</tr>
</tbody></table></div>
<p>Two details are easy to miss:</p>
<ul>
<li><strong>Length changes the category.</strong> A text-only message of 161 characters is no longer a basic message — it is billed like a rich one.</li>
<li><strong>Taps are treated differently.</strong> Google&#39;s documentation says tapping a <em>suggested action</em> (for example &quot;Open link&quot; or &quot;Call&quot;) doesn&#39;t create a billable event, while tapping a <em>suggested reply</em> sends a message back to the business, which does.</li>
</ul>
<h2 id="conversational-vs-non-conversational-agents" class="tn-h">Conversational vs non-conversational agents<a class="tn-anchor" href="#conversational-vs-non-conversational-agents" aria-label="Link to this section">#</a></h2>
<p>Every RCS sender (the &quot;agent&quot;) is set up in one of two billing categories, chosen when the agent is created:</p>
<ul>
<li><strong>Non-conversational</strong> — charged <strong>per message</strong>. This is the typical setup for alerts, notifications and promotions. Google merged the older <em>Basic Message</em> and <em>Single Message</em> categories into this one on <strong>20 November 2025</strong>, without changing which events are billed.</li>
<li><strong>Conversational</strong> — charged <strong>per conversation</strong> when the customer replies within 24 hours; a message the customer never replies to is still charged on its own.</li>
</ul>
<p>Pick conversational only if customers will genuinely talk back — support, bookings, guided selling. For one-way traffic, per-message billing is simpler to predict.</p>
<h2 id="what-rcs-costs-in-india" class="tn-h">What RCS costs in India<a class="tn-anchor" href="#what-rcs-costs-in-india" aria-label="Link to this section">#</a></h2>
<p>Prices are set commercially by operators and providers, so there is no single public price list. What has been published gives a sense of the range. In September 2026, Inc42 reported Jio&#39;s new RCS business messaging rates — <strong>₹0.27–0.30 per marketing message, ₹0.25 per transactional message and ₹0.11–0.16 per OTP</strong> — replacing an earlier flat ₹0.08–0.10 per message. We covered that change in <a href="https://textnation.in/blog/rcs-business-messaging-iphone-india-jio/">RCS business messaging now reaches iPhones on Jio</a>.</p>
<h2 id="what-really-drives-your-rcs-bill" class="tn-h">What really drives your RCS bill<a class="tn-anchor" href="#what-really-drives-your-rcs-bill" aria-label="Link to this section">#</a></h2>
<ol>
<li><strong>Your message mix.</strong> Marketing, transactional and OTP traffic are often priced differently, and so are basic and rich messages.</li>
<li><strong>Text length.</strong> Short, text-only alerts under 160 characters fall into the cheapest category. Every extra character over 160 moves the message up.</li>
<li><strong>How much goes out as SMS fallback.</strong> Numbers that can&#39;t receive RCS get your SMS instead — and that SMS is charged as SMS. The higher your RCS reach, the more of your traffic is billed as RCS.</li>
<li><strong>Replies.</strong> With a conversational agent, replies turn messages into conversations; with a non-conversational one, operators may charge for customer messages.</li>
<li><strong>Failed messages.</strong> Whether undelivered messages are charged depends on your provider&#39;s terms — ask.</li>
</ol>
<h2 id="how-to-keep-rcs-costs-under-control" class="tn-h">How to keep RCS costs under control<a class="tn-anchor" href="#how-to-keep-rcs-costs-under-control" aria-label="Link to this section">#</a></h2>
<ul>
<li><strong>Use rich messages where they change behaviour</strong> — product carousels, offers with a &quot;Buy now&quot; button, order updates with &quot;Track&quot; and &quot;Reschedule&quot;.</li>
<li><strong>Keep plain alerts plain.</strong> A one-line alert doesn&#39;t need an image; keep it under 160 characters, or keep it on SMS.</li>
<li><strong>Always turn on SMS fallback.</strong> It protects reach — and your reports show exactly how much went out as SMS.</li>
<li><strong>Pilot before you scale.</strong> Run one high-volume message on RCS for a couple of weeks and compare cost per click or per conversion with SMS.</li>
<li><strong>Review the split every month.</strong> As RCS reach grows (iPhones on Jio, for example), the share of traffic billed as RCS will change.</li>
</ul>
<h2 id="questions-to-ask-an-rcs-provider-about-pricing" class="tn-h">Questions to ask an RCS provider about pricing<a class="tn-anchor" href="#questions-to-ask-an-rcs-provider-about-pricing" aria-label="Link to this section">#</a></h2>
<ul>
<li>What is the price per <strong>basic</strong> message and per <strong>rich</strong> message — and for marketing, transactional and OTP traffic?</li>
<li>Is my agent <strong>conversational or non-conversational</strong>, and why?</li>
<li>How is <strong>SMS fallback</strong> charged, and does it use my existing DLT header and templates?</li>
<li>Are <strong>undelivered</strong> messages charged?</li>
<li>Are <strong>customer replies</strong> charged?</li>
<li>Can I see, per number, whether a message went out as <strong>RCS or SMS</strong>?</li>
</ul>
<h2 id="the-bottom-line" class="tn-h">The bottom line<a class="tn-anchor" href="#the-bottom-line" aria-label="Link to this section">#</a></h2>
<p>RCS is charged per billable event, and the type of message — basic, rich or conversation — sets the price. Keep simple alerts short, use rich messages where they earn their cost, and always send with SMS fallback. Then measure cost per result, not cost per message.</p>
<h2 id="sources" class="tn-h">Sources<a class="tn-anchor" href="#sources" aria-label="Link to this section">#</a></h2>
<ul>
<li>Google for Developers — <a href="https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rbm-billing-faq" target="_blank" rel="noopener noreferrer">RBM billing FAQ</a></li>
<li>Inc42 — <a href="https://inc42.com/buzz/jio-introduces-new-rcs-business-messaging-rates-for-iphone-users-in-india/" target="_blank" rel="noopener noreferrer">Jio introduces new RCS business messaging rates for iPhone users in India</a> (9 September 2026)</li>
</ul>
]]></content:encoded>
    </item>
    <item>
      <title>How to Choose an RCS Provider in India: 10 Questions to Ask</title>
      <link>https://textnation.in/blog/choose-rcs-provider-india/</link>
      <guid isPermaLink="true">https://textnation.in/blog/choose-rcs-provider-india/</guid>
      <pubDate>Tue, 20 Oct 2026 15:34:33 GMT</pubDate>
      <dc:creator>TextNation Product Team</dc:creator>
      <category>Strategy</category>
      <description>Choosing an RCS service provider in India? Ten questions to ask about agent approval, SMS fallback, reporting, pricing, API, integrations and compliance.</description>
      <content:encoded><![CDATA[<p>Choosing an RCS provider in India is less about who can send a rich message — most can — and more about what happens around it: getting your brand approved, reaching customers who can&#39;t receive RCS, seeing what actually happened to every message, and fitting RCS into the tools you already use.</p>
<p>Here are ten questions to ask any RCS business messaging provider before you commit, and what a good answer sounds like.</p>
<h2 id="1-will-you-help-us-register-and-verify-our-rcs-agent" class="tn-h">1. Will you help us register and verify our RCS agent?<a class="tn-anchor" href="#1-will-you-help-us-register-and-verify-our-rcs-agent" aria-label="Link to this section">#</a></h2>
<p>Your RCS sender — the <strong>agent</strong> — carries your brand name, logo, colours, description and contact details, and has to be verified and approved before it can message customers. A good provider walks you through the information needed, prepares the submission with you and tells you where it stands.</p>
<p><strong>Good answer:</strong> &quot;We&#39;ll collect what&#39;s needed, submit it, and keep you updated until it&#39;s approved.&quot;</p>
<h2 id="2-which-message-types-can-we-send" class="tn-h">2. Which message types can we send?<a class="tn-anchor" href="#2-which-message-types-can-we-send" aria-label="Link to this section">#</a></h2>
<p>At minimum you should be able to send <strong>plain text, rich cards</strong> (image or video with title, description and buttons) and <strong>carousels</strong> of several cards. Buttons should cover opening a link, starting a call, sharing a location and quick replies.</p>
<p><strong>Ask to see:</strong> a preview of each type exactly as customers will see it.</p>
<h2 id="3-what-happens-when-a-phone-can-t-receive-rcs" class="tn-h">3. What happens when a phone can&#39;t receive RCS?<a class="tn-anchor" href="#3-what-happens-when-a-phone-can-t-receive-rcs" aria-label="Link to this section">#</a></h2>
<p>This is the most important question. Not every phone can receive RCS — older phones, some iPhones, RCS switched off, no data. Without a backup, those customers get nothing. Read <a href="https://textnation.in/blog/is-rcs-available-in-india/">Is RCS available in India?</a> for why.</p>
<p><strong>Good answer:</strong> &quot;Automatic SMS fallback on your DLT-registered header and approved template — set once per campaign.&quot;</p>
<h2 id="4-can-we-see-what-happened-to-every-number" class="tn-h">4. Can we see what happened to every number?<a class="tn-anchor" href="#4-can-we-see-what-happened-to-every-number" aria-label="Link to this section">#</a></h2>
<p>Totals aren&#39;t enough. You need to know, <strong>per number</strong>, whether the message was delivered or read, whether it went out as RCS or SMS, and why it failed if it did. You should also be able to export it for your team.</p>
<p><strong>Ask to see:</strong> the sent-message list and the usage report for a real campaign.</p>
<h2 id="5-how-is-rcs-charged-and-how-is-fallback-charged" class="tn-h">5. How is RCS charged — and how is fallback charged?<a class="tn-anchor" href="#5-how-is-rcs-charged-and-how-is-fallback-charged" aria-label="Link to this section">#</a></h2>
<p>RCS is billed per event: basic messages, rich messages and conversations are priced differently, and SMS fallback is charged as SMS. Make sure the provider explains each line. Our guide to <a href="https://textnation.in/blog/rcs-pricing-india-how-rcs-is-charged/">how RCS is charged in India</a> lists the questions to ask.</p>
<h2 id="6-can-our-systems-send-rcs-through-an-api" class="tn-h">6. Can our systems send RCS through an API?<a class="tn-anchor" href="#6-can-our-systems-send-rcs-through-an-api" aria-label="Link to this section">#</a></h2>
<p>Most brands trigger messages from their own systems — order platforms, CRMs, core banking. You need an <strong>HTTP API</strong> for sending and <strong>delivery reports pushed back to your URL</strong> (webhooks), with your own authentication.</p>
<h2 id="7-does-it-work-with-our-marketing-tools" class="tn-h">7. Does it work with our marketing tools?<a class="tn-anchor" href="#7-does-it-work-with-our-marketing-tools" aria-label="Link to this section">#</a></h2>
<p>If your team runs campaigns from a marketing automation or CRM platform, ask whether the provider can be plugged in as the RCS (and SMS and WhatsApp) provider there, and whether delivery reports flow back into it. See our <a href="https://textnation.in/integrations/">integrations</a> for an example of what to look for.</p>
<h2 id="8-what-about-sms-and-whatsapp" class="tn-h">8. What about SMS and WhatsApp?<a class="tn-anchor" href="#8-what-about-sms-and-whatsapp" aria-label="Link to this section">#</a></h2>
<p>RCS works best next to the other channels: RCS with SMS fallback for alerts and offers, WhatsApp for conversations, SMS for OTPs on every phone. One provider for all of them means <strong>one account, one set of reports, one opt-out list</strong>, and journeys that move between channels — for example, an SMS reminder the next day if an RCS message wasn&#39;t read.</p>
<h2 id="9-how-do-you-handle-opt-outs-and-compliance" class="tn-h">9. How do you handle opt-outs and compliance?<a class="tn-anchor" href="#9-how-do-you-handle-opt-outs-and-compliance" aria-label="Link to this section">#</a></h2>
<p>Customers who opt out must stop receiving messages — on every channel, not just the one they opted out of. Fallback SMS still needs <strong>DLT-registered headers and templates</strong>. Ask how opt-outs are applied and whether they cover API and integration traffic too.</p>
<h2 id="10-what-happens-when-we-send-a-lot-at-once" class="tn-h">10. What happens when we send a lot at once?<a class="tn-anchor" href="#10-what-happens-when-we-send-a-lot-at-once" aria-label="Link to this section">#</a></h2>
<p>Big campaigns shouldn&#39;t hold up your OTPs and alerts. Ask how the provider queues large sends, whether time-critical traffic gets priority, and how quickly you can pause or stop a campaign.</p>
<h2 id="a-quick-checklist" class="tn-h">A quick checklist<a class="tn-anchor" href="#a-quick-checklist" aria-label="Link to this section">#</a></h2>
<div class="tn-table"><table>
<thead>
<tr>
<th>Question</th>
<th>What to look for</th>
</tr>
</thead>
<tbody><tr>
<td>Agent registration</td>
<td>Hands-on help until approval</td>
</tr>
<tr>
<td>Message types</td>
<td>Text, rich cards, carousels, buttons, quick replies</td>
</tr>
<tr>
<td>Reach</td>
<td>Automatic SMS fallback on your DLT header and template</td>
</tr>
<tr>
<td>Reporting</td>
<td>Per number: delivered, read, RCS or SMS, failure reason; exports</td>
</tr>
<tr>
<td>Pricing</td>
<td>Clear rates by message type; fallback charged as SMS</td>
</tr>
<tr>
<td>API</td>
<td>Sending API plus delivery webhooks</td>
</tr>
<tr>
<td>Integrations</td>
<td>Works with your marketing and CRM tools</td>
</tr>
<tr>
<td>Other channels</td>
<td>SMS and WhatsApp on the same account</td>
</tr>
<tr>
<td>Compliance</td>
<td>Opt-outs on every channel and every send path</td>
</tr>
<tr>
<td>Scale</td>
<td>Priority for time-critical traffic; pause and stop controls</td>
</tr>
</tbody></table></div>
<h2 id="the-bottom-line" class="tn-h">The bottom line<a class="tn-anchor" href="#the-bottom-line" aria-label="Link to this section">#</a></h2>
<p>The best RCS provider is the one that gets your brand approved, never leaves a customer without the message, and shows you exactly what happened to every number — on the same platform as your SMS and WhatsApp.</p>
]]></content:encoded>
    </item>
    <item>
      <title>RCS Business Messaging Now Reaches iPhones on Jio: What Changes for Brands</title>
      <link>https://textnation.in/blog/rcs-business-messaging-iphone-india-jio/</link>
      <guid isPermaLink="true">https://textnation.in/blog/rcs-business-messaging-iphone-india-jio/</guid>
      <pubDate>Tue, 20 Oct 2026 13:16:39 GMT</pubDate>
      <dc:creator>TextNation Product Team</dc:creator>
      <category>Industry news</category>
      <description>Jio now lets brands send RCS business messages to iPhone users (from 1 Sep 2026). Reported rates, what changes for brands, and why SMS fallback still matters.</description>
      <content:encoded><![CDATA[<p>For years, RCS business messaging in India had one big gap: <strong>iPhone users</strong>. Brands could send rich, branded messages to Android phones, but iPhones fell back to plain SMS. That is starting to change.</p>
<p>According to a report by Inc42 (9 September 2026), Reliance Jio has rolled out new RCS business messaging rates that let brands send marketing, transactional and OTP messages to <strong>iPhone users on Jio&#39;s network</strong>, effective <strong>1 September 2026</strong>. Here is what changed and what it means for your messaging plans.</p>
<h2 id="what-jio-announced" class="tn-h">What Jio announced<a class="tn-anchor" href="#what-jio-announced" aria-label="Link to this section">#</a></h2>
<p>Based on emails Jio sent to businesses, as reported by Inc42:</p>
<div class="tn-table"><table>
<thead>
<tr>
<th>Message type</th>
<th>New rate per message (as reported)</th>
</tr>
</thead>
<tbody><tr>
<td>Marketing</td>
<td>₹0.27–0.30</td>
</tr>
<tr>
<td>Transactional</td>
<td>₹0.25</td>
</tr>
<tr>
<td>OTP</td>
<td>₹0.11–0.16</td>
</tr>
</tbody></table></div>
<p>Previously, Jio charged a <strong>flat ₹0.08–0.10 per message</strong> for RCS business messaging. The report describes this as an expansion of Jio&#39;s existing RCS service, which already reached Android users — not a separate new product. Apple has supported RCS on iPhones since iOS 18, with availability depending on the operator; prices are set by each operator.</p>
<h2 id="why-this-matters" class="tn-h">Why this matters<a class="tn-anchor" href="#why-this-matters" aria-label="Link to this section">#</a></h2>
<p>RCS messages arrive in the phone&#39;s default messaging app with your <strong>brand name, logo and a verification badge</strong>, plus images, carousels and buttons. Until now, a large part of India&#39;s high-value audience — iPhone users — could not see that experience. With iPhones on Jio now reachable:</p>
<ul>
<li><strong>Campaign reach for rich messages grows</strong>, especially for brands whose customers skew premium.</li>
<li><strong>Verified sender identity reaches more people</strong> — useful for banks, insurers and delivery brands whose names are often spoofed.</li>
<li><strong>A single rich message can serve both platforms</strong> on Jio, instead of an Android-only RCS version and an SMS version for everyone else.</li>
</ul>
<h2 id="what-it-means-for-cost" class="tn-h">What it means for cost<a class="tn-anchor" href="#what-it-means-for-cost" aria-label="Link to this section">#</a></h2>
<p>RCS on Jio is no longer a flat, low price. At the reported rates, a marketing RCS message costs noticeably more than before, while OTPs remain at the lower end. That changes the maths:</p>
<ul>
<li><strong>Use RCS where richness pays off</strong> — product carousels, offers with buttons, order updates with &quot;Track&quot; and &quot;Reschedule&quot; actions.</li>
<li><strong>Keep simple alerts simple.</strong> A plain text alert may not need RCS at all.</li>
<li><strong>Compare against WhatsApp and SMS per use case</strong>, not per channel. Our guide to <a href="https://textnation.in/blog/whatsapp-business-api-vs-sms/">WhatsApp Business API vs SMS</a> and the latest <a href="https://textnation.in/blog/whatsapp-pricing-changes-october-2026/">WhatsApp pricing changes</a> help with that comparison.</li>
</ul>
<h2 id="fallback-still-matters" class="tn-h">Fallback still matters<a class="tn-anchor" href="#fallback-still-matters" aria-label="Link to this section">#</a></h2>
<p>Even with iPhones on Jio, not every recipient can receive RCS — other networks, older phones, and devices with RCS switched off. That is why RCS should always be sent with <strong>automatic SMS fallback</strong>: the platform sends the rich message where it works, and the same content as SMS on your DLT-registered header everywhere else. We explain the setup in <a href="https://textnation.in/blog/rcs-business-messaging-india/">RCS business messaging in India</a>.</p>
<h2 id="what-to-do-now" class="tn-h">What to do now<a class="tn-anchor" href="#what-to-do-now" aria-label="Link to this section">#</a></h2>
<ol>
<li><strong>Check your audience mix</strong> — how many customers are on Jio, and how many use iPhones.</li>
<li><strong>Re-price your RCS plan</strong> with the new rates for marketing, transactional and OTP traffic.</li>
<li><strong>Pick the use cases where rich messages earn their cost</strong>, and keep plain alerts on SMS.</li>
<li><strong>Make sure SMS fallback is on</strong> for every RCS message.</li>
</ol>
<h2 id="sources" class="tn-h">Sources<a class="tn-anchor" href="#sources" aria-label="Link to this section">#</a></h2>
<ul>
<li>Inc42 — <a href="https://inc42.com/buzz/jio-introduces-new-rcs-business-messaging-rates-for-iphone-users-in-india/" target="_blank" rel="noopener noreferrer">Jio introduces new RCS business messaging rates for iPhone users in India</a> (9 September 2026)</li>
</ul>
]]></content:encoded>
    </item>
    <item>
      <title>Airtel Enters CPaaS With IQ Gateway and Silent Authentication: What It Means for OTPs</title>
      <link>https://textnation.in/blog/airtel-iq-gateway-silent-authentication/</link>
      <guid isPermaLink="true">https://textnation.in/blog/airtel-iq-gateway-silent-authentication/</guid>
      <pubDate>Tue, 20 Oct 2026 13:16:39 GMT</pubDate>
      <dc:creator>TextNation Product Team</dc:creator>
      <category>Industry news</category>
      <description>Airtel IQ Gateway brings SMS, WhatsApp, RCS, voice and silent authentication. What was announced and how to combine silent verification with OTP fallback.</description>
      <content:encoded><![CDATA[<p>India&#39;s telecom operators are no longer content to carry business messages — they want to sell the platform too. In October 2026, <strong>Airtel Business launched IQ Gateway nationwide</strong>, a platform that brings SMS, WhatsApp, RCS and voice together and adds <strong>&quot;Silent Authentication&quot;</strong> — a way to verify a user&#39;s phone number without sending an OTP.</p>
<p>Here is what was announced, what it could mean for how businesses verify users, and how to think about it if you run OTP flows today.</p>
<h2 id="what-airtel-announced" class="tn-h">What Airtel announced<a class="tn-anchor" href="#what-airtel-announced" aria-label="Link to this section">#</a></h2>
<p>According to a MediaNama report (7 October 2026), Airtel IQ Gateway:</p>
<ul>
<li><strong>Combines SMS, WhatsApp, RCS and voice</strong> in one platform for enterprises.</li>
<li>Adds <strong>Silent Authentication</strong>, which Airtel says can replace OTP SMS for login and SIM-binding flows by validating that the entered number matches the active SIM in the device.</li>
<li>Includes an <strong>&quot;IQ Verify&quot;</strong> system that uses network, device and usage signals, plus protections against <strong>bot-driven SMS pumping</strong> that inflates OTP bills.</li>
<li>Can be integrated with existing systems, installed <strong>on-premises</strong>, or used as <strong>SaaS</strong> on Airtel&#39;s cloud.</li>
<li>Was launched after trials with select banks and financial institutions; Airtel did not share trial results, and the report gave no pricing.</li>
</ul>
<p>MediaNama notes this puts Airtel in direct competition with CPaaS companies such as Twilio, Tanla, Route Mobile, Routee and Netcore Cloud — as well as with telecom offerings like Jio&#39;s JioCX and Vi Business.</p>
<h2 id="what-is-silent-authentication" class="tn-h">What is &quot;silent authentication&quot;?<a class="tn-anchor" href="#what-is-silent-authentication" aria-label="Link to this section">#</a></h2>
<p>A traditional OTP flow sends a code by SMS, and the user types it in. Silent authentication checks — through the mobile network — that the phone number the user entered belongs to the SIM in the device making the request. If it matches, the user is verified <strong>without a code</strong>.</p>
<p>Potential benefits:</p>
<ul>
<li><strong>Faster sign-in</strong> — no waiting for an SMS, no typing.</li>
<li><strong>Fewer OTP costs</strong> for the verifications that succeed silently.</li>
<li><strong>Less exposure to OTP fraud</strong> such as SMS pumping and some SIM-swap and social-engineering attacks.</li>
</ul>
<h2 id="what-it-means-for-your-otp-flows" class="tn-h">What it means for your OTP flows<a class="tn-anchor" href="#what-it-means-for-your-otp-flows" aria-label="Link to this section">#</a></h2>
<p>Don&#39;t rip out OTPs. Think of silent authentication as a <strong>first attempt</strong>, with proven channels behind it:</p>
<ol>
<li><strong>Try silent verification</strong> where it is supported.</li>
<li><strong>Fall back to OTP</strong> — by SMS, or WhatsApp authentication templates — when it isn&#39;t.</li>
<li><strong>Protect the OTP endpoint either way</strong> — rate limits per number and IP, and watching the share of OTPs that are never verified.</li>
</ol>
<p>Our guide to <a href="https://textnation.in/blog/otp-sms-delivery-fixes/">why OTP SMS doesn&#39;t arrive and how to fix it</a> covers the fallback and abuse-protection side in detail.</p>
<h2 id="operators-vs-platforms-what-to-look-for" class="tn-h">Operators vs platforms: what to look for<a class="tn-anchor" href="#operators-vs-platforms-what-to-look-for" aria-label="Link to this section">#</a></h2>
<p>With operators building their own platforms, the choice for businesses is less about &quot;who carries the message&quot; and more about <strong>reach, reliability and control</strong>:</p>
<ul>
<li><strong>Multi-operator reach.</strong> Your customers are on Jio, Airtel, Vi and BSNL. A single-operator product may not cover them all equally.</li>
<li><strong>Channel choice per message.</strong> The cheapest working channel for an alert is not the same as for a campaign.</li>
<li><strong>One view of delivery and cost</strong> across SMS, WhatsApp, RCS and voice.</li>
<li><strong>Compliance built in</strong> — DLT templates, headers, consent and opt-outs.</li>
</ul>
<h2 id="sources" class="tn-h">Sources<a class="tn-anchor" href="#sources" aria-label="Link to this section">#</a></h2>
<ul>
<li>MediaNama — <a href="https://www.medianama.com/2026/10/223-airtel-iq-gateway-messaging-network/" target="_blank" rel="noopener noreferrer">Airtel IQ Gateway unifies SMS, WhatsApp, RCS and voice</a> (7 October 2026)</li>
</ul>
]]></content:encoded>
    </item>
    <item>
      <title>WhatsApp Pricing Changed on 1 October 2026: What Indian Businesses Must Know</title>
      <link>https://textnation.in/blog/whatsapp-pricing-changes-october-2026/</link>
      <guid isPermaLink="true">https://textnation.in/blog/whatsapp-pricing-changes-october-2026/</guid>
      <pubDate>Tue, 20 Oct 2026 13:16:38 GMT</pubDate>
      <dc:creator>TextNation Product Team</dc:creator>
      <category>Industry news</category>
      <description>WhatsApp pricing changed on 1 Oct 2026: 1,000 free service messages per number, in-window utility now charged, and INR billing by 31 Dec 2026.</description>
      <content:encoded><![CDATA[<p>If your business sends WhatsApp messages in India, your bill changed on <strong>1 October 2026</strong>. Two kinds of messages that Meta had made free are now charged, and a billing-currency deadline is coming up at the end of the year.</p>
<p>Here is what changed, what it means in practice, and what to do this quarter. Everything below comes from Meta&#39;s own pricing documentation — rates themselves change, so always check the current rate card before you budget.</p>
<h2 id="what-changed-on-1-october-2026" class="tn-h">What changed on 1 October 2026<a class="tn-anchor" href="#what-changed-on-1-october-2026" aria-label="Link to this section">#</a></h2>
<p>Meta charges for WhatsApp per message, by category: <strong>marketing</strong>, <strong>utility</strong>, <strong>authentication</strong> and <strong>service</strong> (replies to a customer who messaged you first). From 1 October 2026, according to Meta&#39;s pricing updates:</p>
<ol>
<li><strong>Service messages are no longer free without limit.</strong> They had been free since 1 November 2024. Now each business phone number gets <strong>1,000 free service messages per month</strong>, and messages beyond that are charged. The free allowance does not roll over.</li>
<li><strong>Utility messages inside an open customer-service window are charged.</strong> Since 1 July 2025, a utility template sent within 24 hours of the customer&#39;s last message was free. That exception has ended.</li>
</ol>
<p>For India, Meta&#39;s October update did not list a change to the marketing, utility or authentication rates themselves — the change is in <strong>which messages are free</strong>.</p>
<h2 id="the-other-2026-changes-indian-businesses-should-know" class="tn-h">The other 2026 changes Indian businesses should know<a class="tn-anchor" href="#the-other-2026-changes-indian-businesses-should-know" aria-label="Link to this section">#</a></h2>
<div class="tn-table"><table>
<thead>
<tr>
<th>Date</th>
<th>Change (per Meta)</th>
</tr>
</thead>
<tbody><tr>
<td>1 January 2026</td>
<td>India marketing rates went up; billing in Indian rupees (INR) launched for eligible accounts</td>
</tr>
<tr>
<td>1 April 2026</td>
<td>India&#39;s authentication-international rate went up</td>
</tr>
<tr>
<td>1 October 2026</td>
<td>Service messages beyond 1,000 per number per month and in-window utility messages are charged</td>
</tr>
<tr>
<td>31 December 2026</td>
<td>Deadline for eligible India accounts to move billing to INR</td>
</tr>
</tbody></table></div>
<p>The last one matters operationally: Meta says that from <strong>1 January 2027</strong> it will stop delivering messages from non-INR accounts of eligible customers that haven&#39;t migrated. If you are billed directly by Meta, check your account&#39;s currency now. If you send through a provider, ask them to confirm the migration is done.</p>
<h2 id="what-this-means-for-your-whatsapp-costs" class="tn-h">What this means for your WhatsApp costs<a class="tn-anchor" href="#what-this-means-for-your-whatsapp-costs" aria-label="Link to this section">#</a></h2>
<p>Most Indian businesses use WhatsApp in three ways, and each is affected differently:</p>
<ul>
<li><strong>Customer support</strong> (service messages): small and mid-sized teams may stay within 1,000 free messages per number per month. Busy support desks will not — every message after the 1,000th is now billed.</li>
<li><strong>Order, delivery and account updates</strong> (utility): these were sometimes free when sent inside an open chat window. Now every utility template is charged.</li>
<li><strong>Campaigns</strong> (marketing): no change in October, but marketing remains the most expensive category, and the January increase still applies.</li>
</ul>
<h2 id="five-things-to-do-this-quarter" class="tn-h">Five things to do this quarter<a class="tn-anchor" href="#five-things-to-do-this-quarter" aria-label="Link to this section">#</a></h2>
<ol>
<li><strong>Measure your service volume per number.</strong> Find out how many service messages each WhatsApp number sends in a month. If you are near or above 1,000, the new charges apply to you.</li>
<li><strong>Check your template categories.</strong> A utility template with one promotional line can be reclassified as marketing — the most expensive category. Our guide to <a href="https://textnation.in/blog/whatsapp-template-categories-explained/">WhatsApp template categories</a> explains how to keep categories right.</li>
<li><strong>Move routine replies to the right channel.</strong> Not every update needs WhatsApp. A delivery OTP or a simple alert can often go by SMS, while WhatsApp is kept for rich, two-way conversations. See <a href="https://textnation.in/blog/whatsapp-business-api-vs-sms/">WhatsApp Business API vs SMS</a>.</li>
<li><strong>Confirm INR billing before 31 December.</strong> Ask your provider, or check your Meta account if you are billed directly.</li>
<li><strong>Watch cost per conversation, not just per message.</strong> A conversation that needs eight messages instead of three now costs more. Shorter, clearer templates and quick-reply buttons help.</li>
</ol>
<h2 id="sources" class="tn-h">Sources<a class="tn-anchor" href="#sources" aria-label="Link to this section">#</a></h2>
<ul>
<li>Meta for Developers — <a href="https://developers.facebook.com/docs/whatsapp/pricing/updates-to-pricing/" target="_blank" rel="noopener noreferrer">WhatsApp Business Platform pricing updates</a></li>
</ul>
]]></content:encoded>
    </item>
    <item>
      <title>OTP SMS Not Arriving? 9 Fixes for Faster One-Time Passwords in India</title>
      <link>https://textnation.in/blog/otp-sms-delivery-fixes/</link>
      <guid isPermaLink="true">https://textnation.in/blog/otp-sms-delivery-fixes/</guid>
      <pubDate>Sun, 18 Oct 2026 06:17:37 GMT</pubDate>
      <dc:creator>TextNation Product Team</dc:creator>
      <category>Guides</category>
      <description>Why OTP SMS is slow or never arrives in India, and 9 practical fixes: DLT templates, routes, number formats, priority queues, fallback and abuse limits.</description>
      <content:encoded><![CDATA[<p>An OTP that arrives two minutes late is an OTP that failed. The user has already tapped &quot;Resend&quot;, given up, or switched to a competitor&#39;s app. For most Indian businesses, OTP SMS delivery is the single most visible part of the messaging stack — and the one where small configuration mistakes cost the most.</p>
<p>This guide walks through the nine most common reasons OTP SMS is slow or never arrives, and what to do about each. Most of them are fixable in an afternoon.</p>
<h2 id="why-otp-sms-delivery-is-different-from-other-messages" class="tn-h">Why OTP SMS delivery is different from other messages<a class="tn-anchor" href="#why-otp-sms-delivery-is-different-from-other-messages" aria-label="Link to this section">#</a></h2>
<p>A promotional SMS that lands in ten minutes is fine. An OTP usually expires in five. That changes everything about how OTP traffic should be treated:</p>
<ul>
<li><strong>Speed matters more than cost.</strong> A slightly more expensive route that delivers in seconds beats a cheap route that queues.</li>
<li><strong>Every failure is visible.</strong> The user is staring at the screen, waiting.</li>
<li><strong>Volume is spiky.</strong> Logins peak in the morning and around sales; a flash sale can multiply OTP traffic in minutes.</li>
</ul>
<p>Keep those three facts in mind — every fix below comes back to one of them.</p>
<h2 id="1-the-dlt-template-doesn-t-match-the-message" class="tn-h">1. The DLT template doesn&#39;t match the message<a class="tn-anchor" href="#1-the-dlt-template-doesn-t-match-the-message" aria-label="Link to this section">#</a></h2>
<p>Every commercial SMS in India must match a template approved on the TRAI DLT portal. If your OTP text differs from the approved template by even a word, an extra space or a changed variable, operators reject it. This is the most common cause of &quot;the OTP never came&quot;.</p>
<p><strong>Fix:</strong> copy the approved template text exactly, and only change what sits inside the <code>{#var#}</code> placeholders. Keep the OTP itself in a single variable. If you change the wording, register the new template first. Our <a href="https://textnation.in/blog/trai-dlt-registration-guide-india-2026/">DLT registration guide</a> covers template rules in detail.</p>
<h2 id="2-the-otp-is-sent-on-the-wrong-route" class="tn-h">2. The OTP is sent on the wrong route<a class="tn-anchor" href="#2-the-otp-is-sent-on-the-wrong-route" aria-label="Link to this section">#</a></h2>
<p>OTP traffic should travel on a transactional or service route registered for it, with a header (sender ID) linked to the right template. Sending OTPs through a promotional header means DND numbers are blocked and time-window rules apply — so some users will never get the code.</p>
<p><strong>Fix:</strong> check that your OTP header and template are registered under the right category, and that your provider sends them on its transactional/service route, not the bulk promotional one.</p>
<h2 id="3-phone-numbers-are-stored-in-messy-formats" class="tn-h">3. Phone numbers are stored in messy formats<a class="tn-anchor" href="#3-phone-numbers-are-stored-in-messy-formats" aria-label="Link to this section">#</a></h2>
<p>&quot;98765 43210&quot;, &quot;+91-98765-43210&quot;, &quot;098765 43210&quot;, a number pasted from Excel with a hidden non-breaking space — they all look like the same number to a person. To a gateway, some are invalid. Numbers that arrive with invisible characters are a surprisingly common cause of silent OTP failures.</p>
<p><strong>Fix:</strong> normalise every number to one format (country code plus ten digits, e.g. 919876543210) before sending, and reject entries that aren&#39;t valid mobile numbers instead of passing them to the operator. TextNation does this automatically and lists anything that isn&#39;t a mobile number in the report, uncharged.</p>
<h2 id="4-otps-wait-in-the-same-queue-as-bulk-campaigns" class="tn-h">4. OTPs wait in the same queue as bulk campaigns<a class="tn-anchor" href="#4-otps-wait-in-the-same-queue-as-bulk-campaigns" aria-label="Link to this section">#</a></h2>
<p>If a 2-lakh-number promotional campaign and your login OTPs share one queue, the OTPs wait their turn. That&#39;s how a marketing send at 11 am becomes a login outage at 11:02.</p>
<p><strong>Fix:</strong> your provider should give OTP and transactional traffic its own priority lane that never waits behind bulk sends. We explain how priority queues work in <a href="https://textnation.in/blog/how-to-deliver-10m-messages-daily/">how to deliver 10M+ messages daily</a>.</p>
<h2 id="5-no-delivery-reports-are-being-watched" class="tn-h">5. No delivery reports are being watched<a class="tn-anchor" href="#5-no-delivery-reports-are-being-watched" aria-label="Link to this section">#</a></h2>
<p>Many teams send OTPs and never look at delivery reports. When an operator starts rejecting a template, or a route slows down, nobody notices until users complain.</p>
<p><strong>Fix:</strong> track delivery status for OTP traffic separately, and alert on two numbers: the delivery rate over the last 15 minutes, and the share of messages still waiting for a delivery report. A sudden drop in either is your early warning.</p>
<h2 id="6-users-tap-resend-too-fast" class="tn-h">6. Users tap &quot;Resend&quot; too fast<a class="tn-anchor" href="#6-users-tap-resend-too-fast" aria-label="Link to this section">#</a></h2>
<p>When a code hasn&#39;t arrived after 10 seconds, users tap Resend. Each tap sends another OTP, invalidates the previous one, and adds load. Sometimes the first OTP arrives a moment later — and no longer works.</p>
<p><strong>Fix:</strong> show a visible countdown (30–60 seconds) before Resend is enabled, keep the previous code valid until the new one is delivered, and offer an alternative channel on the second attempt rather than a third SMS.</p>
<h2 id="7-there-s-no-fallback-channel" class="tn-h">7. There&#39;s no fallback channel<a class="tn-anchor" href="#7-there-s-no-fallback-channel" aria-label="Link to this section">#</a></h2>
<p>SMS can fail for reasons outside your control: the phone is out of coverage, the inbox is full, a network is congested. If SMS is the only channel, the user is stuck.</p>
<p><strong>Fix:</strong> offer a second channel. WhatsApp authentication templates are built for one-time codes, with a copy-code button, and most Indian smartphone users have WhatsApp. A voice call that reads out the code works on any phone. Offer the fallback after the first resend.</p>
<h2 id="8-otp-abuse-is-eating-your-capacity" class="tn-h">8. OTP abuse is eating your capacity<a class="tn-anchor" href="#8-otp-abuse-is-eating-your-capacity" aria-label="Link to this section">#</a></h2>
<p>Bots that hit your &quot;Send OTP&quot; endpoint with random numbers — OTP pumping — cost you money and can slow down delivery for real users. It usually shows up as a sudden spike of OTPs to numbers that never verify.</p>
<p><strong>Fix:</strong> rate-limit OTP requests per number, per IP and per device; add a CAPTCHA after repeated attempts; and watch the ratio of OTPs sent to OTPs verified. A healthy flow verifies most codes — a falling ratio means someone is abusing the endpoint.</p>
<h2 id="9-the-message-itself-is-hard-to-use" class="tn-h">9. The message itself is hard to use<a class="tn-anchor" href="#9-the-message-itself-is-hard-to-use" aria-label="Link to this section">#</a></h2>
<p>Even a delivered OTP can fail if the user can&#39;t use it quickly. Codes buried in long text, missing the app name, or written in a way that phone keyboards can&#39;t auto-fill all slow people down.</p>
<p><strong>Fix:</strong> put the code first, name your brand, say how long it&#39;s valid, and add the app hash if you use Android&#39;s SMS Retriever API so the code fills in automatically. For example: &quot;482910 is your TextNation login code. Valid for 5 minutes. Do not share it.&quot;</p>
<h2 id="a-quick-otp-delivery-checklist" class="tn-h">A quick OTP delivery checklist<a class="tn-anchor" href="#a-quick-otp-delivery-checklist" aria-label="Link to this section">#</a></h2>
<ul>
<li>OTP text matches the approved DLT template exactly</li>
<li>Sent on a transactional/service header, not promotional</li>
<li>Numbers normalised before sending; invalid entries rejected</li>
<li>OTPs have a priority lane that never waits behind bulk sends</li>
<li>Delivery rate and pending reports monitored, with alerts</li>
<li>Resend countdown and a fallback channel (WhatsApp or voice)</li>
<li>Rate limits and abuse monitoring on the OTP endpoint</li>
<li>Code first in the message, with brand name and validity</li>
</ul>
]]></content:encoded>
    </item>
    <item>
      <title>WhatsApp Template Categories Explained: Marketing, Utility and Authentication</title>
      <link>https://textnation.in/blog/whatsapp-template-categories-explained/</link>
      <guid isPermaLink="true">https://textnation.in/blog/whatsapp-template-categories-explained/</guid>
      <pubDate>Sun, 18 Oct 2026 06:17:37 GMT</pubDate>
      <dc:creator>TextNation Product Team</dc:creator>
      <category>Guides</category>
      <description>Marketing, Utility and Authentication WhatsApp templates explained: what each allows, how pricing depends on category, and how to avoid Meta recategorisation.</description>
      <content:encoded><![CDATA[<p>Every business-initiated WhatsApp message goes out as an approved template, and every template belongs to a category: <strong>Marketing</strong>, <strong>Utility</strong> or <strong>Authentication</strong>. The category decides what the message is allowed to say, how Meta reviews it — and what you pay for it.</p>
<p>Getting WhatsApp template categories right is the difference between templates that sail through approval and campaigns that are paused, rejected or billed at a higher rate than you planned. This guide explains each category, how Meta decides, and how to avoid the most common surprises.</p>
<h2 id="the-three-whatsapp-template-categories" class="tn-h">The three WhatsApp template categories<a class="tn-anchor" href="#the-three-whatsapp-template-categories" aria-label="Link to this section">#</a></h2>
<div class="tn-table"><table>
<thead>
<tr>
<th>Category</th>
<th>Use it for</th>
<th>Typical examples</th>
</tr>
</thead>
<tbody><tr>
<td>Marketing</td>
<td>Promotions, offers, re-engagement, anything that sells</td>
<td>Festive sale, abandoned cart, new collection, &quot;we miss you&quot;</td>
</tr>
<tr>
<td>Utility</td>
<td>Updates about a transaction or account the user already has</td>
<td>Order confirmed, shipment dispatched, payment received, appointment reminder</td>
</tr>
<tr>
<td>Authentication</td>
<td>One-time codes that verify a user</td>
<td>Login code, payment confirmation code, account recovery code</td>
</tr>
</tbody></table></div>
<p>The rule of thumb: if the message would still make sense to send even if you had nothing to sell, it&#39;s probably Utility. If any part of it promotes something, it&#39;s Marketing.</p>
<h2 id="marketing-templates" class="tn-h">Marketing templates<a class="tn-anchor" href="#marketing-templates" aria-label="Link to this section">#</a></h2>
<p>Marketing templates are the most flexible. They can include images, video, documents, buttons, links and carousels, and they can promote anything that WhatsApp&#39;s commerce policy allows.</p>
<p>They are also the most closely watched. Users can block or report marketing messages, and a template with poor feedback can be paused or limited by Meta. Users can also opt out of marketing messages from a business — so marketing templates need consent, relevance and frequency limits.</p>
<h2 id="utility-templates" class="tn-h">Utility templates<a class="tn-anchor" href="#utility-templates" aria-label="Link to this section">#</a></h2>
<p>Utility templates confirm, update or remind users about something they already started: an order, a booking, a payment, a support request. They must be specific to that transaction.</p>
<p>What turns a Utility template into Marketing is usually one extra line. &quot;Your order has shipped&quot; is Utility. &quot;Your order has shipped — use code SAVE10 on your next purchase&quot; is Marketing. Meta reviews the whole message, not just the first sentence.</p>
<h2 id="authentication-templates" class="tn-h">Authentication templates<a class="tn-anchor" href="#authentication-templates" aria-label="Link to this section">#</a></h2>
<p>Authentication templates carry one-time passcodes, and they are the most structured. Meta provides the message format; you supply the code. The template can add a security disclaimer and an expiry note, and it uses a copy-code or one-tap button so the user can enter the code quickly. Links, media and promotional text are not allowed.</p>
<p>If you&#39;re building login flows, an authentication template is a strong fallback when SMS OTPs don&#39;t arrive — see our guide on <a href="https://textnation.in/blog/otp-sms-delivery-fixes/">why OTP SMS fails and how to fix it</a>.</p>
<h2 id="how-pricing-depends-on-the-category" class="tn-h">How pricing depends on the category<a class="tn-anchor" href="#how-pricing-depends-on-the-category" aria-label="Link to this section">#</a></h2>
<p>WhatsApp Business Platform pricing is set per category and per country. Meta charges for template messages by category, with Marketing typically priced highest and Authentication and Utility lower. Utility templates sent while a customer-service window is open (within 24 hours of the user&#39;s last message) are not charged.</p>
<p>Rates change, so always check Meta&#39;s current rate card for India before planning a large campaign. The point to remember: <strong>the category directly changes your cost</strong>, which is why recategorisation matters.</p>
<h2 id="when-meta-changes-a-template-s-category" class="tn-h">When Meta changes a template&#39;s category<a class="tn-anchor" href="#when-meta-changes-a-template-s-category" aria-label="Link to this section">#</a></h2>
<p>This is the surprise that catches most teams. You get a template approved as Utility, build a flow around it, and later Meta reclassifies it as Marketing — so every message now costs more, and marketing opt-outs apply.</p>
<p>Common triggers:</p>
<ul>
<li>A discount code, offer or &quot;shop now&quot; line inside a utility message</li>
<li>Generic wording that isn&#39;t tied to a specific transaction (&quot;Here&#39;s an update for you&quot;)</li>
<li>Buttons that lead to a product catalogue rather than the order</li>
<li>Sending the same &quot;utility&quot; text to users who never made a transaction</li>
</ul>
<p>TextNation watches for these changes. If a template moves from Utility to Marketing while a campaign is running, the campaign pauses and shows you the change — so you decide whether to continue at the new rate, instead of finding out from the invoice.</p>
<h2 id="how-to-get-templates-approved-first-time" class="tn-h">How to get templates approved first time<a class="tn-anchor" href="#how-to-get-templates-approved-first-time" aria-label="Link to this section">#</a></h2>
<ol>
<li><strong>Pick the honest category.</strong> Submitting a promotional message as Utility to save money usually ends in rejection or recategorisation.</li>
<li><strong>Be specific.</strong> Reference the transaction: &quot;Your order {{1}} for {{2}} has been shipped.&quot;</li>
<li><strong>Use sample values.</strong> Give realistic examples for every variable so the reviewer understands the message.</li>
<li><strong>Keep variables away from the edges.</strong> A template that starts or ends with a variable, or has two variables side by side, is more likely to be rejected.</li>
<li><strong>Match buttons to the purpose.</strong> A utility template&#39;s button should open the order, booking or ticket — not the home page.</li>
<li><strong>Avoid near-duplicates.</strong> Many almost-identical templates are harder to manage; use variables instead.</li>
</ol>
<h2 id="template-categories-at-a-glance" class="tn-h">Template categories at a glance<a class="tn-anchor" href="#template-categories-at-a-glance" aria-label="Link to this section">#</a></h2>
<ul>
<li><strong>Marketing</strong> — anything promotional; most flexible; needs consent; highest cost</li>
<li><strong>Utility</strong> — specific to a user&#39;s transaction or account; lower cost; free inside an open service window</li>
<li><strong>Authentication</strong> — one-time codes only; fixed format with a copy-code button; no links or media</li>
</ul>
<p>For a broader comparison of WhatsApp with SMS on reach, open rates and cost, read <a href="https://textnation.in/blog/whatsapp-business-api-vs-sms/">WhatsApp Business API vs SMS</a>, or see how <a href="https://textnation.in/services/whatsapp-business-api/">TextNation&#39;s WhatsApp Business API</a> handles templates, campaigns and replies.</p>
]]></content:encoded>
    </item>
    <item>
      <title>RCS Business Messaging in India: What It Is and When to Use It</title>
      <link>https://textnation.in/blog/rcs-business-messaging-india/</link>
      <guid isPermaLink="true">https://textnation.in/blog/rcs-business-messaging-india/</guid>
      <pubDate>Sun, 18 Oct 2026 06:17:37 GMT</pubDate>
      <dc:creator>TextNation Product Team</dc:creator>
      <category>Strategy</category>
      <description>What RCS business messaging is, how it compares with SMS and WhatsApp in India, the best use cases, and how to launch it with automatic SMS fallback.</description>
      <content:encoded><![CDATA[<p>For years, business messaging in India has meant two options: plain SMS that reaches everyone, or WhatsApp that needs the user&#39;s opt-in and an approved template. RCS business messaging sits between the two. It arrives in the phone&#39;s default messaging app like an SMS, but looks and behaves like a modern chat — with your brand name, logo, images, carousels and buttons.</p>
<p>This guide explains what RCS business messaging is, what it can do in India today, where it beats SMS and WhatsApp, and how to roll it out without losing reach.</p>
<h2 id="what-is-rcs-business-messaging" class="tn-h">What is RCS business messaging?<a class="tn-anchor" href="#what-is-rcs-business-messaging" aria-label="Link to this section">#</a></h2>
<p>RCS (Rich Communication Services) is the upgrade to SMS built into Android&#39;s messaging app (Google Messages). When a business sends an RCS message, the user sees:</p>
<ul>
<li><strong>A verified sender</strong> — your brand name and logo with a verification badge, instead of a six-character header</li>
<li><strong>Rich content</strong> — images, GIFs, video and rich cards with a title, description and buttons</li>
<li><strong>Carousels</strong> — several cards side by side, for products, plans or offers</li>
<li><strong>Suggested replies and actions</strong> — tappable buttons that open a link, start a call, show a location or send a reply</li>
<li><strong>Read receipts</strong> — you know when the message was read, not just delivered</li>
</ul>
<p>The user doesn&#39;t install anything. If their phone supports RCS, the message simply arrives richer.</p>
<h2 id="rcs-vs-sms-vs-whatsapp" class="tn-h">RCS vs SMS vs WhatsApp<a class="tn-anchor" href="#rcs-vs-sms-vs-whatsapp" aria-label="Link to this section">#</a></h2>
<div class="tn-table"><table>
<thead>
<tr>
<th></th>
<th>SMS</th>
<th>RCS</th>
<th>WhatsApp</th>
</tr>
</thead>
<tbody><tr>
<td>Where it arrives</td>
<td>Default messaging app</td>
<td>Default messaging app (RCS-enabled Android)</td>
<td>WhatsApp app</td>
</tr>
<tr>
<td>Sender identity</td>
<td>6-character header</td>
<td>Brand name, logo, verified badge</td>
<td>Business name and profile</td>
</tr>
<tr>
<td>Rich media and buttons</td>
<td>No</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Read receipts</td>
<td>No</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Reach</td>
<td>Every mobile phone</td>
<td>Phones with RCS enabled</td>
<td>Users with WhatsApp</td>
</tr>
<tr>
<td>Needs prior opt-in</td>
<td>DLT rules apply</td>
<td>Brand agent approved before launch</td>
<td>Yes, plus approved templates</td>
</tr>
</tbody></table></div>
<p>No single channel wins everywhere. SMS has the widest reach, WhatsApp has deep engagement, and RCS adds a rich, branded experience inside the inbox people already check for OTPs and alerts.</p>
<h2 id="where-rcs-works-best" class="tn-h">Where RCS works best<a class="tn-anchor" href="#where-rcs-works-best" aria-label="Link to this section">#</a></h2>
<p><strong>Promotions that need visuals.</strong> A carousel of three products with &quot;Buy now&quot; buttons converts very differently from a 160-character SMS with a link.</p>
<p><strong>Transactional journeys.</strong> Order updates with a &quot;Track order&quot; button, appointment reminders with &quot;Reschedule&quot; and &quot;Get directions&quot;, payment alerts with &quot;View statement&quot;.</p>
<p><strong>Trust-sensitive messages.</strong> A verified brand name and logo help users tell a real message from a spoof — useful for banks, insurers and delivery companies whose names are often impersonated.</p>
<h2 id="the-reach-question-and-how-fallback-solves-it" class="tn-h">The reach question — and how fallback solves it<a class="tn-anchor" href="#the-reach-question-and-how-fallback-solves-it" aria-label="Link to this section">#</a></h2>
<p>Not every phone can receive RCS. iPhones, older Android phones, and devices where RCS is turned off will not get the rich version. That&#39;s why RCS should never be a separate channel you switch to — it should be the first attempt, with SMS as the automatic backup.</p>
<p>With <strong>RCS-first, SMS-fallback</strong>, the platform checks whether the number can receive RCS. If it can, the rich message goes out. If it can&#39;t — or the RCS message isn&#39;t delivered within a set time — the same content goes out as SMS on your DLT-registered header. Every user gets the message; the ones who can see more, do.</p>
<h2 id="building-journeys-with-rcs" class="tn-h">Building journeys with RCS<a class="tn-anchor" href="#building-journeys-with-rcs" aria-label="Link to this section">#</a></h2>
<p>RCS gets more powerful when one message leads to the next. A user who taps &quot;Interested&quot; on a carousel can automatically get a follow-up; someone who didn&#39;t read the first message can get an SMS reminder the next day. TextNation&#39;s <a href="https://textnation.in/services/journey-builder/">Journey Builder</a> lets you design these flows visually across RCS, SMS, WhatsApp and voice.</p>
<h2 id="how-to-launch-rcs-business-messaging" class="tn-h">How to launch RCS business messaging<a class="tn-anchor" href="#how-to-launch-rcs-business-messaging" aria-label="Link to this section">#</a></h2>
<ol>
<li><strong>Register your brand agent.</strong> Your RCS sender (the &quot;agent&quot;) is set up with your brand name, logo, colours, description and contact details, then verified and approved before it can message users.</li>
<li><strong>Design for rich content.</strong> Plan images (and their sizes), card titles, buttons and suggested replies. Keep text short — RCS is visual.</li>
<li><strong>Turn on SMS fallback.</strong> Make sure every RCS message has an SMS version on a registered DLT header and template.</li>
<li><strong>Start with transactional traffic.</strong> Measure RCS reach and read rates on messages you already send.</li>
<li><strong>Expand to campaigns.</strong> Use carousels and rich cards for offers, with clear opt-out options.</li>
<li><strong>Measure end to end.</strong> Compare read rates, button taps and conversions with your SMS baseline.</li>
</ol>
<h2 id="is-rcs-right-for-your-business" class="tn-h">Is RCS right for your business?<a class="tn-anchor" href="#is-rcs-right-for-your-business" aria-label="Link to this section">#</a></h2>
<p>RCS is a strong fit if you send high volumes of transactional messages, run visual promotions, or need users to trust that a message really comes from you. Combined with SMS fallback, it upgrades the experience for every user who can receive it, without losing anyone who can&#39;t.</p>
<p>To compare RCS with the other channels in more depth, read <a href="https://textnation.in/blog/whatsapp-business-api-vs-sms/">WhatsApp Business API vs SMS</a>, or explore <a href="https://textnation.in/services/rcs-messaging/">RCS messaging on TextNation</a>.</p>
]]></content:encoded>
    </item>
    <item>
      <title>How to Deliver 10M+ Messages Daily: Infrastructure &amp; Reliability</title>
      <link>https://textnation.in/blog/how-to-deliver-10m-messages-daily/</link>
      <guid isPermaLink="true">https://textnation.in/blog/how-to-deliver-10m-messages-daily/</guid>
      <pubDate>Wed, 20 May 2026 04:30:00 GMT</pubDate>
      <dc:creator>TextNation Product Team</dc:creator>
      <category>Engineering</category>
      <description>A deep dive into high-throughput enterprise messaging architecture — direct carrier peering, queue management, retry logic, DND filtering, and real-time…</description>
      <content:encoded><![CDATA[<p>Sending one SMS is trivial. Sending 10 million SMS messages per day — with sub-second delivery latency, 99.9%+ delivery rates, real-time status tracking, and zero single points of failure — is an engineering challenge that most platforms quietly struggle with. This article explains how it&#39;s done.</p>
<p>Whether you are evaluating an enterprise SMS provider or building your own messaging infrastructure, understanding these layers will help you ask the right questions and set realistic expectations.</p>
<h2 id="layer-1-carrier-connectivity-direct-peering-vs-aggregator-routing" class="tn-h">Layer 1 — Carrier Connectivity: Direct Peering vs Aggregator Routing<a class="tn-anchor" href="#layer-1-carrier-connectivity-direct-peering-vs-aggregator-routing" aria-label="Link to this section">#</a></h2>
<p>Every SMS ultimately travels over a telecom operator&#39;s network. How a messaging platform connects to those networks is the most fundamental architectural decision — and the one with the greatest impact on delivery rates and latency.</p>
<h3 id="aggregator-routing-the-common-approach" class="tn-h">Aggregator routing (the common approach)<a class="tn-anchor" href="#aggregator-routing-the-common-approach" aria-label="Link to this section">#</a></h3>
<p>Most SMS providers purchase capacity from wholesale SMS aggregators, who in turn connect to carriers. The typical chain looks like: your application → SMS platform → aggregator A → aggregator B → carrier → subscriber. Each hop adds latency (10–500ms per hop), introduces a potential failure point, and reduces delivery reliability. Grey routes — unauthorised paths that bypass carrier agreements — are common in aggregator networks and violate TRAI regulations.</p>
<h3 id="direct-carrier-peering-the-enterprise-approach" class="tn-h">Direct carrier peering (the enterprise approach)<a class="tn-anchor" href="#direct-carrier-peering-the-enterprise-approach" aria-label="Link to this section">#</a></h3>
<p>A direct carrier connection means the messaging platform has a bilateral agreement with the telecom operator and connects via a dedicated SMPP (Short Message Peer-to-Peer) link directly to the carrier&#39;s SMSC (Short Message Service Centre). The chain becomes: your application → SMS platform → carrier SMSC → subscriber.</p>
<p>The benefits are substantial:</p>
<ul>
<li>✓Sub-100ms delivery latency for domestic messages</li>
<li>✓Direct DLR (Delivery Receipt) from the carrier — not an estimated status from an aggregator</li>
<li>✓No grey routing — 100% compliance with TRAI regulations</li>
<li>✓Higher throughput limits negotiated directly with the carrier</li>
<li>✓Dedicated connections that are not shared with other customers during peak periods</li>
<li>✓Carrier-level visibility into why a message failed (handset off, number invalid, DND, etc.)</li>
</ul>
<p>TextNation maintains direct SMPP connections to all four major Indian carriers: Airtel, Jio, BSNL, and Vi. This means every message is routed based on the subscriber&#39;s actual current carrier (not a static lookup), and delivery receipts reflect the actual handset status.</p>
<h2 id="layer-2-the-smpp-protocol-and-throughput-management" class="tn-h">Layer 2 — The SMPP Protocol and Throughput Management<a class="tn-anchor" href="#layer-2-the-smpp-protocol-and-throughput-management" aria-label="Link to this section">#</a></h2>
<p>SMPP (Short Message Peer-to-Peer) is the industry-standard protocol for SMS communication between messaging platforms and carrier SMSCs. It operates over TCP/IP using a persistent connection (unlike HTTP, which is stateless).</p>
<p>Key SMPP parameters relevant to high-throughput deployments:</p>
<pre><code>// Key SMPP throughput parameters
max_outstanding_pdus: 500     // concurrent unacknowledged messages per link
window_size: 256              // sliding window for pipelining
enquire_link_timer: 30s       // heartbeat to detect dead connections
session_init_timer: 10s       // connection establishment timeout
submit_sm_throttle: 1000/s    // per-link submit rate
</code></pre>
<p>To achieve 1M+ messages per hour, a platform needs multiple parallel SMPP connections to each carrier. A single SMPP link with a window size of 256 and 500ms average latency can theoretically sustain ~500 messages/second. To reach 1,000+ messages/second per carrier, you need at least 2–4 parallel links, with automatic load balancing across them.</p>
<p>Connection pooling — maintaining a pool of pre-established SMPP sessions rather than opening new connections per batch — is essential. SMPP session establishment takes 100–300ms; a cold-start approach would destroy throughput at scale.</p>
<h2 id="layer-3-queue-architecture-and-priority-management" class="tn-h">Layer 3 — Queue Architecture and Priority Management<a class="tn-anchor" href="#layer-3-queue-architecture-and-priority-management" aria-label="Link to this section">#</a></h2>
<p>Not all messages are equal. An OTP that expires in 60 seconds must be delivered immediately. A promotional campaign can afford to be delivered within a 2-hour window. Queue architecture must reflect this reality.</p>
<p>A production-grade messaging queue has at minimum three priority tiers:</p>
<div class="tn-table"><table>
<thead>
<tr>
<th>Tier</th>
<th>Examples</th>
<th>Throughput mode</th>
<th>Default TTL</th>
</tr>
</thead>
<tbody><tr>
<td><strong>P1 — Critical</strong></td>
<td>OTPs, 2FA codes, payment alerts, banking notifications</td>
<td>Highest — direct to carrier with minimal queuing</td>
<td>60–300 seconds</td>
</tr>
<tr>
<td><strong>P2 — Transactional</strong></td>
<td>Order confirmations, delivery updates, appointment reminders</td>
<td>High — 5–30 second queue depth acceptable</td>
<td>24 hours</td>
</tr>
<tr>
<td><strong>P3 — Promotional</strong></td>
<td>Marketing campaigns, bulk announcements, promotional offers</td>
<td>Rate-limited — distributed across configured send window</td>
<td>72 hours or campaign end</td>
</tr>
</tbody></table></div>
<p>At 10M messages/day, promotional campaigns represent the bulk of volume — often 70–80% of daily traffic. Rate-limiting P3 traffic is essential so that a sudden spike in promotional sends does not degrade OTP delivery times for other customers on the platform.</p>
<p>The queue itself is typically built on a distributed message broker (Apache Kafka, RabbitMQ, or AWS SQS, depending on the architecture). Consumer workers pull from the queue and submit to carrier SMPP connections. The number of consumer workers scales horizontally with load.</p>
<h2 id="layer-4-dnd-filtering-blacklist-management-and-dlt-validation" class="tn-h">Layer 4 — DND Filtering, Blacklist Management, and DLT Validation<a class="tn-anchor" href="#layer-4-dnd-filtering-blacklist-management-and-dlt-validation" aria-label="Link to this section">#</a></h2>
<p>Before any promotional message enters the queue, it must pass through regulatory filters:</p>
<ol>
<li><strong>DND/NDNC registry check</strong> — TRAI publishes a National Do Not Call (NDNC) registry. Enterprise platforms download and index this list (updated daily by TRAI) and filter all promotional submissions against it before queuing. At 10M messages/day, this filter must be a fast in-memory lookup — a hash set or bloom filter — not a database query per message.</li>
<li><strong>Internal blacklist / unsubscribe management</strong> — Numbers that have replied with &quot;STOP,&quot; raised complaints, or are flagged as invalid must be excluded. This list is maintained in-platform and merged with the NDNC filter before every batch send.</li>
<li><strong>DLT parameter validation</strong> — Every message must carry a valid Entity ID, Header, and Template ID. Invalid DLT parameters result in carrier rejection. Validation at submission time (before queuing) prevents wasted capacity and helps customers identify misconfigured API calls before they become a bulk delivery failure.</li>
<li><strong>Time-window enforcement</strong> — Promotional SMS is restricted to 9am–9pm IST by TRAI. Messages submitted for promotional delivery outside this window must be held in the queue until the window opens — not silently dropped.</li>
</ol>
<h2 id="layer-5-retry-logic-and-failure-handling" class="tn-h">Layer 5 — Retry Logic and Failure Handling<a class="tn-anchor" href="#layer-5-retry-logic-and-failure-handling" aria-label="Link to this section">#</a></h2>
<p>Not every message delivers on the first attempt. Handsets are switched off, in areas with poor coverage, or temporarily unreachable. Carriers return specific error codes that indicate whether a retry is warranted:</p>
<div class="tn-table"><table>
<thead>
<tr>
<th>Error Code Category</th>
<th>Retry Strategy</th>
</tr>
</thead>
<tbody><tr>
<td>Absent subscriber (handset off / unreachable)</td>
<td>Exponential backoff: 1 min → 5 min → 15 min → 30 min → 1 hr. Max 6 retries within TTL.</td>
</tr>
<tr>
<td>Subscriber busy (in a call, for older networks)</td>
<td>Retry after 2 minutes. Max 3 retries.</td>
</tr>
<tr>
<td>Invalid number / number not in service</td>
<td>No retry. Mark as permanently failed. Flag for customer.</td>
</tr>
<tr>
<td>DND blocked</td>
<td>No retry. Log as filtered. Update DND cache.</td>
</tr>
<tr>
<td>Carrier congestion (temporary throttle)</td>
<td>Retry with exponential backoff. Route to secondary carrier if available.</td>
</tr>
<tr>
<td>DLT validation failure</td>
<td>No retry. Return error to client immediately. Log DLT params for debugging.</td>
</tr>
</tbody></table></div>
<p>Intelligent retry logic — as opposed to blind retry-everything approaches — is critical for both delivery rates and cost efficiency. Retrying permanently invalid numbers wastes carrier capacity and inflates customer costs.</p>
<h2 id="layer-6-carrier-failover-and-load-balancing" class="tn-h">Layer 6 — Carrier Failover and Load Balancing<a class="tn-anchor" href="#layer-6-carrier-failover-and-load-balancing" aria-label="Link to this section">#</a></h2>
<p>No single carrier is reliable 100% of the time. Planned maintenance windows, unplanned outages, and regional degradations happen. At 10M messages/day, a 30-minute carrier outage can mean 200,000+ undelivered messages if there is no failover.</p>
<p>Carrier failover requires:</p>
<ul>
<li>✓<strong>Real-time health monitoring</strong> of each carrier connection — tracking submission success rates, delivery rates, and response latencies on a per-minute basis.</li>
<li>✓<strong>Automatic rerouting</strong> — when a carrier&#39;s success rate drops below a threshold (e.g., 95% within 5 minutes), traffic is automatically shifted to backup carriers.</li>
<li>✓<strong>Subscriber MNP (Mobile Number Portability) awareness</strong> — routing messages to the subscriber&#39;s current carrier, not their original carrier. India has had significant MNP adoption; routing to the wrong carrier for a ported number adds an unnecessary hop.</li>
</ul>
<p>Load balancing across carriers also improves cost efficiency. Carriers offer different pricing tiers for volume commitments. A well-designed platform routes messages to the most cost-effective carrier for each traffic type while maintaining delivery quality thresholds.</p>
<h2 id="layer-7-real-time-delivery-monitoring" class="tn-h">Layer 7 — Real-Time Delivery Monitoring<a class="tn-anchor" href="#layer-7-real-time-delivery-monitoring" aria-label="Link to this section">#</a></h2>
<p>At 10M messages/day, delivery monitoring is not a reporting feature — it is an operational necessity. The monitoring stack needs to answer these questions in real time:</p>
<ul>
<li>What is the current delivery rate per carrier, per message type, per customer?</li>
<li>Are any carrier connections degraded or failed?</li>
<li>Is the queue depth growing (indicating a processing bottleneck)?</li>
<li>Are any customers sending at abnormally high rates (potential abuse)?</li>
<li>What is the average end-to-end latency for P1 messages in the last 5 minutes?</li>
</ul>
<p>TextNation&#39;s analytics dashboard surfaces per-campaign and per-carrier delivery statistics in real time, with alerting for delivery rate drops below configurable thresholds. Enterprise customers can also receive webhooks for each delivery receipt event, enabling real-time status updates in their own applications.</p>
<h2 id="what-to-look-for-in-an-enterprise-sms-provider" class="tn-h">What to Look for in an Enterprise SMS Provider<a class="tn-anchor" href="#what-to-look-for-in-an-enterprise-sms-provider" aria-label="Link to this section">#</a></h2>
<p>Based on the architecture layers above, here are the questions to ask any enterprise SMS provider:</p>
<ul>
<li><strong>Q1: Do you have direct carrier connections or do you use aggregators?</strong> — Direct connections = lower latency, higher delivery rates, no grey routing.</li>
<li><strong>Q2: Which Indian carriers do you have direct SMPP agreements with?</strong> — You want coverage of Airtel, Jio, BSNL, and Vi minimum.</li>
<li><strong>Q3: What is your sustained throughput capacity per customer?</strong> — Ask for limits in messages/second, not messages/month. Burst capacity matters for OTP use cases.</li>
<li><strong>Q4: How do you handle carrier failover?</strong> — Ask for specifics: detection threshold, failover time, whether it is automatic or manual.</li>
<li><strong>Q5: Do you provide real DLR from carriers or synthetic status estimates?</strong> — Some providers return &quot;delivered&quot; based on submission confirmation, not actual carrier DLR.</li>
<li><strong>Q6: What is your uptime SLA and how is downtime measured?</strong> — Get this in writing. Ask for historical uptime data.</li>
<li><strong>Q7: How do you handle DLT compliance on my behalf?</strong> — Do they validate DLT parameters at submission? Do they manage DND filtering?</li>
</ul>
]]></content:encoded>
    </item>
    <item>
      <title>WhatsApp Business API vs SMS: Which Channel Converts Better?</title>
      <link>https://textnation.in/blog/whatsapp-business-api-vs-sms/</link>
      <guid isPermaLink="true">https://textnation.in/blog/whatsapp-business-api-vs-sms/</guid>
      <pubDate>Sun, 10 May 2026 04:30:00 GMT</pubDate>
      <dc:creator>TextNation Product Team</dc:creator>
      <category>Strategy</category>
      <description>Data-driven comparison of WhatsApp Business API and SMS for Indian enterprises. Open rates, CTR, cost per conversion, compliance overhead, and which channel…</description>
      <content:encoded><![CDATA[<p>Every Indian enterprise messaging team faces the same question at some point: should we invest in WhatsApp Business API, or does SMS remain the better-performing channel for our use case? The honest answer is that it depends — but in ways that are predictable and measurable.</p>
<p>This article breaks down the comparison across six dimensions: reach, open rates, engagement, cost, compliance overhead, and integration complexity. We end with a use-case decision matrix so you can make the call for your specific situation.</p>
<h2 id="1-reach-who-can-you-actually-message" class="tn-h">1. Reach: Who Can You Actually Message?<a class="tn-anchor" href="#1-reach-who-can-you-actually-message" aria-label="Link to this section">#</a></h2>
<h3 id="sms" class="tn-h">SMS<a class="tn-anchor" href="#sms" aria-label="Link to this section">#</a></h3>
<p>SMS works on every mobile phone in India — from a ₹500 feature phone in rural Rajasthan to the latest iPhone. There are approximately 1.1 billion mobile subscribers in India (TRAI, 2025), and virtually all of them can receive SMS. No app installation is required. No internet connectivity is needed.</p>
<p>The caveat: promotional SMS cannot be delivered to numbers registered on the DND/NDNC registry. As of 2025, approximately 300 million Indian numbers are DND-registered. For transactional and OTP messages, DND restrictions do not apply.</p>
<h3 id="whatsapp" class="tn-h">WhatsApp<a class="tn-anchor" href="#whatsapp" aria-label="Link to this section">#</a></h3>
<p>WhatsApp has approximately 500 million active users in India, making it the world&#39;s largest WhatsApp market. However, this means roughly 55% of Indian mobile subscribers are reachable on WhatsApp — a significant gap compared to SMS.</p>
<p>WhatsApp requires the recipient to have the app installed and an active data connection. Users in rural areas or on older devices may not receive WhatsApp messages reliably. For this reason, enterprise platforms like TextNation offer SMS fallback — if a WhatsApp message fails to deliver within a configured window, an SMS is automatically sent instead.</p>
<h2 id="2-open-rates-who-actually-reads-the-message" class="tn-h">2. Open Rates: Who Actually Reads the Message?<a class="tn-anchor" href="#2-open-rates-who-actually-reads-the-message" aria-label="Link to this section">#</a></h2>
<p>SMS achieves a 98% open rate in India, with most messages read within 3 minutes of delivery. This is not because people love SMS — it&#39;s because the notification is inescapable and the message appears in a clean, distraction-free inbox.</p>
<p>WhatsApp achieves 70–80% open rates, which are substantially higher than email (20–25% in India) but lower than SMS. The gap widens for promotional messages: WhatsApp users are increasingly using the &quot;mute&quot; and &quot;archive&quot; features for business messages they find irrelevant. WhatsApp also introduced the &quot;Recent Updates&quot; section for business broadcasts in 2024, creating a separation from personal messages.</p>
<p>The critical nuance: SMS open rate measures whether the message was opened, not whether it was read. A user who opens an SMS notification without reading is counted. WhatsApp&#39;s read receipts (double blue ticks) provide a more reliable signal of genuine engagement.</p>
<h2 id="3-click-through-and-conversion-rates" class="tn-h">3. Click-Through and Conversion Rates<a class="tn-anchor" href="#3-click-through-and-conversion-rates" aria-label="Link to this section">#</a></h2>
<p>This is where WhatsApp has a clear structural advantage. WhatsApp supports interactive message types that SMS cannot match:</p>
<ul>
<li>✓ Quick reply buttons (up to 3) that reduce friction to a single tap</li>
<li>✓ Call-to-action buttons with URLs or phone numbers</li>
<li>✓ Rich media: images, PDFs, videos, location pins</li>
<li>✓ Product catalogues and list messages for e-commerce</li>
</ul>
<p>Based on aggregated data from TextNation&#39;s enterprise clients across BFSI, e-commerce, and healthcare verticals in 2025: WhatsApp interactive messages achieved a 15–25% CTR compared to 6–8% for SMS links. The highest performers were WhatsApp template messages with a single, prominent CTA button and a relevant visual.</p>
<p>However, SMS CTR has improved with the adoption of RCS (Rich Communication Services), which brings WhatsApp-like buttons and media to the SMS channel. For operators supporting RCS (primarily Airtel and Jio in India), RCS achieves CTRs comparable to WhatsApp at SMS-equivalent costs.</p>
<h2 id="4-cost-comparison" class="tn-h">4. Cost Comparison<a class="tn-anchor" href="#4-cost-comparison" aria-label="Link to this section">#</a></h2>
<p>Cost structures differ fundamentally between the two channels:</p>
<div class="tn-table"><table>
<thead>
<tr>
<th>Factor</th>
<th>SMS</th>
<th>WhatsApp Business API</th>
</tr>
</thead>
<tbody><tr>
<td>Per message cost</td>
<td>₹0.04–₹0.15</td>
<td>₹0.30–₹0.80 per conversation (24-hr window)</td>
</tr>
<tr>
<td>Pricing model</td>
<td>Per message</td>
<td>Per 24-hour conversation (not per message)</td>
</tr>
<tr>
<td>Free tier</td>
<td>None</td>
<td>1,000 free conversations/month (via Meta)</td>
</tr>
<tr>
<td>Setup cost</td>
<td>Low (DLT registration)</td>
<td>Moderate (Meta BSP onboarding, business verification)</td>
</tr>
<tr>
<td>Variable costs</td>
<td>Flat per message</td>
<td>Varies by conversation category (marketing, utility, service)</td>
</tr>
<tr>
<td>Volume discounts</td>
<td>Significant at scale</td>
<td>Tiered by Meta; passed through by BSPs</td>
</tr>
</tbody></table></div>
<p>For high-volume transactional use cases (OTPs at 500K/day, delivery alerts, bank notifications), SMS is dramatically cheaper. The math is simple: at ₹0.08/SMS, sending 100,000 OTPs costs ₹8,000. The same volume via WhatsApp, even assuming full conversation windows, would cost significantly more.</p>
<p>For conversational use cases — customer support, sales qualification, post-purchase follow-up — WhatsApp&#39;s per-conversation model is often more economical than per-message SMS, because a single 24-hour WhatsApp conversation window can include many back-and-forth messages for one conversation fee.</p>
<h2 id="5-compliance-overhead" class="tn-h">5. Compliance Overhead<a class="tn-anchor" href="#5-compliance-overhead" aria-label="Link to this section">#</a></h2>
<h3 id="sms-compliance-trai-dlt" class="tn-h">SMS compliance: TRAI DLT<a class="tn-anchor" href="#sms-compliance-trai-dlt" aria-label="Link to this section">#</a></h3>
<p>SMS in India requires TRAI DLT registration — entity, headers, and pre-approved templates. Initial setup takes 3–7 working days. Every new message type requires a new pre-approved template. The framework is prescriptive but stable and well-documented.</p>
<p>Ongoing compliance: maintain templates, re-verify entity annually, pass Template IDs with every API call. The compliance overhead is moderate and largely automatable via your SMS provider.</p>
<h3 id="whatsapp-compliance-meta-bsp-framework" class="tn-h">WhatsApp compliance: Meta BSP framework<a class="tn-anchor" href="#whatsapp-compliance-meta-bsp-framework" aria-label="Link to this section">#</a></h3>
<p>To use WhatsApp Business API, your business must be verified by Meta and connect through an official Business Solution Provider (BSP) like TextNation. The onboarding process involves:</p>
<ul>
<li>Facebook Business Manager account setup and business verification</li>
<li>WhatsApp Business Account (WABA) creation</li>
<li>Phone number registration and verification</li>
<li>Message template creation and Meta approval (usually 24–72 hours)</li>
<li>Quality rating management: your templates are rated based on recipient feedback</li>
</ul>
<p>WhatsApp&#39;s compliance framework is more dynamic than DLT. Meta can change template categories, pricing, and approval criteria with relatively short notice. Template quality ratings affect your sending limits — poor-quality templates can throttle your account. This requires active monitoring that SMS does not.</p>
<h2 id="6-use-case-decision-matrix" class="tn-h">6. Use Case Decision Matrix<a class="tn-anchor" href="#6-use-case-decision-matrix" aria-label="Link to this section">#</a></h2>
<p>Use this matrix to choose the right channel for your specific use case:</p>
<div class="tn-table"><table>
<thead>
<tr>
<th>Use Case</th>
<th>Best Channel</th>
<th>Reason</th>
</tr>
</thead>
<tbody><tr>
<td>OTP / 2FA</td>
<td>SMS</td>
<td>100% device reach, sub-second delivery, lowest cost, DND-exempt</td>
</tr>
<tr>
<td>Bank alerts &amp; transaction notifications</td>
<td>SMS</td>
<td>Speed, reach, low cost at high volume, DND-exempt</td>
</tr>
<tr>
<td>Delivery tracking updates</td>
<td>WhatsApp (with SMS fallback)</td>
<td>Rich status cards, location sharing, better CX</td>
</tr>
<tr>
<td>Promotional campaigns</td>
<td>WhatsApp</td>
<td>Higher CTR, richer media, no DND blocking for opted-in users</td>
</tr>
<tr>
<td>Customer support</td>
<td>WhatsApp</td>
<td>Two-way conversation, chatbot integration, file sharing</td>
</tr>
<tr>
<td>Appointment reminders</td>
<td>WhatsApp or SMS</td>
<td>WhatsApp for button-based confirmations; SMS for lower-cost broad reach</td>
</tr>
<tr>
<td>Payment collection / invoices</td>
<td>WhatsApp</td>
<td>PDF attachments, payment CTA buttons, higher conversion</td>
</tr>
<tr>
<td>Re-engagement / win-back</td>
<td>WhatsApp</td>
<td>Rich media, personalisation, interactive elements</td>
</tr>
<tr>
<td>Emergency alerts / critical notices</td>
<td>SMS</td>
<td>Guaranteed delivery, no app required, works without data</td>
</tr>
</tbody></table></div>
<h2 id="the-omnichannel-answer-use-both" class="tn-h">The Omnichannel Answer: Use Both<a class="tn-anchor" href="#the-omnichannel-answer-use-both" aria-label="Link to this section">#</a></h2>
<p>The most effective enterprise messaging strategies in India do not choose one channel — they orchestrate both. The pattern that consistently delivers the best results:</p>
<ol>
<li><strong>Transactional triggers → SMS.</strong> — OTPs, alerts, and confirmations go via SMS for speed and reach. Cost is minimised at high volume.</li>
<li><strong>Engagement campaigns → WhatsApp.</strong> — Marketing, re-engagement, and conversion flows go via WhatsApp for richer interactions and higher CTR among opted-in users.</li>
<li><strong>WhatsApp with SMS fallback.</strong> — For messages where delivery matters above all (payment reminders, appointment confirmations), attempt WhatsApp first and fall back to SMS automatically if undelivered within a set window.</li>
<li><strong>Measure and optimise.</strong> — Track delivery rates, open rates, CTR, and conversion per channel per campaign type. Let data drive channel allocation over time.</li>
</ol>
<p>TextNation&#39;s unified API lets you manage SMS and WhatsApp from a single integration, with fallback logic, unified delivery reporting, and campaign analytics across both channels — eliminating the need to maintain separate vendor relationships.</p>
]]></content:encoded>
    </item>
    <item>
      <title>TRAI DLT Registration Guide for Enterprise SMS India 2026</title>
      <link>https://textnation.in/blog/trai-dlt-registration-guide-india-2026/</link>
      <guid isPermaLink="true">https://textnation.in/blog/trai-dlt-registration-guide-india-2026/</guid>
      <pubDate>Fri, 01 May 2026 04:30:00 GMT</pubDate>
      <dc:creator>TextNation Product Team</dc:creator>
      <category>Compliance</category>
      <description>Complete step-by-step guide to TRAI DLT registration for enterprise SMS in India. Entity registration, header submission, template pre-approval, and how to…</description>
      <content:encoded><![CDATA[<p>If you send commercial SMS messages to Indian phone numbers, TRAI&#39;s Distributed Ledger Technology (DLT) registration is not optional. Every message — whether a bank OTP, an e-commerce delivery alert, or a promotional campaign — must originate from a TRAI-approved entity, travel through a registered sender ID (header), and match a pre-approved message template. Violations result in immediate message blocking, operator penalties, and potential regulatory action.</p>
<p>This guide covers every step of the DLT registration process as of 2026, including updated portal workflows, common rejection patterns, and how to get your SMS campaigns live without delays.</p>
<h2 id="what-is-trai-dlt-and-why-it-exists" class="tn-h">What Is TRAI DLT and Why It Exists<a class="tn-anchor" href="#what-is-trai-dlt-and-why-it-exists" aria-label="Link to this section">#</a></h2>
<p>The Telecom Regulatory Authority of India introduced the DLT framework in 2018 under its Telecom Commercial Communications Customer Preference Regulations (TCCCPR). The mandate became enforceable for all commercial entities in November 2020.</p>
<p>DLT uses a blockchain-based distributed ledger maintained by Telecom Service Providers (TSPs) — Airtel, Jio, BSNL, and Vi — to record every Principal Entity (business sending SMS), every registered sender ID (header), and every approved message template. When your SMS gateway submits a message, the TSP checks the DLT ledger in real time. If any element — entity, header, or template — is not registered, the message is rejected before it reaches the subscriber.</p>
<p>The goal: eliminate unsolicited commercial communications and spam, give subscribers verifiable information about who is messaging them, and create an auditable chain of responsibility for every commercial message sent in India.</p>
<h2 id="before-you-register-prerequisites" class="tn-h">Before You Register: Prerequisites<a class="tn-anchor" href="#before-you-register-prerequisites" aria-label="Link to this section">#</a></h2>
<p>Gather the following before starting the DLT registration process. Incomplete documents are the single biggest cause of entity registration rejection.</p>
<ul>
<li><strong>PAN Card of the business</strong> — Active PAN issued to the entity (company, LLP, partnership, or proprietorship) sending SMS. Individual PANs are accepted only for sole proprietors.</li>
<li><strong>GST Registration Certificate</strong> — Must match the legal name under which you intend to register. If your GST is under a trade name that differs from the legal entity name, prepare an explanation letter.</li>
<li><strong>Certificate of Incorporation or Business Registration</strong> — For companies: MCA Certificate of Incorporation. For LLPs: LLP Agreement. For proprietorships: Shop &amp; Establishment certificate or equivalent.</li>
<li><strong>Authorised Signatory Details</strong> — Name, designation, mobile number, and email of the person who will be the entity&#39;s DLT account holder. This mobile number must be reachable for OTP verification.</li>
<li><strong>Brand Name / Trade Name</strong> — The name you want to appear as your sender ID prefix. This must match your registered business or trademark. Mismatches are rejected.</li>
</ul>
<h2 id="step-1-choose-your-dlt-portal" class="tn-h">Step 1 — Choose Your DLT Portal<a class="tn-anchor" href="#step-1-choose-your-dlt-portal" aria-label="Link to this section">#</a></h2>
<p>Each major TSP operates its own DLT portal. Registration on any one portal gives you a Universal Entity ID that is accepted across all operators. You do not need to register separately on every portal.</p>
<div class="tn-table"><table>
<thead>
<tr>
<th>Operator</th>
<th>Portal Name</th>
<th>Notes</th>
</tr>
</thead>
<tbody><tr>
<td>Airtel</td>
<td>Airtel DLT (airtel.in/dlt)</td>
<td>Widest industry adoption; recommended for enterprises already on Airtel Business</td>
</tr>
<tr>
<td>Jio</td>
<td>Jio Trueconnect (trueconnect.jio.com)</td>
<td>Faster template approval turnaround in 2025–26</td>
</tr>
<tr>
<td>BSNL</td>
<td>BSNL SMS (smsc.bsnl.co.in)</td>
<td>Government entities often register here first</td>
</tr>
<tr>
<td>Vi (Vodafone Idea)</td>
<td>Vi Business DLT (vilive.in)</td>
<td>Suitable if existing Vi business account holder</td>
</tr>
</tbody></table></div>
<h2 id="step-2-entity-registration" class="tn-h">Step 2 — Entity Registration<a class="tn-anchor" href="#step-2-entity-registration" aria-label="Link to this section">#</a></h2>
<p>Entity registration creates your Principal Entity (PE) record on the DLT blockchain. This is your business identity for all commercial SMS in India.</p>
<ol>
<li><strong>Create an account</strong> — On the chosen portal, select &quot;Register as Principal Entity.&quot; Enter your authorised signatory&#39;s mobile number. You will receive an OTP to verify the number.</li>
<li><strong>Enter business details</strong> — Fill in Legal Name (exactly as on PAN), PAN number, GSTIN, registered address, and business category. Select the correct category — &quot;Bank/NBFC,&quot; &quot;Healthcare,&quot; &quot;E-Commerce,&quot; &quot;Education,&quot; &quot;Government,&quot; etc. Category determines the template types you can register later.</li>
<li><strong>Upload documents</strong> — Upload PAN card (PDF/JPG, max 2MB), GST certificate, and incorporation/registration document. File names should be descriptive (e.g., &quot;PAN_TextNation.pdf&quot;) — portals sometimes reject files with special characters in names.</li>
<li><strong>Accept T&amp;C and submit</strong> — Review the terms and submit. You will receive an acknowledgement email with a reference number. Keep this — it is required if you need to follow up.</li>
<li><strong>Verification and approval</strong> — The TSP verifies documents within 1–3 working days. On approval, you receive your Universal Entity ID (a 19-digit alphanumeric string). This ID is your DLT identity across all TSPs.</li>
</ol>
<h2 id="step-3-header-sender-id-registration" class="tn-h">Step 3 — Header (Sender ID) Registration<a class="tn-anchor" href="#step-3-header-sender-id-registration" aria-label="Link to this section">#</a></h2>
<p>A header is the sender name that appears on the recipient&#39;s phone. TRAI defines three types:</p>
<div class="tn-table"><table>
<thead>
<tr>
<th>Type</th>
<th>Format</th>
<th>Used for</th>
</tr>
</thead>
<tbody><tr>
<td>Transactional</td>
<td>6 letters (e.g., TXTNTN)</td>
<td>OTPs, bank alerts, order confirmations, service updates triggered by user action. Can be sent to DND numbers.</td>
</tr>
<tr>
<td>Promotional</td>
<td>6 digits (e.g., 560012)</td>
<td>Marketing, offers, announcements. Cannot be sent to DND-registered numbers. Time-restricted (9am–9pm).</td>
</tr>
<tr>
<td>Service (Implicit)</td>
<td>6 letters (e.g., TXTNTS)</td>
<td>Service messages not triggered by a transaction (e.g., appointment reminders, renewal notices). DND rules vary.</td>
</tr>
</tbody></table></div>
<p>To register a header, navigate to the &quot;Headers&quot; or &quot;Sender IDs&quot; section of your DLT portal. Enter your desired 6-character string, select the header type, link it to your registered entity, and submit. Header approval typically takes 24–48 hours.</p>
<p>You can register multiple headers under a single entity (e.g., separate headers for OTP, alerts, and promotions). Most enterprises register 3–5 headers to segment message types cleanly.</p>
<h2 id="step-4-template-registration-and-pre-approval" class="tn-h">Step 4 — Template Registration and Pre-Approval<a class="tn-anchor" href="#step-4-template-registration-and-pre-approval" aria-label="Link to this section">#</a></h2>
<p>Every message body must match a pre-approved template. Templates define the fixed and variable parts of your messages.</p>
<h3 id="template-types-and-variable-rules" class="tn-h">Template types and variable rules<a class="tn-anchor" href="#template-types-and-variable-rules" aria-label="Link to this section">#</a></h3>
<p>DLT templates use a <code>{#var#}</code> placeholder syntax for variable content. Key rules:</p>
<ul>
<li>Each variable is represented as <code>{#var#}</code> in the template text.</li>
<li>You cannot have two consecutive variables without fixed text between them.</li>
<li>The fixed portion of the template must make up the majority of the message content.</li>
<li>OTP/PIN values count as variables and must use the <code>{#var#}</code> placeholder.</li>
<li>URLs in templates must be either hardcoded or from a TRAI-whitelisted URL shortener.</li>
<li>Promotional templates cannot include phone numbers or URLs that redirect to non-branded pages.</li>
</ul>
<h3 id="example-otp-template" class="tn-h">Example: OTP template<a class="tn-anchor" href="#example-otp-template" aria-label="Link to this section">#</a></h3>
<pre><code>// Approved template (Transactional, Header: TXTNTN)
Your TextNation verification code is {#var#}. Valid for 10 minutes. Do not share with anyone. — TextNation
</code></pre>
<h3 id="submitting-templates" class="tn-h">Submitting templates<a class="tn-anchor" href="#submitting-templates" aria-label="Link to this section">#</a></h3>
<ol>
<li>In the DLT portal, go to &quot;Templates&quot; → &quot;Register New Template.&quot;</li>
<li>Select the template type (Transactional / Promotional / Service).</li>
<li>Select the header this template will be sent from.</li>
<li>Enter the template content using <code>{#var#}</code> for each variable.</li>
<li>Provide a brief description of the template purpose (e.g., &quot;OTP for login verification&quot;).</li>
<li>Submit. Approval typically takes 24–72 hours.</li>
<li>Once approved, you receive a Template ID. This ID must be passed with every API call to your SMS provider.</li>
</ol>
<h2 id="common-rejection-reasons-and-how-to-avoid-them" class="tn-h">Common Rejection Reasons and How to Avoid Them<a class="tn-anchor" href="#common-rejection-reasons-and-how-to-avoid-them" aria-label="Link to this section">#</a></h2>
<ul>
<li><strong>Entity name mismatch</strong> <em>(very common)</em> — The business name on PAN does not exactly match what was entered in the registration form. Solution: copy the name letter-for-letter from your PAN card.</li>
<li><strong>Two consecutive variables in a template</strong> <em>(very common)</em> — e.g., &quot;Your order {#var#} {#var#} has shipped&quot; is rejected. Fix: &quot;Your order {#var#}, quantity {#var#}, has shipped.&quot;</li>
<li><strong>Template content too short</strong> <em>(common)</em> — Very short messages (under 15 characters of fixed text) are frequently rejected for not meeting the fixed-content threshold.</li>
<li><strong>Wrong template type for a header</strong> <em>(common)</em> — Submitting a promotional template against a transactional header. The header type and template type must match.</li>
<li><strong>Unregistered URL in promotional template</strong> <em>(common)</em> — URLs in promotional templates must be from TRAI-whitelisted domains or registered URL shorteners. Bare domain links to external sites are rejected.</li>
<li><strong>Document quality issues</strong> <em>(moderate)</em> — Blurred or cropped PDFs, password-protected files, or files exceeding the 2MB portal limit cause entity registration failures.</li>
</ul>
<h2 id="timelines-and-what-to-expect-after-registration" class="tn-h">Timelines and What to Expect After Registration<a class="tn-anchor" href="#timelines-and-what-to-expect-after-registration" aria-label="Link to this section">#</a></h2>
<div class="tn-table"><table>
<thead>
<tr>
<th>Step</th>
<th>Typical Timeline</th>
</tr>
</thead>
<tbody><tr>
<td>Entity registration approval</td>
<td>1–3 working days</td>
</tr>
<tr>
<td>Header registration approval</td>
<td>24–48 hours</td>
</tr>
<tr>
<td>Template approval</td>
<td>24–72 hours</td>
</tr>
<tr>
<td>Entity re-verification (annual)</td>
<td>Required once per year; same timeline</td>
</tr>
</tbody></table></div>
<p>Once all three elements are registered and approved, you are ready to send. Your SMS provider (like TextNation) will need your Entity ID, Header, and Template ID for each message submission. These are passed in the API request so the gateway can include them in the DLT chain.</p>
<p>DLT entities must re-verify annually. You will receive an email reminder from the TSP portal 30 days before expiry. Failure to re-verify results in suspension of all registered headers and templates.</p>
<h2 id="how-textnation-simplifies-dlt-compliance" class="tn-h">How TextNation Simplifies DLT Compliance<a class="tn-anchor" href="#how-textnation-simplifies-dlt-compliance" aria-label="Link to this section">#</a></h2>
<p>Managing DLT registration, tracking template IDs, and passing the right DLT parameters with every API call adds overhead to your engineering and operations teams. TextNation&#39;s enterprise SMS platform handles this transparently:</p>
<ul>
<li><strong>Dedicated DLT onboarding support — our compliance team guides you through entity, header, and template registration on your preferred TSP portal.</strong></li>
<li><strong>Template ID management — store all approved template IDs in your TextNation dashboard and reference them by name in API calls.</strong></li>
<li><strong>Automatic DLT parameter injection — the API handles Entity ID and Template ID fields so your application code stays clean.</strong></li>
<li><strong>DND filtering applied automatically — promotional messages are filtered against the NDNC/DND registry before dispatch.</strong></li>
<li><strong>Annual re-verification reminders — we flag expiring registrations 45 days in advance.</strong></li>
</ul>
]]></content:encoded>
    </item>
  </channel>
</rss>
