> 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-on-whatsapp-or-predefined-menu-or-quick-access-menu.md).

# Create Commands On WhatsApp Or Predefined Menu Or Quick Access Menu

To create predefined menu commands in WhatsApp:

* Go to **Channels → WhatsApp → 3 dots → WA Manager** to open WhatsApp Manager.
* Navigate to **Phone Numbers → Settings → Automations → Commands**.
* Click **Edit** and add your predefined menu commands (keywords with descriptions).
* You can add up to **30 commands** which act as shortcuts to trigger specific bots or flows.
* Click **Save** after adding the commands.
* Go to your **Flow Builder** and add these commands as **hot keywords** or conditions                    (e.g., contains “Expo” or exact match “\Expo”).
* During chat, customers can type **/** (backslash option) to view the command menu and select any option to trigger the linked flow.

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


---

# 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-on-whatsapp-or-predefined-menu-or-quick-access-menu.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.