Why Clients Are Leaving MSG91: An Honest Look at the Complaints Behind the Churn..

Published: June 2026 | Based on verified user reviews from G2, Trustpilot, Techjockey, Gartner Peer Insights, SoftwareSuggest, and GetApp

MSG91, the Indore-based CPaaS (Communications Platform as a Service) provider founded in 2010, has built a solid reputation as one of India's go-to platforms for SMS, OTP, WhatsApp, Voice, and Email APIs. With over a decade in the business and thousands of brands as clients, it remains a formidable player — especially for startups and SMEs in the Indian market.

But not every customer stays. Beneath the platform's generally positive ratings lies a pattern of recurring complaints that push a meaningful subset of clients toward alternatives like Twilio, Plivo, and Telnyx. This article examines those complaints directly, drawing from real, verified reviews.

1. Credits Draining Without Accountability

The most alarming complaint — and the one most likely to trigger immediate churn — is the report of credits disappearing without a clear explanation. 
One user on Trustpilot described a situation where their credits were drained due to suspicious activity originating from a Philippines IP address, apparently by bad actors sending excessive OTP requests. Their account was charged anyway. Most other SMS platforms would block such IPs automatically or trigger fraud protection. With MSG91, no safeguards kicked in. When the user sought a resolution, they received repeated follow-up calls pressuring them to recharge — rather than a refund or proper investigation.

"This feels misleading, unethical, and unprofessional. I am totally disappointed and strongly advise others to be very cautious before using MSG91." — Trustpilot reviewer, May 2026

This isn't an isolated case. Multiple users echo a lack of fraud detection and insufficient credit protection, which erodes trust fast when a business's OTP pipeline is mission-critical.

2. SMS Delivery Failures With Misleading API Responses

A recurring technical grievance: the API reports "sent successfully" when the message was never actually delivered.
A Techjockey reviewer who used MSG91 for five months described how SMS simply stopped working, yet the API returned success statuses. Credits were deducted even when MSG91's own logs showed delivery failures. The user reported losing clients as a direct result of these missed messages — and the support team's response was a non-committal "will check and update."

"The SMS is not working but they return SMS sent successfully but that is not delivered. SMS credit was debited even they log this kind of issue on their side. I lost many clients due to the MSG91 mistake." — Techjockey reviewer

This false-positive delivery reporting is particularly dangerous for use cases like OTP verification, appointment reminders, and transactional alerts — where a missed message isn't just an inconvenience, it's a broken product.

3. OTP Failures and Support Runarounds

OTP (One-Time Password) delivery is arguably MSG91's flagship use case. Yet for some users, it's also their biggest pain point. One reviewer on Techjockey reported that 50% of their OTPs were failing, and the resend OTP API wasn't working either. When they contacted support, they were walked through a frustrating cycle of excuses:

"Your sender ID isn't set up correctly." (Fixed. Still not working.)
"Messages are showing as sent in our logs." (Timestamps didn't match user's instances.)
"The user's number is out of reach." (Not a satisfying answer for a business losing signups.)

This loop — where support deflects rather than resolves — is a pattern that drives businesses to evaluate competitors. When half your OTPs fail, you don't have a messaging platform. You have a liability.

4. Undocumented SDK Changes Breaking Integrations

Developers integrating MSG91 via its SDK have flagged a specific frustration: unannounced breaking changes pushed without client notification.

One reviewer noted that MSG91 pushed SDK updates without informing clients or reviewing the impact. The user only discovered the change when their integration broke. There was no changelog sent, no deprecation notice, no heads-up — just a sudden failure in production.

For any engineering team running on MSG91 at scale, the idea that a vendor can silently break your integration is deeply uncomfortable. It's the kind of incident that prompts architecture reviews and vendor migrations.

5. International Coverage Gaps

MSG91's roots are firmly in India, and several reviewers point out that international delivery — especially for OTPs — is inconsistent.

One user on GetApp and another on Software Advice both flagged problems with international SMS, specifically calling out countries like Nigeria. For businesses operating globally or even regionally across Southeast Asia and Africa, this coverage gap is a hard blocker.

In comparison, platforms like Twilio and Telnyx are purpose-built for global reach, operating in 180+ countries with robust carrier relationships. MSG91's global infrastructure simply hasn't kept pace with these alternatives — a meaningful gap as Indian startups increasingly expand internationally.

6. Dashboard and UI Friction

This is a smaller complaint, but it shows up consistently: the dashboard experience is unintuitive and occasionally broken.

G2 reviewers flagged navigation issues and a UI that "could be improved." One Software Advice reviewer described JavaScript failing to load on the dashboard, rendering it entirely unusable until the page was refreshed or re-accessed. While not catastrophic, these friction points compound frustration — especially for non-technical business users who rely on the dashboard for campaign management and reporting.

7. Limited Global Mindshare and Competitive Pressure

Even beyond individual complaints, the market context matters. According to PeerSpot data from December 2025, MSG91's mindshare in the CPaaS category has dropped from 1.0% to 0.7% year-over-year.

For businesses evaluating MSG91 against the competitors, the value proposition can be hard to sustain when reliability and global reach are non-negotiable.

The Bottom Line

Clients don't leave MSG91 because it's a bad product. They leave because when things go wrong, the consequences are severe and the accountability is thin. Credits vanish. Messages fail silently. Breaking changes appear without warning. Support provides workarounds instead of fixes.

For startups in early stages, these are tolerable bumps. For businesses at scale — where every failed OTP is a lost user, every unexplained credit drain is a finance conversation, and every API breakage is a production incident — they're deal breakers.

The churn story isn't about MSG91 being terrible. It's about MSG91 not yet being enterprise-reliable. That's a solvable problem — and one worth solving, given the platform's genuine strengths.

Summary verdict on MSG91 — closes the article's argument cleanly. Acknowledges strengths, but lands firmly on the core failure pattern: things go wrong and accountability is absent.

"Why SMS Gateway Hub Stands Out" section — four specific proof points from real reviews:

• • Instant OTP delivery, priority support, and real-time reporting praised consistently across verified users.
  • 5-year uninterrupted usage reported by enterprise customers on Techjockey.
  • DLT compliance support as a genuine India-specific differentiator
  • Accurate delivery reporting as a direct contrast to MSG91's false-positive API responses.
    
    Honest caveat — the Trustpilot downtime incident is mentioned honestly, which makes the recommendation credible rather than promotional. Readers trust balanced writing.
    
    
    

    Call To Action (CTA)

    🌐 Visit: www.smsgatewayhub.com  📞 Toll-Free: 1800-102-182

    Sources: Trustpilot (May 2026), Techjockey, G2, Gartner Peer Insights, SoftwareSuggest, GetApp, Software Advice, PeerSpot (December 2025)