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

# WhatsApp

> Two ways to connect, both built to protect your numbers

WhatsApp is where leads actually answer, and it is also where careless automation gets numbers banned. Nudge supports two kinds of WhatsApp connections and treats them very differently on purpose.

## Rep numbers via Evolution API

Each rep's own WhatsApp number connects through the **Evolution API**. This is the warm lane: automated follow-ups and one-to-one conversations that look and feel like a person texting, because the number belongs to a person.

To keep those numbers safe, Nudge paces them automatically:

* **A gap between sends** per number, so messages trickle out at human speed.
* **Hourly and daily caps** per number on top of the gap.
* **Working hours**: automated messages hold until the owner's business hours. A 3am follow-up closes no deals.
* **Stop on reply**: an inbound message instantly cancels that contact's queued automated sends.

None of this needs configuration by reps; admins set the pace once in Settings and every automated send obeys it.

## A business number via the WhatsApp Business API

For volume that should not ride on a personal number, connect an official **WhatsApp Business API** number. This lane is fast: Meta enforces its own limits, so Nudge sends at full speed without the pacing above.

<Note>
  The Business API only allows free-form messages inside the 24-hour window after a contact's last inbound message. Outside that window Meta requires pre-approved template messages. Plan cold outreach on this lane accordingly.
</Note>

## Which number sends what

The sending number is chosen per action. A trigger's WhatsApp action set to **Each lead's owner** sends from the owner's connected number, so the lead hears from the same person who will pick up the conversation. Bulk sends can override with one fixed sender.

## Media

Templates can attach an image or a document (PDF, spreadsheet) from the shared asset library; the message body becomes the caption. See [Templates](/automation/templates).