WhatsApp Cloud API and the Green Tick: A Business Owner's Guide to Going Official

What is the WhatsApp Cloud API, and how is it different from the app on your phone?

Most Indian business owners use WhatsApp every day without ever thinking about which WhatsApp they are using. But there are actually three separate products, and the difference decides what your business can and cannot do. Understanding the WhatsApp Cloud API is the first step to sending order updates, payment reminders and offers to hundreds or thousands of customers in a way that is reliable, professional and permitted by Meta.

The first is the personal WhatsApp app, the green one on your phone that you use to message family. Using it to run a business is against WhatsApp's terms, and heavy broadcasting from a personal number is the fastest way to get blocked.

The second is the WhatsApp Business app, a free download meant for a single small shop. It gives you a business profile, catalogue, quick replies and away messages. It is genuinely useful for a one-person operation, but it runs on one phone, one person can reply at a time, and you cannot connect it cleanly to your billing software, website or CRM.

The third is the WhatsApp Business Platform, and the WhatsApp Cloud API is how you connect to it. There is no app to install. Instead, your number is hosted on Meta's servers and connected to software, so many agents can reply from one number, and your systems can send messages automatically. This is the version built for businesses that have outgrown a single phone.

What does the green tick actually mean, and how is the verified badge granted?

The green tick, officially the green verified badge, is a small checkmark that appears next to your business name inside WhatsApp. It tells the customer that Meta has confirmed this is an authentic, notable brand and not an imposter. It builds instant trust, which matters when you are asking someone to click a payment link or trust an order confirmation.

The most important thing to understand is that the green tick is not something you buy, and it is not the same as being on the Cloud API. You can run a fully working Cloud API number, send templates and take orders, with no green tick at all. Plenty of successful businesses operate this way. The badge is a separate, discretionary approval from Meta.

Meta grants the green tick based on whether your brand is considered notable, which usually means it is written about in independent news coverage and has a real public presence, not just a website and social pages you control yourself. A small local shop with no press coverage will often be declined, and that is normal, not a failure on your part.

Before you can even apply, your Facebook Business Manager and your business phone number must be verified, and your display name must follow WhatsApp's naming rules. A partner or your software provider submits the request through the platform; you cannot email Meta directly to demand it.

Why can't you just type a message and blast it to everyone?

This is the part that surprises most owners. On the Cloud API you cannot freely type whatever you want and send it to a list of numbers. Meta protects users from spam by controlling business-initiated messages very tightly, and once you understand the logic, the rules make sense.

There are two situations. Inside a 24-hour customer service window, which opens the moment a customer messages you first, you can reply with any free-form text, images or documents you like. This window is for genuine two-way conversations and closes 24 hours after the customer's last message.

Outside that window, when you want to reach out first, for example to send an order update to someone who has not messaged you today, you must use a pre-approved message template. In the platform these are called HSMs, or Highly Structured Messages. You write the template once, submit it to Meta, and only after it is approved can you use it to message people.

Templates can include variables in curly braces, so a single approved template like an order-shipped notice can be personalised with each customer's name and tracking number. Meta reviews templates for spammy or misleading content, and approval is usually fast, often within minutes to a few hours, though it can be rejected if the wording looks promotional in a category meant for transactions.

This template system is exactly why the Cloud API is safe to scale on. Every proactive message has already passed a quality check.

What is opt-in, and why does it protect your business?

Meta requires that every person you message on the Cloud API has given you permission, called an opt-in. You must have clear evidence that the customer agreed to receive WhatsApp messages from your business. This is not optional bureaucracy; it is what keeps your number healthy and out of trouble.

An opt-in can be collected in many practical ways that fit an Indian business. The customer can tick a box at checkout on your website, fill in a form, reply with a keyword, or agree at the counter and be recorded in your system. The key is that they knowingly said yes to your brand contacting them on WhatsApp.

The opt-in must make three things obvious to the customer: that they will receive messages on WhatsApp, from your specific business name, and roughly what kind of messages, such as order updates or offers. Silently importing a list of numbers you scraped or bought is a violation and a fast route to being reported and banned.

There is a strong business reason to take this seriously beyond the rules. Messages sent to people who did not ask for them get blocked and reported, and those complaints directly lower your quality rating, which we cover below. Good opt-in practice is not just compliance; it is what keeps your delivery working.

How does WhatsApp Cloud API pricing work, and what will you actually pay?

WhatsApp does not charge you per message in the old SMS sense. Instead, the platform charges per conversation, and conversations are grouped into categories, each priced differently. Knowing the categories helps you predict your bill and choose the cheapest correct one for each message.

The four conversation categories are:

• Marketing: promotions, offers, product launches, festival campaigns and re-engagement. This is the most expensive category because it is the most intrusive.
• Utility: transactional messages tied to a specific action the customer took, such as order confirmations, shipping updates, payment receipts and appointment reminders. Cheaper than marketing.
• Authentication: one-time passwords and login codes. Priced separately and usually low.
• Service: your free-form replies to a customer inside the 24-hour window, when the customer messaged first.

Rates are set by Meta per country and are revised periodically, and India has its own price list, so treat any specific paisa figure you read online as approximate and confirm the current rate before you budget. As a broad guide, marketing conversations cost the most, utility and authentication cost noticeably less, and service conversations are the cheapest, sometimes effectively free within limits.

The practical lesson for cost control is simple: send the right category. Dressing up a genuine order update as a marketing message wastes money, and disguising a promotion as a utility template gets it rejected. On top of Meta's charge, your software partner will have its own platform fee, so ask for the all-in cost before you commit.

How do you send broadcasts at scale without getting your number banned?

The biggest fear owners have is spending money to set this up and then getting their number banned on day one. That fear is justified if you do it wrong, but the platform gives you clear guardrails, and following them keeps you safe. Two ideas matter most: number warming and quality rating.

A brand-new Cloud API number starts on a low messaging tier, typically allowing you to initiate conversations with a limited number of unique customers per day. As you send good messages that people accept and reply to, Meta automatically raises your tier, letting you reach more people. This ramp-up is called number warming: you start small, prove your messages are wanted, and grow into larger volumes rather than blasting thousands on day one.

Every number also carries a quality rating, shown as high, medium or low, driven mainly by how customers react. Blocks and reports push it down; replies and read messages hold it up. If your rating falls too far, Meta throttles or pauses your ability to send, so protecting the rating is protecting your whole channel.

The practical habits that keep you safe are straightforward:

• Only message people who opted in, and remove anyone who asks to stop, immediately.
• Warm the number gradually over days and weeks instead of importing your entire database at once.
• Lead with utility and useful content; do not open the relationship with aggressive marketing blasts.
• Write clear templates that match the category, so customers are not surprised by what they receive.
• Watch your quality rating and slow down the moment it dips, before Meta slows it down for you.

Done this way, a business can reliably reach thousands of opted-in customers with festival offers, order updates and reminders, month after month, on one stable number.

How do chatbots and automation fit on top of the Cloud API?

Once your number is on the Cloud API, the real leverage comes from building automation on top of it, because the platform is designed to talk to your other software. This is where a WhatsApp presence stops being a messaging inbox and starts saving your team hours every day.

Because the API connects to your systems, order confirmations and dispatch updates can fire automatically the moment status changes in your billing or eCommerce software. If you keep accounts in Tally or a similar system, payment reminders can go out on a schedule instead of someone manually chasing customers. Abandoned carts, feedback requests after delivery and appointment reminders can all run without a person clicking send.

On the incoming side, a chatbot can greet customers, answer common questions like store timings or order status, capture leads, and hand over to a human agent only when the query genuinely needs one. More advanced setups use AI to understand what the customer is asking in plain Hindi or English and respond helpfully, which is a natural extension of the automation work TheManki builds for clients.

The important sequencing point is that the Cloud API is the foundation, and automation is the building on top. You verify the number, get templates approved, respect opt-in and pricing, and then layer chatbots and integrations onto that solid base. Skip the foundation and even the smartest chatbot will sit on a number that keeps getting throttled.

Ready to put your business on the official WhatsApp platform?

Going official on WhatsApp is one of the highest-return moves an Indian SMB can make right now, but the setup, verification, template approvals and quality management are fiddly, and mistakes are expensive. This is exactly the kind of unglamorous, high-impact plumbing TheManki handles for its clients, in line with our tagline, Engineering Business Evolution.

TheManki is an India-based custom software, ERP and automation company, headquartered in Guwahati and founded by Mayank Agarwal. Through MankiWave, our Official WhatsApp Cloud API Partner platform, we handle the entire journey for you: getting your number onto the Cloud API, guiding your green tick application, writing and submitting templates for approval, setting up compliant opt-in flows, warming your number, and building the chatbots and integrations that connect WhatsApp to your billing, eCommerce and CRM systems.

If you are tired of running your business off a single phone, or you have been burned by a banned number, we can move you onto a stable, official setup that scales. Book a free, no-pressure strategy call with our team on WhatsApp at +91 70022 08642, and we will map out exactly what going official looks like for your business, your industry and your budget.