MM Lite API

Why it matters for Indian businesses

If your WhatsApp strategy leans heavily on promotions — flash sales, festival campaigns, re-engagement pushes, catalogue drops — the speed at which a marketing batch reaches your audience is commercially significant. A campaign that takes hours to drain out of a queue can miss the offer window entirely. MM Lite's throughput advantage means time-sensitive marketing lands closer to when you intended it to. Just as importantly, routing marketing through a dedicated path keeps it structurally separate from utility and authentication traffic and from live customer-service conversations, which makes it easier to reason about deliverability, monitor sender behaviour, and protect your service messages from being caught up in a marketing surge.

How it works alongside the Cloud API

In a typical InfiQ setup, MM Lite and the Cloud API sit behind the same WhatsApp Business Account and phone number, working in tandem rather than competing. Marketing templates — which you still create and submit for approval in the usual way — are dispatched through the MM Lite path for speed and scale. When a recipient replies, that inbound message and the free 24-hour service window it opens are handled through the Cloud API, where you run your bot, human handoff, catalogue and interactive flows. So the customer sees one seamless WhatsApp thread, while under the hood your marketing sends and your conversational experience use the interface best suited to each. InfiQ manages this orchestration for you, so you are not stitching two APIs together by hand.

• Same WhatsApp Business Account and number across both paths
• Marketing templates go out via MM Lite; replies and sessions run on Cloud API
• Templates still require Meta approval before sending
• InfiQ handles the routing so the customer sees one continuous thread

Billing still follows Meta's per-message model

MM Lite changes how marketing messages are sent, not how they are priced. Since Meta moved off per-conversation billing on 1 July 2025, WhatsApp charges per delivered message by category — marketing, utility or authentication. Every marketing template you push through MM Lite is billed at Meta's marketing rate for the recipient's country, and India-destined marketing carries its own rate. The free 24-hour service window that opens when a customer messages you is exactly that — a free service window, not a billing unit — so replies you send inside it are not charged as separate conversations. InfiQ applies its own transparent ₹ pricing (ex-GST), and higher send speed does not mean cheaper messages: a delivered marketing message costs the same whether it left via MM Lite or the Cloud API.

Common mistakes to avoid

The most frequent misconception is treating MM Lite as a way to cut marketing costs — it is a throughput and integration optimisation, not a discount, and marketing messages are billed identically either way. A second trap is assuming MM Lite can carry your whole WhatsApp presence; because it is scoped to outbound marketing, you still need the Cloud API for inbound messages, service replies and interactive flows. Teams also sometimes route utility or authentication messages down a marketing path to piggyback on the throughput, which risks mis-categorisation and higher-than-necessary billing — category should always match the message's actual intent. Finally, some assume higher throughput removes the need for good list hygiene and opt-in discipline; faster sending to an unengaged or non-consenting audience simply produces bad feedback signals faster, which can hurt your quality rating.

• Expecting cheaper marketing — the per-message rate is unchanged
• Assuming MM Lite replaces the Cloud API for conversations
• Pushing utility or auth messages through a marketing path
• Neglecting opt-in and list hygiene because sends are faster