Front Message Templates & Canned Answers Explained

What a message template actually is in Front

In some help desks these are called canned responses or saved replies; in Front they're message templates, and the naming matters because a template can carry more than body text. A single template can hold a subject line, a formatted body, attachments, and even a satisfaction survey — all saved together and dropped into a reply in one action. That's a meaningful step up from a plain text snippet.

Because Front is a shared-inbox platform rather than a ticketing tool, templates are built for collaboration from the start. They live alongside the other team primitives — shared tags, signatures, and rules — and they can be scoped to individuals or to whole teams. If you're still getting your bearings on how the inbox itself is structured, what is Front covers the shared-inbox model that templates plug into.

Creating a template: two paths

Front gives you two ways in, and most teams use both depending on where they are when inspiration strikes.

From the composer (the fastest path). When you've just written a reply you know you'll send again, click the template icon in the composer toolbar and choose New from draft. Front lifts your current draft into a new template and asks you to name it, set its privacy (individual or shared), and pick a folder. This is the natural way canned answers accumulate — you promote your best real replies into reusable ones.

From Settings (the deliberate path). Go to Settings → Templates → Messages tab and click Create. Here you fill in the fields directly: a name, an optional subject, the message content, a folder, and the inbox availability. Per Front's Understanding message templates and folders documentation, both admins and regular members can create templates, so this isn't an admin-only chore.

There is currently no hard limit on the number of message templates you can create, and you can organize them into folders up to five layers deep — useful once a library grows past a couple of dozen entries.

Personal vs shared (team) templates

This is the distinction that trips people up, so it's worth being precise. Front supports two visibilities:

• Individual templates are visible only to you. Good for your own drafts-in-progress, personal phrasings, or replies you're not ready to standardize for the team.
• Shared templates are visible to teammates at the inbox level — the team's canonical answers to common questions. Shared templates can be restricted to specific inboxes using the "Make available for any inbox" setting, so a Billing template needn't clutter the Sales inbox.

One nuance from the docs: teammates who hold the "Shared message templates and folders" permission can view all shared templates regardless of inbox restrictions — worth knowing when you're reasoning about who sees what.

Dynamic variables: the part that keeps templates personal

A canned answer that opens "Hi there" every time reads like a canned answer. Front's dynamic variables fix that by pulling live values into the text as you insert the template. You type two open curly brackets {{ in the composer or template editor and a menu of variables appears.

The common ones, per Front's guide to using variables in message templates:

• Recipient: {{recipient.first_name}}, {{recipient.last_name}}, {{recipient.email}}
• Account / teammate: {{account.name}}, {{user.name}}, {{user.email}}
• Conversation: {{conversation.id}}, {{message.id}}
• Custom fields: {{recipient.custom.customer_id}}, {{account.custom.account_manager}}

The detail that saves you from awkward blanks is the fallback syntax: {{recipient.first_name | 'there'}} renders the contact's first name when Front knows it and the word there when it doesn't. Always give name variables a fallback — an empty greeting is worse than a generic one.

One honest caveat on plan gating: the richer end of dynamic variables — application objects ({{app.object_name}}, one per template) and using variables inside automated rules for auto-replies — is documented as an Enterprise-plan feature. Basic recipient and account variables are broadly available, but if you're planning variable-driven automation, confirm your tier against Front's pricing before you design around it.

Inserting a template mid-reply

Once a template exists, dropping it into a conversation takes a second. There are two motions:

1. The composer icon. Click the message templates icon in the composer toolbar to open the picker. You can search by keyword or scroll, hover to preview the full template, then click to insert.
2. The slash shortcut. Type / (or /template) directly in the composer, start typing the template's name, and press Enter. This is the keyboard-driven path most power users live in — no mouse required.

Either way, dynamic variables resolve at the moment of insertion, so {{recipient.first_name}} becomes the actual customer's name in the reply you're about to send.

Template hygiene: keeping the library trustworthy

Templates rot quietly. A price changes, a policy updates, a product renames — and a stale canned answer keeps confidently sending the old version. A few habits keep the library honest:

• Fold aggressively. Use Front's folders (up to five layers) to group by team and topic. A flat list of 60 templates is a list nobody browses.
• Name for search, not for you. Because insertion is search-driven (/refund, /shipping-delay), name templates by the situation the agent is in, not internal jargon.
• Prune with data. On the latest Professional plan or above, the message templates report shows how often each template is applied, its reply rate, and handle time — so you can retire the ones nobody uses and double down on the winners. Note the report excludes auto-reply rules, deleted templates, private templates, and sequences, per Front's message templates report docs.
• Own shared templates. Assign a clear owner per folder so "who updates the refund wording?" always has an answer.

The honest limits — and where an AI layer picks up

Front's templates are genuinely good at the job they're built for: fast, consistent, personalized replies to the questions you already know how to answer. But a template is a static artifact. It can't decide which answer a conversation needs, it can't read a novel question and compose a fresh reply, and its variables only surface data Front already stores as a field — they can't reach into your order system, look up shipment #4471, and write that status into the sentence.

So the coverage curve flattens. Templates handle the top handful of repeat questions beautifully and then leave the long tail — the ambiguous, the multi-part, the "it's kind of two questions at once" — for an agent to type out by hand every time. Choosing the right template is itself work, and picking the wrong one and half-editing it can be slower than writing from scratch.

This is the seam where an AI agent layer fits, and the broader category of AI agents for customer service exists to do exactly the reasoning-heavy work a canned answer can't. Macha is one such layer: it runs on top of the Front you already use through a native connector — it does not replace Front or its templates. Where a template is a fixed block of text, a Macha agent reads the actual conversation, decides whether it can be answered, drafts or posts a grounded reply, and can fetch live order or account status through a custom tool that turns a REST API into something the agent can call and quote inside the answer. Credits are consumed per AI action, not per resolution — the pricing page has the breakdown.

The clean division of labour: keep Front's message templates as the fast, human-owned answers to your most common questions, and layer an agent on top for the long tail the template library was never going to cover. One is a snippet; the other is a colleague who reads before it writes.

FAQ

What are message templates in Front? They're Front's canned answers — saved replies you create once and reuse. A template can include a subject, formatted body, attachments, and a satisfaction survey, and can carry dynamic variables that auto-fill values like the recipient's name when you insert it.

How do I insert a message template in a reply? Two ways: click the message templates icon in the composer toolbar to search and preview, or type / (or /template) in the composer, type the template's name, and press Enter to insert it.

What's the difference between personal and shared templates? Individual templates are visible only to you; shared templates are visible to teammates at the inbox level and can be restricted to specific inboxes. Both admins and regular members can create either type.

How do dynamic variables work? Type {{ in the composer to pick a variable such as {{recipient.first_name}} or {{account.name}}. Add a fallback with {{recipient.first_name | 'there'}} so an unknown value renders a sensible word instead of a blank. The richer application-object variables and rule-based auto-replies are gated to the Enterprise plan.

Can I add AI to Front without replacing Front? Yes. An AI agent layer like Macha connects to Front as a native connector and runs on top of your existing inbox and templates — it doesn't replace them. It handles the long-tail conversations no canned answer covers by reading each message and drafting a grounded reply, while your templates stay the fast answer to common questions.

Ready to cover the questions your templates can't? Start a free trial of Macha and connect it to your Front inbox in minutes.