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

# 📝 Templates

Typing the same useful answer for the tenth time is a waste. Templates give you the good starting point without pretending every person deserves the exact same message.

You can create normal message templates and multi-step sequence templates. Both can be personal or shared with your workspace.

## Insert a template

<Steps>
  <Step title="Open the template menu">
    In a conversation, click **Templates** or type `;;` in the composer.
  </Step>

  <Step title="Choose Messages or Sequences">
    Press `1` for **Sequences** or `2` for **Messages** while the menu is open. Search or move through the saved templates.
  </Step>

  <Step title="Insert and personalize">
    Select a template, resolve any missing variables, then edit the draft for this person before sending or scheduling it.
  </Step>
</Steps>

## Create a message template

Open the template menu and choose **Create template**. Add:

→ A name that describes when to use it.<br />→ The message itself.<br />→ Personal or shared scope.

You can edit, duplicate, delete, and drag templates into the order you use most often.

## Use custom variables

Write variables with double curly brackets:

```text theme={null}
Hi {{first_name}},

I saw what you're building around {{topic}}.
Would it be useful if I sent over {{resource}}?
```

TalkToHumans highlights variables in the composer. Resolved fields and missing fields look different, so you can catch unfinished placeholders before sending.

Common examples include:

→ `{{first_name}}`<br />→ `{{topic}}`<br />→ `{{link}}`<br />→ `{{icp}}`<br />→ `{{outcome}}`<br />→ `{{department}}`

Custom placeholders are useful when the important detail cannot come from a profile. Write `{{specific_observation}}`, then fill it manually for each person.

## Personal or shared?

Use personal templates for your voice, experiments, and one-person workflows. Use shared templates when the team needs one approved starting point.

A shared template should still leave room for judgment. The best team templates standardize structure, proof, and next step while leaving the opening line specific to the person.

<Tip>
  Name templates after the moment: `Positive reply: send calendar` is easier to use than `Template 7`.
</Tip>