> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/messaging-channels/whatsapp-api/managing-your-whatsapp-api/create-commands-or-menu-for-end-users-for-whatsapp-api.md).

# Create Commands Or Menu For End Users For WhatsApp API

* Go to **Channels → WhatsApp → WA Manager** to open WhatsApp Manager for your number.
* Navigate to **Phone Numbers → Settings → Automations → Commands**.
* Click **Edit** to create or manage commands (predefined menu keywords).
* Add a **Command name** (max 32 characters) and a **Hint/Description** (max 256 characters).
* You can create up to **30 commands** which users can see by typing **/** (forward slash) during chat.
* Click **Save** after adding the required commands.
* Go to your **Flow Builder** and add these command keywords as **hot keywords** or conditions (e.g., contains “expo” or exact match “/expo”).
* When a user types **/**, the command menu will appear and selecting a command will trigger the linked bot flow.

Commands can be useful to trigger specific Bot flows based on user input.

{% embed url="<https://youtu.be/i_8coqXkiY8>" %}


---

# 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://helpdocumentation.gitbook.io/user-documentation/messaging-channels/whatsapp-api/managing-your-whatsapp-api/create-commands-or-menu-for-end-users-for-whatsapp-api.md?ask=<question>&goal=<user_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.