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

# Why build on WhatsApp

> Why a conversation beats a form, what opens up when your product lives where customers already are, and the kinds of things people build on WhatsApp.

Most of the ways a business reaches people are borrowed. Social feeds are rented from a platform that decides who sees what. Email lands in a tab people check less every year. A website waits, quietly, for someone to remember it exists and type the address. In each case the relationship sits on someone else's terms, and mostly it flows one way.

A conversation is different. It's the one place a customer and a business can actually talk — and on WhatsApp, that conversation happens in the app people already have open.

## The reach is the point

WhatsApp isn't one channel among many with a bit more scale. For a large part of the world it's the default way people communicate at all.

<CardGroup cols={2}>
  <Card title="~3 billion users" icon="globe">
    More than 3 billion people use WhatsApp every month, sending north of 100 billion messages a day.
  </Card>

  <Card title="Where you'd expect a website" icon="map-pin">
    In markets like South Africa, Brazil, and Nigeria, penetration sits around 90%+. WhatsApp *is* the internet's front door for a lot of people.
  </Card>

  <Card title="A daily habit" icon="repeat">
    People open WhatsApp far more often than any other app in a day — so a message there meets an existing habit rather than fighting for a new one.
  </Card>

  <Card title="Messages get read" icon="mail-open">
    Because it's where personal conversations live, messages tend to actually get opened — read rates run well above what a marketing email can expect.
  </Card>
</CardGroup>

## Why a conversation beats a form

A form is a wall with a slot in it. The customer fills in fields, presses submit, and hopes something happens on the other side. They stay anonymous until the moment they hand over their details, and most of them leave before they get there.

A conversation inverts that. From the first message you have a named person who is *already talking to you* — not a bounce off a landing page. You can ask one thing at a time, adapt to what they say, answer the question they actually have, and carry the thread forward. Nobody has to "find the right page." They just reply.

That shift shows up in the outcomes. When a link points someone to a web form, most drop off before they finish. When it opens a chat, more people reply and more of them see it through — response and completion tend to run several times higher than the same journey does over email or a website.

<Tip>
  The mental shift is from **broadcasting at people** to **being reachable by them**. A website is somewhere customers have to go. A conversation is somewhere they already are.
</Tip>

## What opens up when you live where customers already are

Once the interaction is a conversation instead of a destination, a few things change at once:

* **You own the relationship.** The thread is a direct line between you and the customer — not a post in a feed an algorithm may or may not show, and not an email hoping to dodge the promotions tab.
* **The distance to action collapses.** There's no "click the link, load the page, find the button." An ad that opens a chat lands you a named lead mid-conversation. A question gets answered in the same place it was asked.
* **It works around the clock.** A conversation doesn't need someone at a desk. Answers, confirmations, and updates can arrive in seconds, at any hour.
* **It carries credibility.** A verified business presence on WhatsApp reads as real in a way a cold email or an unknown number never quite does.

## The kinds of things people build

Because the channel is just "a conversation," the range of what fits inside one is wide. A sample of what businesses run on WhatsApp:

<CardGroup cols={2}>
  <Card title="Support that answers instantly" icon="life-buoy">
    Common questions handled in seconds, at any hour, with a handoff to a person when it matters.
  </Card>

  <Card title="Lead capture and qualification" icon="user-plus">
    Turning an ad click or a "hi" into a named, qualified lead — without a landing page in the middle.
  </Card>

  <Card title="Bookings and reminders" icon="calendar-check">
    Appointments booked, confirmed, and reminded about, all in the thread.
  </Card>

  <Card title="Updates and notifications" icon="bell">
    Order status, flight and check-in updates, invoices, payslips — delivered where they'll be seen.
  </Card>

  <Card title="Learning and internal tools" icon="graduation-cap">
    Tutoring bots, quizzes, staff knowledge bots — the same conversation shape, pointed inward or at customers.
  </Card>

  <Card title="Commerce and re-engagement" icon="shopping-bag">
    Guided buying, cart recovery, and bringing people back with a message that actually gets opened.
  </Card>
</CardGroup>

For a long time most of this was locked behind enterprise budgets. That's the real change: the tools to build it are now within reach of a small business, not just a large one.

## Where to next

<CardGroup cols={2}>
  <Card title="Which WhatsApp product" icon="git-branch" href="/learn/whatsapp-products">
    There are three WhatsApp products, and only one of them can be programmed. Start here before you build.
  </Card>

  <Card title="Message types" icon="layout-list" href="/learn/message-types">
    The building blocks of a WhatsApp conversation — text, buttons, lists, media, flows, and templates.
  </Card>

  <Card title="Thinking in flows" icon="route" href="/learn/thinking-in-flows">
    How to design a conversation people actually finish.
  </Card>
</CardGroup>