What the MSG91 Startup Program Gives You
MSG91, the Indore-headquartered communications platform, offers $1,500 in startup credits toward its messaging stack: transactional SMS, OTP verification, WhatsApp Business messaging, email, voice and RCS, all drawn from a single balance.
AI Perks tracks it in the Communications category alongside $7.7M in credits across 194 companies.
$1,500 reads small next to a cloud grant and behaves nothing like one. Messaging is metered per message, not per hour of compute, so the balance does not evaporate the week your servers get busy. It converts into a message count, and for an India-focused product that count runs well into six figures.
The boundary matters. The credit covers MSG91 traffic. Sender registration, regulator-side fees and whatever Meta charges directly for WhatsApp templates behave as their own line items. Program scope and eligibility depend on stage and funding, listed on getaiperks.com.
What a Messaging API Is Actually For
A communications platform solves one problem that is invisible from its feature list: getting a message onto a handset in a country where you hold no carrier relationship. The dashboards, templates and analytics are packaging around routing agreements and regulatory registrations you cannot obtain alone.
Sending an SMS is one HTTP call. Having it arrive in four seconds, on an Indian mobile network, at 2am, in the middle of a signup, is a supply chain: aggregator routes, operator scrubbing, sender ID registration, template approval, delivery receipts and a fallback for when one link fails.
Two kinds of traffic hide behind the same API, and confusing them is expensive:
- Transactional and OTP traffic is triggered by a user action: login codes, payment confirmations, delivery updates. Latency is the metric. A failure is a user locked out of your product.
- Promotional traffic is initiated by you. Consent is the metric, and in India it runs through the national DND registry with time-window restrictions and separate operator routes.
OTP deserves the attention, because it is the most load-bearing message most startups ever send. It sits at the exact point in the funnel where acquisition spend has already been paid and revenue has not yet started. If 4 percent of codes fail to arrive, you lose 4 percent of every signup cohort at the most expensive place available to lose them.
How Messaging Costs Behave at Scale
Messaging bills scale with users multiplied by messages per user, and the unit price swings by more than a factor of ten depending only on which country the phone number sits in.
A cloud bill grows when your product gets busy. A messaging bill grows when your product gets popular somewhere expensive. Those are different risks, and only one of them is fixed by better engineering.
| Channel | What you are billed for | What makes the bill grow |
|---|---|---|
| Domestic SMS (India) | Each message segment, per recipient | Signups, retries, message length |
| International SMS | Each segment, priced per destination country | Where users are, not only how many |
| WhatsApp Business | Meta's template rates by category and country, plus platform fees | Marketing volume, country mix |
| Each email sent | Send frequency and list size | |
| Voice OTP | Per call, billed in pulses or minutes | Fallback rate on failed SMS |
| RCS | Per message, subject to device and carrier support | Handset mix, reach |
WhatsApp billing keeps changing shape, having moved from 24-hour conversation windows toward per-template-message pricing with separate marketing, utility and authentication categories. Verify current rates against live pricing, not against any article, this one included.
Then there is the cost multiplier almost nobody models: encoding.
| Message content | Encoding | Characters per segment | Segments for a 150-character message |
|---|---|---|---|
| Plain Latin text | GSM-7 | 160 (153 concatenated) | 1 |
| One emoji anywhere in the body | UCS-2 | 70 (67 concatenated) | 3 |
| Hindi, Tamil or other non-Latin script | UCS-2 | 70 (67 concatenated) | 3 |
| Curly apostrophe pasted from a doc | UCS-2 | 70 (67 concatenated) | 3 |
One character copied out of a design document can triple the price of every message you send. Vernacular messaging carries the same arithmetic by design: reaching regional-language users costs roughly three times per message, which belongs in the model rather than on invoice three.
What MSG91 Credits Stack With
Messaging credits stack cleanly because the bill touches almost nothing else. MSG91 charges for messages leaving the building, and every neighbouring system that triggers those messages has a startup program of its own.
- Cloud credits cover the application and database firing the sends
- Auth and identity credits cover the login layer requesting the code
- Data and analytics credits cover the warehouse where delivery rates get joined to activation
- Model and API credits cover anything writing, translating or routing the message copy
The overlap trap is worth naming. Auth providers, support desks and CRMs increasingly bundle their own SMS sending at per-message rates that are usually worse than a dedicated platform. Stacking an identity grant on a messaging grant can quietly route the same OTP down the more expensive pipe. Which programs complement each other and which duplicate is why AI Perks is maintained as a list, not a folder of bookmarks.
What Founders Get Wrong About Messaging Credits
The most expensive mistake is an unauthenticated endpoint that can trigger an SMS. Free balance plus an open send path is exactly the setup that SMS pumping fraud exists to drain.
Ignoring SMS pumping. Also called artificially inflated traffic: an attacker scripts your signup form against numbers on routes they profit from, and your balance funds it. Rate limit per number and per IP, block destinations you do not serve, and put a challenge in front of the send. A grant makes this worse, because nobody watches a spend anomaly on money they did not pay for.
Treating a delivery receipt as proof of arrival. A receipt says a carrier accepted the message. Handset delivery, filtering and the user actually reading the code are separate events. Count completed verifications, not messages sent.
Underestimating the registration layer. India requires DLT registration of the entity, header and templates before transactional SMS flows. The United States requires A2P 10DLC or toll-free verification, and several markets pre-register alphanumeric sender IDs. This is paperwork with lead times in days or weeks, and free credit shortens none of it.
Budgeting OTP as marketing spend. Verification is a cost of acquisition. The metric is cost per successful verification, which includes retries, voice fallback and the users who never finished.
Threading the vendor SDK through the codebase. Message content and templates are portable. Fifty call sites importing a provider client are not. One thin send interface now is a config change later.
Spending the balance on blasts. Messaging grants are commonly scoped to transactional traffic rather than promotional campaigns, and what any given program actually covers is listed on getaiperks.com.
How to Make a $1,500 Messaging Credit Go Further
The grant size is fixed. How many delivered messages it converts into is decided by template encoding, retry logic and fraud controls, all set in the first fortnight, before real volume exists.
Audit templates for encoding. Strip emoji and curly punctuation from Latin-script messages, and keep OTP copy inside one GSM-7 segment. An hour of work that can cut per-message cost by two thirds.
Build the fallback ladder in sequence, not in parallel. SMS first, then WhatsApp or voice after a timeout. Firing all three at once triples the cost to buy a few seconds.
Rate limit before launch, not after the first anomaly. Per number, per IP, per hour, with a hard daily ceiling and a balance alert.
Start the registration paperwork early. Headers and templates get approved on someone else's schedule, and the credit clock does not wait for them.
Instrument cost per successful verification from day one. It is the only number that says whether the balance is buying signups or buying messages.
Price the unsubsidised version at 70 percent consumed. MSG91 sits in the Communications category on getaiperks.com beside the email, support and CRM programs, and the cloud grant behind the app that fires your sends often matters more to the total than this one does.
Frequently Asked Questions
How much is the MSG91 startup program worth?
$1,500 in credits toward MSG91, usable across transactional SMS, OTP verification, WhatsApp Business messaging, email and voice from one balance. Because messaging is billed per message rather than per seat, the delivered message count depends on which countries your users are in. Current amounts are tracked at AI Perks.
What is MSG91 used for?
MSG91 is an Indian communications platform: an API layer for sending SMS, OTP codes, WhatsApp Business messages, email, voice and RCS without holding carrier relationships yourself. It is most often adopted for phone verification and transactional alerts aimed at Indian users, where domestic SMS rates are among the lowest anywhere.
Do I need DLT registration to use MSG91 in India?
Yes. India requires transactional senders to register the entity, the sender header and every message template through the DLT system before operators deliver the traffic. That requirement comes from the regulator rather than the vendor, so it applies whichever provider you choose. Begin it early, because approval runs on someone else's timetable.
Is MSG91 cheaper than Twilio?
For domestic Indian traffic, usually yes, and that is the main reason teams pick it. For a user base spread across North America and Europe the gap narrows, because cost is dominated by destination country rates rather than by the platform. Price your actual destination mix before committing either way.
Can I combine MSG91 credits with other startup credits?
Yes, and messaging credits stack well because the bills rarely overlap. Cloud credits cover the app triggering the sends, data credits cover the warehouse where delivery results land, and identity credits cover the login flow requesting the code. AI Perks tracks $7.7M in credits across 194 companies.
What happens when the MSG91 credits run out?
You inherit a bill shaped by choices made while it was free: template encoding, retry aggressiveness and how much bot traffic reached the send path. Fix those three first, then price your destination mix against alternatives at 70 percent consumed rather than after the first unsubsidised invoice.
Ship the signup flow. Let someone else fund the codes while you find out how many people finish it.