> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/messaging-templates/create-a-messaging-template.md).
# Create a Messaging Template
Take the PXA course
Use *Messaging templates* as a way to reach out to partners when you send content, dynamic fields, and insert signup links.
#### Create a messaging template
1. From the left navigation menu, select  **\[Engage] → Partners** → **Automation** → **Messaging Templates**.
2. In the upper-right corner, select **Create Messaging Template**.
3. If you want to apply an existing template,  **\[Toggle on]** **Messaging Template** and select an existing messaging template from the  **\[Drop-down menu]** **Select Template**.
4. Enter your messaging template details:
| Field | Description |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Template Name | This will be the name you select when using the template. |
| Send from | This is the *from* name that recipients will see when they receive the template. |
| Reply to | This is the email address that partners will contact when they reply to this template |
| Cc/Bcc | 
\[Toggle on] to include a Cc or Bcc email recipient in addition to the partners in your chosen segment.
• You can add 1 email address to the Cc field and 1 to the Bcc field.
• Any email address added as a CC or BCC will receive a copy of every email sent to partners in the selected segment. The number of emails may vary depending on the segment size.
|
| Subject | The subject of the template. |
| Content | Enter the content of your template in the provided text editor.
• The Content section will already be populated if you have chosen to add an existing template.
|
5. Optionally, **Insert signup link** to one of your template terms. This will add a **Join my program** button that acts as a sign up link to your template terms.
6. Optionally, **Insert other dynamic token** fields into your newsletter. You can see the dynamic fields available by selecting the  **\[Expand]** icon to the right of the option.
* See the *Dynamic fields reference* below for more info about these fields.
Dynamic fields for newsletter
Select **Insert** to populate your template with relevant information (such as a partner’s name, or the current date) in your template.
{% hint style="warning" %}
**Attention:** Tokens are case sensitive. Do not place any formatting within special tokens (for example,`{lastName}` is valid but, `{LastName}` is not.
{% endhint %}
| Token | Description |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `{adcode_}` | Populates with the full ad listing of the specified \ value (e.g., {adcode\_\}).
Ad code limitations
The number of ad codes you can use per template is limited by the number of audience members that are part of your template.
Number of Adcodes/Limit
Maximum of 1 — up to 60,000 partners
Maximum of 5 — up to 30,000 partners
Maximum of 10 — up to 20,000 partners
Maximum of 20 — up to 5,000 partners
|
| `{mpid}` | Populates with the ID value of the partner’s account (e.g., 98765). |
| `{mpname}` | Company name. |
| `{firstName}` | Populates with the first name of the partner (e.g., John). |
| `{lastName}` | Populates with the last name of the partner (e.g., Doe). |
| `{currentDay}` | Populates with the current date (e.g., January 19, 2038). |
| `{currentTime}` | Populates with the full date in ISO format (e.g., 19-Jan-2038 03:14:08 UTC). |
| `{currentMonthYear}` | Populates with the current month and year (e.g., January, 2038). |
| `{unsubscribeUrl}` | URL to unsubscribe from the template. |
| `{programName}` | The program name. |
| `{programLogoSrc}` | The source URL of the program logo. |
7. Select **Preview** for a preliminary display of the segment. Once you're happy with the preview, select **Done** or **Send test email**.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/messaging-templates/create-a-messaging-template.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.