Scenario Automations are the underused power tool of Freshservice. Unlike Workflow Automator (event-triggered), scenarios are agent-triggered: one click runs a sequence of actions on the current ticket. They cut click-fatigue on repetitive patterns dramatically.
When scenarios beat workflows
Use a scenario when:
- The action depends on agent judgment (cannot be auto-triggered).
- Multiple steps happen at once and the agent does them every day.
- The actions are conditional on agent context, not data.
Use a workflow when:
- The trigger is an event, not a person.
- The conditions are deterministic.
- It runs without agent involvement.
Both can call each other; scenarios can trigger workflows by changing fields that workflows watch.
Common useful scenarios
Triage scenarios (turn an unrouted ticket into a triaged ticket):
- Assign to right group.
- Set priority based on description.
- Add an internal note with triage rationale.
- Add tags.
- Send acknowledgment to requester.
One scenario, one click, five actions. Without it, agents do five clicks per ticket.
Resolution scenarios (close out common issues):
- Set status to Resolved.
- Apply the right resolution template (canned reply).
- Set resolution code (root cause field).
- Schedule a follow-up reminder.
- Update related asset record if applicable.
For “password reset done” tickets that come in 50 a week, a scenario saves 250 clicks weekly per agent.
Building a scenario
Admin, Scenarios, New Scenario. Pick the module (Tickets, Changes, Releases). Add actions in sequence. Each action is a field change, note, or workflow trigger.
The actions run in order; later actions can depend on earlier actions’ results. Field changes are atomic at scenario completion (not interleaved with manual edits).
Scenario visibility
Scope each scenario to specific groups. The “Password reset done” scenario should appear only in the IT helpdesk group, not in HR or Facilities. Agents in other groups never see irrelevant scenarios.
Less choice = faster execution. Agents do not scroll through 40 scenarios looking for the right one.
Naming and discoverability
Scenarios appear in a dropdown on the ticket. Name them as actions (“Resolve - Password Reset,” “Triage - VIP Escalate,” “Close - Spam Report”). Sort alphabetically; the agent finds them by typing the first few letters.
Avoid creative names. The scenario list is not a place for personality.
Auditing scenario usage
The activity log on each ticket shows which scenarios ran. Build a report: count of scenario invocations per scenario per agent per week.
High-usage scenarios are doing their job; zero-usage scenarios are dead weight. Retire after 90 days of no use.
If one scenario is used by everyone except one agent, that agent needs training (or the scenario is the wrong fit for their workflow).
Limitations
Scenarios cannot:
- Read external data via API (use a workflow with webhook for that).
- Run on multiple tickets at once (no bulk scenarios; use bulk actions).
- Branch conditionally (the actions all run; build separate scenarios for different cases).
The lack of branching is the biggest constraint. Agents pick the right scenario; the scenario does not pick the right behavior.
Promoting scenarios in onboarding
New agent onboarding should walk through every active scenario in their group. Scenarios are the highest-leverage productivity tool; an agent who does not know they exist is doing 5x the clicks.
Print a one-page cheat sheet of “scenarios for your group” and have agents reference it for the first 30 days.
What to do this week
Sit with two senior agents and watch them work for 30 minutes. Note the multi-click patterns they do repeatedly. Build one scenario for the most common pattern. Roll out and measure clicks saved per week.
