> ## Documentation Index
> Fetch the complete documentation index at: https://sippet.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Create reusable templates

> Build reusable email, SMS, and API request templates for support and follow-up workflows.

## Goal

Create a small template library your team can reuse across support operations.

## Before you start

* Decide which templates should be customer-facing and which are purely operational.
* Keep the first variable set simple and easy to validate.

## Step 1: start with the most repeated message

Good starting points:

* support follow-up email
* reminder SMS
* API request template for sending a support outcome into another system

## Step 2: define clear variables

Use variables for information that changes often, such as:

* customer name
* account name
* next-step link
* support outcome

## Step 3: keep the content operationally safe

* avoid ambiguous language
* make next steps explicit
* keep templates short enough for the channel

## Example workflow

* the team creates a standard “support follow-up” email template
* a matching SMS template handles shorter reminders
* a playbook uses those templates after a call outcome requires follow-up

## What good looks like

* operators and automations use the same approved wording
* message variables are easy to fill correctly
* templates reduce editing time without sounding robotic

## Troubleshooting

* If a template becomes too flexible, split it into two narrower templates.
* If variables are frequently wrong, reduce the number of required placeholders.

## Related pages

* [Templates overview](/console/templates)
* [Build a follow-up playbook](/console/playbooks-guide)
* [Configure SMS and WhatsApp follow-up](/console/sms-whatsapp-guide)
