> For the complete documentation index, see [llms.txt](https://docs.authgear.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.authgear.com/~/changes/anTCj6yoZ06s3pLJk5v8/how-to-guide/custom-email-and-sms-templates.md).
# Custom Email and SMS Templates
Modify the template for emails and SMS messages for your Authgear project.
Authgear allows you to modify the default Email/SMS template content for sending password reset and verification messages.
To set a custom email or SMS template, log in to Authgear Portal then navigate to **Branding** > **Email/SMS Templates**.
You can edit the Email/SMS Templates for each language you have enabled for your application.
**Note:** You must upgrade your [project plan](https://docs.authgear.com/reference/billing-faq) to a paid plan to edit the templates.
### Important notice for sending SMS to Chinese phone numbers (+86):
The template for SMS to Chinese numbers can not be modified. As a result, even when you have set a custom template, Authgear will use the default template for Chinese numbers.
Authgear will use your custom SMS template for other users with non-Chinese phone numbers.
The following is the content of the default SMS template:
For `locale = en` or other languages
```
【Authgear】{code} is your {app-name} one-time password.
```
For `locale = zh-Hant` (Traditional Chinese)
```
【Authgear】你的{app-name}一次性密碼為 {code}，請勿分享給任何人
```
For `locale = zh-Hans` (Simplified Chinese)
```
【Authgear】你的{app-name}一次性密码为 {code}，请勿分享给任何人
```
The reason for falling back to the above default SMS template is that services are required to register their SMS templates before they can deliver to Chinese numbers. Authgear has registered the default SMS template so that one will deliver without any further action on your side.
Enterprise users who still wish to customize their SMS template for Chinese numbers can [contact us](https://www.authgear.com/schedule-demo) for more details.
### Important notice for sending SMS to Vietnamese phone numbers (+84)
Due to the regulatory requirements from the local government, all SMS messages to Vietnam must include the application name in the message body. If your users in Vietnam experience difficulties receiving SMS, try adding `[Authgear]` at the begining of the SMS template. SMS without `[Authgear]` may be blocked by the mobile operators. For example, your OTP message could appears like:
```
[Authgear] {code} is your {app-name} one-time password.
Don't share it with anyone.
```
Enterprise users who still wish to customize the beginning part of the message for Vietnamese numbers can [contact us](https://www.authgear.com/schedule-demo) for more details.
---
# 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.authgear.com/~/changes/anTCj6yoZ06s3pLJk5v8/how-to-guide/custom-email-and-sms-templates.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.
