> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/outsmart-knowledge-base/outsmart-knowledge-base-pt/loja-virtual-pacotes-e-power-ups/power-ups/portal-de-cliente/criar-modelos-de-email-do-portal-de-cliente.md).

# Criar Modelos de email do Portal de cliente

Criar os modelos usados para convites do Portal, Pedidos e reposições de palavra-passe.

O Portal de cliente usa modelos de email separados para as ações do portal.

Criar estes templates antes de os associar nas Definições de Portal.

{% stepper %}
{% step %}

### Abrir Modelos de email

Ir para **Definições → Modelos de email**.
{% endstep %}

{% step %}

### Abrir a secção Portal de cliente

Encontrar a secção de Modelo de email para emails do portal.
{% endstep %}

{% step %}

### Adicionar os templates de que necessita

Criar templates para convites, pedidos, notificações internas e reposições de palavra-passe.
{% endstep %}

{% step %}

### Guardar os templates

Verificar o assunto, o remetente e o conteúdo.

Depois, guardar.
{% endstep %}

{% step %}

### Associá-los ao portal

Abrir **Definições → Definições de Portal → Definições de email** e selecionar os templates.
{% endstep %}
{% endstepper %}

### Perguntas frequentes

<details>

<summary>Que templates são normalmente necessários?</summary>

Templates de convite, pedido, pedido interno e reposição de palavra-passe.

</details>

<details>

<summary>O que acontece se for omitido um template?</summary>

Esse email não é enviado.

</details>

<details>

<summary>Os templates são associados aqui?</summary>

Não.

São criados primeiro e depois associados nas Definições de Portal.

</details>

### Tópicos relacionados

* [**Portal de cliente**](/outsmart-knowledge-base/outsmart-knowledge-base-pt/loja-virtual-pacotes-e-power-ups/power-ups/portal-de-cliente.md)
* [**Configurar definições de email**](/outsmart-knowledge-base/outsmart-knowledge-base-pt/loja-virtual-pacotes-e-power-ups/power-ups/portal-de-cliente/configurar-as-definicoes-de-email.md)
* [**Automação para o Portal de cliente**](/outsmart-knowledge-base/outsmart-knowledge-base-pt/loja-virtual-pacotes-e-power-ups/power-ups/automacoes-ilimitadas/automacoes-para-o-portal-de-cliente.md)


---

# 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://knowledge.out-smart.com/outsmart-knowledge-base/outsmart-knowledge-base-pt/loja-virtual-pacotes-e-power-ups/power-ups/portal-de-cliente/criar-modelos-de-email-do-portal-de-cliente.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.