How to Set Up Canned Responses in Freshdesk

What a canned response actually is

A canned response in Freshdesk is a reusable reply template, stored centrally and available from inside any ticket. Each one has a title (how agents find it), a message body (rich text, with formatting, links, and images), and a visibility setting that decides who can use it. Templates live inside folders, so you can group them by team or topic rather than scrolling one flat list.

The feature that keeps a template from feeling robotic is dynamic placeholders — tokens like {{ticket.requester.name}} or {{ticket.id}} that resolve to real values the moment an agent inserts the response into a live ticket. So one saved template can greet Priya by her first name on ticket #4471 and greet Marcus on #4472, without either agent touching the wording. If you want the conceptual tour before the click-by-click, we cover the mental model in Freshdesk canned responses explained.

Step 1: Create a folder to hold your responses

Freshdesk organises canned responses folder-first, so you make the container before the template. Per Freshworks' Creating common reply templates with Canned Responses documentation, the path is:

1. Go to Admin → Agent Productivity → Canned Responses. (On the Customer Service Suite the equivalent path is Admin Settings → Configuration and Workflows → Ticket Canned responses.)
2. Click New Folder.
3. Give the folder a name that matches how your team thinks — Billing, Onboarding, Shipping & Returns — and click Create.

Folders are cheap; make a handful up front. A team that files templates under sensible headings finds the right one in seconds, while a single un-foldered pile becomes unusable at around twenty entries. You can also move responses between folders later by selecting them and choosing Move, so early mistakes aren't permanent.

Step 2: Write the response and add dynamic placeholders

With a folder open, click New Canned Response inside it, then:

1. Enter a clear title — this is what agents search for, so make it descriptive (Refund status update, not Reply 3).
2. Compose the message in the rich-text editor. Use the formatting toolbar for structure, links, and images just as you would in a normal reply.
3. Drop in placeholders using the insert-placeholder control (the green plus / Insert Placeholders button above the editor). Freshworks' dynamic content and placeholders reference lists the common tokens:

One thing worth internalising: placeholders only resolve inside a live ticket. In the template editor they stay as literal {{...}} tokens — that's expected. They fill in with real data only at the moment an agent inserts the response into an actual reply, so always sanity-check a template by inserting it into a real ticket rather than trusting the preview.

Step 3: Decide who can use it — sharing across agents

Before you save, Freshdesk asks who the response is Available for. There are three levels, and choosing the right one is what keeps your library both useful and uncluttered:

• Myself — the response is saved to your Personal folder and no one else can see it. Good for the phrasings you lean on that aren't team standards.
• All agents — the response is visible to everyone in the account. Use this for canonical, on-brand answers you want the whole team giving identically.
• Agents in group — the response is scoped to one or more specific groups (Billing, Tier 2, EU Support). This is the sweet spot for most teams: the right templates surface for the right desks without cluttering everyone else's list.

A practical rule: default team-wide answers to All agents, keep department-specific ones on Agents in group, and reserve Myself for personal drafts. That way the shared library stays curated instead of ballooning with everyone's private variations.

Step 4: Insert a canned response in a reply

Saved templates are only worth it if they're fast to reach mid-ticket. Inside any ticket:

1. Open the Reply editor.
2. Click Insert Canned Response (the icon/button above the reply field).
3. Browse or search by title, pick the template, and it drops into the reply — with any placeholders resolved to that ticket's real values.
4. Edit anything ticket-specific, then send.

If you're mid-reply and realise the answer you're typing should be reusable, you don't have to leave: Freshdesk lets you Add New Canned Response straight from the canned-response dropdown, capturing the wording you just wrote into a fresh template for next time. That "save-as-you-go" habit is how good libraries actually get built — from real replies, not a big up-front documentation project.

The honest limits — and where an AI layer picks up

Canned responses are a genuinely great feature, and they're free across Freshdesk's plans, so there's no reason not to use them. But be clear about the shape of the tool. A canned response is a static template an agent chooses. That design carries three real limits.

First, someone still has to pick the right one. The feature doesn't read the ticket and decide which template fits — an agent parses the question, remembers the library, and selects. On a busy queue that's cognitive load, and newer agents often don't know a perfect template exists.

Second, placeholders personalise the wrapper, not the answer. {{ticket.requester.name}} fills in a name, but it can't fill in "your order shipped this morning and arrives Thursday." The moment a reply needs a real fact from your order system or knowledge base, a canned response can't supply it — it can only leave a blank for the agent to research and type.

Third, anything non-standard falls straight through. Templates cover the predictable FAQs beautifully; they do nothing for the long tail of one-off questions, which is often where the most time goes.

This is the seam where an AI agent layer fits, and it's worth weighing the build-versus-buy tradeoff before you reach for one. The broader category of AI agents for customer service exists to do the reasoning a template can't: understanding the question, retrieving the actual answer, and drafting a reply grounded in your real data. Macha is one such layer — it runs on top of the Freshdesk you already use as a native connector, and it does not replace your help desk or your canned responses. You connect Macha to Freshdesk with your subdomain and API key, and it reads and writes the same tickets your templates already serve: drafting grounded replies for the tickets no template fits, and looking up order or account status through a custom tool that turns a REST API into something the agent can call — so the fact the placeholder couldn't supply gets filled in too. (Macha's connector is for Freshdesk specifically — not Freshchat, Freshservice, or Freshcaller. Credits are consumed per AI action, not per resolution — the pricing page has the breakdown.) If you'd rather see the automation angle end to end, how to automate Freshdesk with AI walks through it.

The clean division of labour: keep canned responses as your team's library of on-brand, high-frequency replies, and layer an agent on top for the two things a template can't do — decide which answer a ticket needs, and supply the facts that make the answer true.

FAQ

Where do I set up canned responses in Freshdesk? Go to Admin → Agent Productivity → Canned Responses (or, on the Customer Service Suite, Admin Settings → Configuration and Workflows → Ticket Canned responses). Create a New Folder first, then add a New Canned Response inside it with a title, a message body, and a sharing setting.

How do I add a customer's name to a canned response? Use a dynamic placeholder. Insert {{ticket.requester.firstname}} for a first-name greeting or {{ticket.requester.name}} for the full name via the insert-placeholder control above the editor. It resolves to the real value when an agent inserts the response into a live ticket.

Can I share canned responses with the whole team? Yes. Each response has an Available for setting: Myself (private Personal folder), All agents (visible account-wide), or Agents in group (scoped to one or more specific groups). Choose All agents for canonical team answers and Agents in group for department-specific ones.

Are canned responses available on every Freshdesk plan? Canned responses are available across Freshdesk's plans, including Free. A few advanced placeholders (for example {{ticket.billable_hours}} or {{ticket.total_time_spent}}) depend on plan or feature availability, so confirm those against your own plan.

Can I add AI on top of canned responses without replacing Freshdesk? Yes. An AI agent layer like Macha connects to Freshdesk as a native connector and runs on top of your existing help desk and its canned responses — it doesn't replace them. It drafts grounded replies for the tickets no template fits and retrieves real facts through custom tools, while your canned-response library stays the source of your standard, on-brand answers.

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