> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chatflows.io/llms.txt
> Use this file to discover all available pages before exploring further.

# WhatsApp Business basics for Shopify stores

> The WhatsApp words and rules worth knowing before you start: templates, the 24-hour window, what Meta charges, and why a message doesn't arrive.

Before you start setting things up, it helps to know a few words that come up again and again in ChatFlows. Read this once and the rest of the guides will make sense.

> [!NOTE]
>
> Already know your way around WhatsApp Business? Skip straight to the [Quick start](https://docs.chatflows.io/index.md).

## The building blocks

> [accordion] Workspace — your company's account in ChatFlows
>
> **Your company's dedicated space inside ChatFlows.**
>
> You get a workspace when you install ChatFlows from Shopify. Your team, customers, conversations, and settings are stored securely within your workspace. Other companies cannot access your data.
>
> Everything you do in ChatFlows happens inside your workspace.

> [accordion] Channel — a WhatsApp number you have connected
>
> **A WhatsApp Business number connected to ChatFlows.**
>
> This is what sends and receives your messages. Connect more than one if you want — for example, one number for sales and one for support. A Facebook Messenger page can also be a channel.
>
> Nothing can be sent or received until you connect at least one.
>
> See [Connecting WhatsApp](https://docs.chatflows.io/core-setup/channels/whatsapp.md).

> [accordion] Contact — one customer's details
>
> **One person you can message.**
>
> A contact stores their phone number, and anything else you want to save — name, email, city, or your own [custom fields](https://docs.chatflows.io/core-setup/custom-fields.md).
>
> Customers from your Shopify store come in by themselves: shoppers who check out or order are added automatically, matched by phone number, and you can [bring in the customers already in your store](https://docs.chatflows.io/shopify/shopify-admin-app.md) with one click.
>
> You can also add them one by one, or [import a list](https://docs.chatflows.io/contacts/import-export.md) from an Excel or CSV file.

> [accordion] Conversation — one customer's chat
>
> **The chat between your business and one customer.**
>
> It works just like WhatsApp on your phone: every message you both send stays together in one thread. Your team opens and replies to these in the [Inbox](https://docs.chatflows.io/messaging/live-chat.md).
>
> A contact is the person. A conversation is the chat with that person.
>
> > [!NOTE]
> >
> > Your bill also uses this word. WhatsApp counts one *new conversation* whenever a chat begins after a quiet gap.

> [accordion] Template — a message Meta has approved
>
> **A ready-made message that Meta has checked and approved.**
>
> WhatsApp does not allow you to message a new customer in your own words. You must send an approved template first.
>
> One template works for every customer, because you can leave blanks that fill in automatically. Write `Hi {{1}}, your order {{2}} is out for delivery` once, and each person gets their own name and order number.
>
> See [WhatsApp Templates](https://docs.chatflows.io/messaging/whatsapp-templates.md) and [Merge fields](https://docs.chatflows.io/messaging/merge-fields.md).

> [accordion] Variable — a blank that fills in for each person
>
> A **variable** is a placeholder in a message. It is filled in with real information when the message is sent.
>
> You can use variables in **templates, campaigns, chats, quick replies, and automations**.
>
> In **templates**, the placeholders are numbered, like **`{{1}}`** and **`{{2}}`**. You fill them in when you send the template:
>
> * Sending to **one person** — type the value yourself, such as the customer's name.
> * Sending to **many people** — select a [merge field](https://docs.chatflows.io/messaging/merge-fields.md), and each person gets their own value.

> [accordion] Campaign — one message sent to many people
>
> **One message sent to many contacts together.**
>
> For example, a Diwali offer, a new price list, or a payment reminder.
>
> Choose who receives it — everyone, one group, or a smaller selected list — pick an approved template, then send it now or schedule it for later.
>
> See [Campaigns](https://docs.chatflows.io/messaging/campaigns.md).

> [accordion] Automation — replies that run on their own
>
> **Rules that reply to customers for you, day and night.**
>
> For example, when a customer sends "price", the automation sends your price list and asks which product they need. Nobody has to be online.
>
> Build it by dragging blocks on screen, or just describe what you want in plain English and let AI create the first version.
>
> See [Automation Flows](https://docs.chatflows.io/automation/overview.md).

## Two WhatsApp rules that shape everything

These rules come from WhatsApp, not from ChatFlows. Every tool built on the WhatsApp Business Platform follows them.

> [accordion] You need an approved template to message someone first
>
> You cannot type a fresh message and send it to a customer who has not first messaged you. You must use a template that Meta has already approved.
>
> Once approved, that template can go to anyone, any number of times.

> [accordion] When a customer replies, you get 24 hours
>
> The moment a customer messages you, a **24-hour window** opens. Inside it you can reply normally — type anything, send photos or files, no template message needed.
>
> Each new message from the customer restarts the 24 hours, so an active chat stays open. The window only closes after a full day of silence from their side.

| Your situation | What you can send |
| - | - |
| Messaging a new customer | An approved template |
| Customer replied within 24 hours | Anything you like, in your own words |
| Customer has been quiet over 24 hours | An approved template |

> [!TIP]
>
> This is why your first job in ChatFlows is getting one template approved. Without it, you cannot start a single conversation.

## What WhatsApp charges you

WhatsApp is free as an app on your phone. That part stays true. But once your business messages customers through a platform like ChatFlows, Meta charges for some of those messages.

So you have **two separate bills**:

* **Your ChatFlows bill** — what you pay us for the software, through Shopify.
* **Meta's message charges** — what WhatsApp charges for messages you send to customers.

### The short version

**Chatting costs you nothing. Starting a conversation costs money, and promotional messages cost the most.**

### What is free

> [accordion] Every message a customer sends you
>
> Incoming messages are never charged, no matter how many arrive.

> [accordion] Your replies inside the 24-hour window
>
> Once a customer has messaged you, everything you type back in your own words during those 24 hours is free — text, photos, files, voice notes.
>
> For most small businesses this is the majority of daily messaging.

> [accordion] Order and account updates sent inside the window
>
> A template that tells someone their order has shipped is free if you send it while their 24-hour window is still open.

### What is charged

Every template belongs to a category, and the category decides both the price and whether the 24-hour window helps you.

| Category | What it's for | When you're charged |
| - | - | - |
| **Marketing** | Offers, launches, reminders to come back | Always, even inside the window |
| **Utility** | Order updates, delivery updates, receipts | Only outside the window |
| **Authentication** | One-time passcodes and login codes | Only outside the window |
| **Service** | Your own words, inside the window | Never |

Two other things to know:

* **The price depends on the customer's country.** Messaging a customer in one country can cost several times more than another.
* **You're charged when a message is *delivered*, not when you press send.** A message that never reaches the phone isn't billed.

> [!TIP]
>
> Open a template and choose **View Stats** to see how it performed — sent, delivered, read, and button clicks. For what Meta actually charged you, check the billing section of your WhatsApp Business account in Meta's own tools. See [WhatsApp Templates](https://docs.chatflows.io/messaging/whatsapp-templates.md).

> [!NOTE]
>
> Meta sets and changes these rates, and they differ by country, so we don't list them here. Meta publishes the current rates and the full list of free cases under [pricing](https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing).

## Your number's reputation

WhatsApp watches how people react to your messages and adjusts what you're allowed to do. Two things move together.

> [!TIP]
>
> Message people who gave you their number — customers, inquiries, anyone who has contacted you before. Bought or scraped lists are the quickest way to get a number blocked.

> [accordion] Quality rating — green, yellow, or red
>
> A score Meta gives your number based on how customers respond. Blocks and reports push it down; replies and reads keep it up.
>
> Green is healthy. Yellow is a warning. Red means your sending is being restricted, and if it stays there the number can be suspended.
>
> You can see your current rating on the channel's page, and again when you build a campaign.

> [accordion] Messaging limit — how many new chats you can start a day
>
> A cap on how many *different* customers you can start a conversation with in a rolling 24 hours. Replying to people who messaged you doesn't count against it.
>
> New numbers start modest. The limit rises in steps as you send good-quality messages that people actually engage with, and gets there faster once your business is verified with Meta.

> [!TIP]
>
> These two are why "send to everyone immediately" is a bad first move. Start with customers who know you, keep the quality green, and the limits open up on their own.

> [!NOTE]
>
> Meta explains the tiers and how to move up them under [messaging limits](https://developers.facebook.com/documentation/business-messaging/whatsapp/messaging-limits).

## Your business identity

Three different things that are easy to confuse.

> [accordion] Display name — the name customers see
>
> The business name shown at the top of the chat. Meta reviews it, and it has to genuinely relate to your business. Made-up names, words like "Official", and web addresses get rejected.
>
> A rejected display name stops your setup, so it's worth getting right first time.

> [accordion] Business verification — proving your business is real
>
> Meta checks your business documents against a live, public website showing your name, what you sell, and how to contact you.
>
> It isn't required to start sending. What it gives you is a faster path to higher messaging limits and quicker template approvals.

> [accordion] The verified badge — the tick next to your name
>
> The badge shown beside a business name in WhatsApp. It's the thing most people mean when they ask about the "green tick", though Meta now shows it in blue.
>
> **Being honest: most small businesses will not get it.** Meta grants it based on how well known your brand is — it looks for independent press coverage, not paid placements. It can't be bought, and no platform can obtain it for you. It's also not needed to message customers or to look professional; a clear display name does that job.

## When a message doesn't arrive

Every message shows a status. Knowing what each one means saves a lot of worry.

| Status | What it means |
| - | - |
| **Queued** | Waiting its turn to go out. Normal for large campaigns. |
| **Sent** | It left ChatFlows and reached WhatsApp. |
| **Delivered** | It reached the customer's phone. |
| **Read** | They opened it. |
| **Failed** | It couldn't be delivered. |

> [accordion] It says Sent but never Delivered
>
> The customer's phone is off, out of signal, or out of storage. WhatsApp keeps trying for a while and delivers it when they come back online. Nothing is broken and nothing is lost.

> [accordion] It says Delivered but never Read
>
> Either they haven't opened it yet, or they've turned read receipts off in their WhatsApp settings.
>
> **If read receipts are off, "Read" will never appear — even after they've read it.** That's a WhatsApp privacy setting on the customer's phone, and nothing can change it from our side. Judge those conversations by whether people reply, not by read counts.

> [accordion] It says Failed
>
> Common reasons:
>
> * The number isn't on WhatsApp, or was typed wrong.
> * You've hit your daily limit for starting new conversations.
> * You tried to send outside the 24-hour window without a template.
> * The template was paused or removed after you scheduled the message.
> * Too many people recently marked your messages as spam.
>
> Campaign reports list the reason against each failed contact, and you can retry just those. See [Campaigns](https://docs.chatflows.io/messaging/campaigns.md).

### When a template is rejected

Templates are reviewed before you can use them, and rejection is common on a first attempt. The reason is shown against the template, and you can edit and resubmit as often as you need.

The usual causes are choosing the wrong category — promotional wording submitted as an order update, for example — placeholders left without example text, or wording that reads like spam.

> [!WARNING]
>
> Approval isn't permanent. If people repeatedly block or report messages sent with a template, Meta can pause or switch it off later, even after months of use. You'll see the changed status on the **Message Templates** page.

> [!NOTE]
>
> Meta lists every template status and the rules behind them under [message templates](https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/overview).

## What's next

> [card] [Connecting WhatsApp](https://docs.chatflows.io/core-setup/channels/whatsapp.md)
>
> Connect your WhatsApp Business number to your workspace.

> [card] [WhatsApp Templates](https://docs.chatflows.io/messaging/whatsapp-templates.md)
>
> Write your first template and send it to Meta for approval.

> [card] [Recover abandoned carts](https://docs.chatflows.io/shopify/cart-recovery.md)
>
> Send your first approved template to shoppers who left at checkout.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.