Letterbook Docs
Templates overview
Understand snippets and email signatures in Letterbook.
Last updated June 25, 2026
What this guide covers#
Templates help your team reuse approved language without rewriting the same reply in every ticket.
Letterbook currently has two template tools in Settings > Templates:
- Snippets are reusable reply blocks that agents insert while composing a message.
- Email signatures are per-inbox signatures that Letterbook appends to draft replies.
Use snippets for support language that changes by situation. Use signatures for standard closing details tied to the inbox that sends the reply.
Snippets#
Snippets are shared text templates for common responses, policy explanations, troubleshooting steps, and handoff language.
Agents insert snippets from the message editor by typing /. The snippet content is added to the draft, where the agent can edit it before sending.
Snippets support rich text and variables. Variables let a snippet personalize the reply with customer or agent details when those values are available.
Read the full guide: Create and use snippets.
Email signatures#
Email signatures are configured per active inbox. A support address can have one signature while another address uses a different signature.
Signatures are automatically appended to draft replies, which makes them best for content that should stay consistent on every email sent from that inbox:
- Team name
- Company name
- Support hours
- Compliance or legal footer
- Plain closing language
Read the full guide: Configure email signatures.
Choosing the right template type#
| Need | Use |
|---|---|
| Insert a saved reply for a specific situation | Snippet |
| Personalize a response with customer or agent variables | Snippet |
| Add a standard footer to replies from one inbox | Email signature |
| Keep different closings for support, billing, and sales inboxes | Email signature |
| Share approved troubleshooting steps with the team | Snippet |
Recommended setup#
Start with a small set of high-value snippets. The best first snippets are replies your team already sends several times a week:
- Acknowledging a bug report
- Asking for logs, screenshots, or reproduction steps
- Explaining refund or cancellation policy
- Confirming an escalation
- Closing a resolved ticket
Then configure signatures for each active inbox that sends email replies. Keep signatures short enough that they do not bury the actual support response.