Other Industry compliance

India Expands Short-Term Voice-and-SMS-Only Plans

For businesses distributing Indian mobile plans, operating recharge services, or supporting account verification, expanded voice-and-SMS-only options affect product catalogs and customer guidance. On September 21, 2026, TRAI released its Thirteenth Amendment to the telecom consumer protection framework, requiring operators to offer additional short-duration, calendar-month, and longer-validity recharge options without bundled data. The change concerns consumer recharge products, not enterprise A2P wholesale messaging prices; distribution teams should therefore review plan availability separately from their messaging procurement and verification workflows. ([trai.gov.in](https://www.trai.gov.in/sites/default/files/2026-09/PR_No120of2026.pdf))

Published:11/04/2026 Updated:11/04/2026

1. Regulatory focus

The amendment changes operators’ Special Tariff Voucher offerings: each validity period of 30 days or less available for a voice, SMS, and data bundle must have a corresponding voice-and-SMS-only option with an appropriate tariff reduction. Operators must also offer calendar-month renewal, using the final day when the corresponding renewal date does not exist, plus at least one longer-validity option corresponding to a bundled offering. These requirements concern the availability and duration of consumer recharge products; they should not be presented to enterprise customers as a mandatory reduction in A2P SMS gateway or termination charges. ([gazettetracker.com](https://gazettetracker.com/g/CG-DL-E-30092026-276645))

2. Business impact

TRAI identified limited availability of voice-and-SMS-only vouchers, concentrated in longer validity periods, as the problem behind the amendment. ([trai.gov.in](https://www.trai.gov.in/sites/default/files/2026-09/PR_No120of2026.pdf)) Our operational recommendation is for recharge platforms and distributors to check whether their catalogs still expose only long-duration options, with validity, SMS allowances, and data entitlements stored as separate product attributes rather than inferred from a plan name. Account-verification teams can add a no-mobile-data scenario to their test matrix, but should not treat the amendment as evidence that OTP delivery, inactive-number handling, number retention, or incoming-message eligibility has changed; those questions require separate operator confirmation.

3. Operating recommendations

Build an operator-by-operator comparison table containing bundled-plan validity, the corresponding voice-and-SMS-only product, price, SMS allowance, and listing date, then validate short-duration, calendar-month, and longer-validity options separately. Add month-end test cases and keep 28-day rolling validity distinct from renewal on the same calendar date each month, rather than treating both as a generic monthly product. For support scripts, require operator confirmation before promising automatic payment, indefinite OTP reception, or service continuity after expiry, and retain the underlying product terms with each catalog update. These are implementation checks proposed for distributors and product teams, not additional statutory reporting obligations.

Frequently Asked Questions

Our catalog already includes a long-validity voice-and-SMS plan. What else should we check?
Do not treat one long-validity product as a complete coverage check. Obtain the operator’s current bundled-voucher inventory and match every validity period of 30 days or less to its voice-and-SMS-only counterpart, then check calendar-month and longer-validity options separately. Record product identifiers and review dates, and ask the supplier to explain any apparent gaps before updating customer-facing claims. ([trai.gov.in](https://www.trai.gov.in/sites/default/files/2026-09/PR_No120of2026.pdf))
Should every user on a data-free plan be switched to SMS verification?
No blanket migration is recommended. Test login journeys with mobile data disabled, Wi-Fi available, and no internet connection, checking whether the user can actually view, enter, and complete verification with the code. Base channel selection on user preference and observed availability, and apply resend cooldowns and request-level deduplication rather than triggering several channels for the same verification attempt.
Can support promise indefinite number retention and OTP reception with these plans?
Do not make that promise. Ask the operator to confirm plan validity, number-retention terms, incoming-SMS conditions, any grace period, and restoration steps as separate items. Update the support knowledge base only after receiving documented answers, and limit customer-facing statements to verified entitlements instead of presenting the new product-availability requirements as a guarantee of permanent number retention or OTP reception.
This article is for informational purposes only and does not constitute legal advice.

Need compliance guidance?

Contact us for guidance on target markets, message scenarios, and sending routes.

Get in Touch
Privacy Policy