> For the complete documentation index, see [llms.txt](https://docs.zipchat.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zipchat.ai/channels/whatsapp.md).
# WhatsApp
This section contains everything you need to know about the Zipchat x WhatsApp Integration.
### Why WhatsApp
WhatsApp is a service and marketing channel with incredible potential; it’s the most used messaging app in Europe, LATAM, India, and it’s growing fast in the United States
Main reasons to use WA:
* Open rate of marketing messages: 85%
* Click-through-rate: 15%
* Automatic collection of the customer’s Name, Surname and Phone Number
* 24 hours to keep the conversation going, while if someone texts you on your website, as soon as they close the browser you cannot reach to them
* You are always in your customers pocket, one conversation away
* Most importantly - customers EXPECT to speak with you on WA
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.zipchat.ai/channels/whatsapp.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.