Freshdesk scenario automations: how to set them up (and where they stop)

What are Freshdesk scenario automations?

A scenario automation is a macro. You define an ordered list of actions once, give it a name, and from then on any agent can apply that whole list to a ticket in a single action. The classic example from Freshdesk's own docs: instead of repeating "tag the ticket as Refund, assign it to the Refunds group, and set the status to Processing Refund" by hand, you "create a macro command using Scenarios and execute them in a single action."

The important thing to get straight up front is that scenarios are manual and agent-triggered. They sit alongside Freshdesk's other automation layer, the background automation rules (Ticket Creation, Ticket Updates, and Hourly Triggers) that fire on their own when something happens to a ticket. Scenarios don't fire on their own. They wait for an agent to click them.

If you've used Zendesk, scenarios are basically Freshdesk's take on macros: a reusable shortcut for the multi-step grunt work agents repeat dozens of times a day.

Scenario automations vs automation rules: which one do you actually want?

This trips people up constantly, so it's worth being precise. The two features sound similar and they share a lot of the same actions, but they solve different problems.

The rule of thumb we'd use: if a human needs to look at the ticket and make a judgement before the actions run, it's a scenario. If the logic is unambiguous and should just happen, it's a rule.

Routing every "payment failed" ticket to your billing group the moment it arrives? That's a ticket creation rule, and Freshdesk will run all matching rules top to bottom if you flip the "Execute all matching rules" setting.

But "this looks like a duplicate of last week's escalation, tag it, set it to problem, and push it to QA"? A human has to make that call, so a scenario is the right tool. For the fully automatic side of the house, our guides on ticket triage and working with ticket tags go deeper.

How to set up a scenario automation in Freshdesk

Here's the actual flow. It takes about two minutes once you know where everything lives.

1. Open the scenario builder

Go to Admin > Agent Productivity > Scenario Automations and click New Scenario. Give it a name and a short description. The name is what agents will see in the dropdown, so make it obvious ("Process refund", "Escalate to QA", "Mark as spam and close") rather than clever.

2. Add your actions, in order

Click Add new action and stack the steps you want the scenario to perform. Per the Freshdesk scenario docs, the available actions are:

• Set priority, type, or status
• Set Reply (prefills a canned reply for the agent to review, it does not auto-send)
• Add Note (public or private)
• Add Tag and Add Watcher
• Assign to agent, group, or product
• Send Email to a group, agent, or requester
• Delete the ticket or Mark as Spam
• Set Reference Number

So a "Process refund" scenario might be: set type to Refund, set status to Processing Refund, assign to the Refunds group, and add a refund tag. Four manual clicks collapse into one.

3. Set who can use it, then save

Under Available for, choose whether the scenario is visible to just you, all agents, or a specific group. Admins can fine-tune personal-versus-shared scenario permissions through Admin > Roles. Save, and it's live.

4. Run it (one ticket or in bulk)

Agents apply a scenario from a ticket via More actions > Execute scenarios. You can also bulk-execute a scenario across several selected tickets straight from the Tickets list, which is the underrated part, clearing a backlog of 30 misrouted tickets becomes one select-all-and-click. One quirk worth knowing: the Set Reply action only works from the Ticket Details page, not the ticket list.

A quick plan note: scenario automations aren't on the Free plan. They start on Growth ($19/agent/month annually) and carry through Pro and Enterprise. If you're still deciding whether Freshdesk is the right home for this, our roundup of Freshdesk alternatives is a useful sanity check.

What scenarios are good at

Used well, scenarios take a real bite out of the repetitive load that grinds support teams down. And that load is the whole reason teams come looking for automation in the first place. As one support leader put it in a case study about scaling a small team:

"As a fast-growing startup with a small team, our customers far outnumber our employees. It's crucial that we have robust self-service solutions as well as tools to supercharge the efficiency of our client-facing teams."

Jon Miron, Director of Support & Operations, Yellowdig (eesel case study)

The scenarios that earn their keep tend to fall into a few buckets:

• Standardised triage. A scenario that sets type, priority, and group for a known ticket category keeps your queue consistent no matter which agent picks the ticket up. It pairs well with proper ticket triage habits.
• Refunds, returns, and other workflow tickets. Anything with a fixed set of fields-to-update is a textbook scenario, the same shape as building reusable macro templates for refunds and shipping issues.
• Spam and bulk cleanup. Mark as spam plus close, run in bulk across a flood of junk tickets.
• Escalation handoffs. Set the type, add an internal note, assign to the specialist group, and add a watcher, all in one move.

If most of your volume is this kind of structured, repetitive work, scenarios are a quick win and you should set up a handful today. They're a solid step up from doing everything by hand, and a natural companion to Freshdesk's automatic automation rules.

Where scenario automations hit a ceiling

Here's the honest part. Scenarios make a repetitive task faster, but they don't make it go away. Three limits show up the moment you try to push them harder:

A human still has to trigger every one. The agent has to open the ticket, read it, work out which scenario applies, and click. On a queue of 500 repetitive tickets a day, that's 500 acts of human judgement and 500 clicks. The toil shrinks, it doesn't disappear.

They apply preset actions, they don't think. A scenario can set a status and prefill a canned reply, but it can't read what the customer actually asked, pull their live order data, or write a response tailored to their specific problem. The "Set Reply" action drops in a fixed template that the agent still has to review and send.

They can't decide. Scenarios have no notion of "this ticket is straightforward, handle it, but that one's tricky, leave it for a human." Every routing decision is yours to make.

This is exactly the gap between a rule-based system and an AI agent. Rules and scenarios are deterministic: if X, do Y, and a person decides when X is true. An AI agent reads the ticket, figures out X for itself, and takes Y, while knowing when to back off and hand to a human. Most teams discover this ceiling about a month into scenario-heavy workflows, when the click-fatigue sets back in even though every individual action is "automated."

Try eesel for Freshdesk

eesel sits on top of Freshdesk and does the part scenarios can't: it reads each incoming ticket, decides which actions fit, drafts a reply in your team's voice, and only escalates the ones it isn't confident about. Think of it as a scenario that triggers itself, judges the ticket, and writes the response, instead of waiting for an agent to click.

The differentiator that matters most here is control. You're not flipping a switch and hoping the AI answers everything; you tell it, in plain language, exactly which tickets it's allowed to handle and where to draw the line. That's the thing support leaders ask for first, the freedom to let AI own the confident, repetitive tickets while every uncertain one is left untouched for a person. eesel trains on your past Freshdesk tickets and existing docs, so it sounds like your team from day one, and you can run it in copilot mode (drafts for agents to send) before ever letting it reply on its own.

Pricing is usage-based with no per-seat fees, so it scales with tickets handled rather than headcount, and there's a free trial if you want to point it at your real Freshdesk queue and see what it resolves. If scenario automations got you most of the way and you've hit the click-fatigue wall, that's the next step worth taking toward real automated ticket resolution.