> For the complete documentation index, see [llms.txt](https://ajuda.comandaxis.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ajuda.comandaxis.com.br/clientes-e-marketing/mensagens-whatsapp.md).

# Mensagens de WhatsApp

> Templates para chamar os clientes de volta, com nome, cupom e link do cardápio.

Em **WhatsApp › Mensagens**, crie templates com **Novo template** e marque o preferido com **Definir como padrão**. O nome do cliente entra depois da saudação e o link do cardápio vai no final.

No texto, você pode usar as variáveis {loja}, {dias} (dias sem pedir), {pedidos}, {cupom} e {beneficio}: elas são trocadas pelos dados de cada cliente.

{% hint style="info" %}
Com o WhatsApp da loja conectado (**Configurações › Conexão e avisos**), o **Enviar** manda a mensagem direto pelo número da loja (até 200 por dia) e ela aparece no **Inbox**. Sem a conexão, o **WhatsApp Web** abre com a mensagem pronta e você confirma o envio. Nos dois casos o contato fica registrado no histórico do cliente.
{% endhint %}

{% hint style="info" %}
Ficou com dúvida? No painel, pergunte ao **Chefe X**, o assistente no canto inferior direito da tela.
{% endhint %}


---

# 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://ajuda.comandaxis.com.br/clientes-e-marketing/mensagens-whatsapp.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.
