> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/whatsapp-commerce/getting-started/connecting-whatsapp-number.md).

# Connecting WhatsApp Number&#x20;

To start using **WhatsApp Catalog Automation** and access all features, your business must connect a number through the **WhatsApp Business API**.

{% embed url="<https://youtu.be/H0Flfzh8WCg?feature=shared>" %}

### Number Requirements

1. You need a **mobile or landline number** that has **not been previously used** on WhatsApp.
2. If you already use the number on WhatsApp Personal or WhatsApp Business App, you must **delete the account from the app** (do not uninstall the app).
   * For better quality, we recommend using a **new number**.
3. Avoid using numbers that were previously **blocked by WhatsApp** or connected to any **automated software**, as this may increase the risk of future blockages.
4. The number must be **active and able to receive a Text or Voice OTP**, since WhatsApp will send one during the verification process.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.pickyassist.com/whatsapp-commerce/getting-started/connecting-whatsapp-number.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
