Playbooks 4 mins read

How to Set Up Freshservice Automations: A Step-by-Step AU Guide

Freshservice automations are one of the highest-leverage configuration tasks ANZ IT teams can complete. Most Freshservice implementations utilise 20 to 30% of the automation capability available. That gap creates real ongoing operational cost. Unnecessary manual administration. Missed escalations. Inconsistent ticket handling. Closing it delivers 25 to 35% improvement in agent productivity within 60 days.

This guide covers what to automate. It covers how to configure each automation type. It covers the deployment sequence. It covers how to validate before production rollout.

What Is Freshservice Automation?

Freshservice automation executes configured actions on tickets based on defined conditions. It triggers when tickets are created, updated or on a schedule. The Workflow Automator is the no-code automation engine. IT administrators construct automated processes without scripting. Common automation patterns include auto-assignment. SLA escalation notifications. Status updates. Approval workflows. Scheduled administrative tasks. Integration triggers. All subscription plans include automation. Pro and Enterprise plans add advanced capabilities.

The Five Highest-Value Automations to Configure First

Start with these five automation patterns. Auto-assignment by category. SLA escalation notifications. Ticket categorisation rules. Scheduled reminders for stalled tickets. Approval workflows for service catalogue items. These five deliver the bulk of operational value. Configure them within the first 30 days. Advanced automation patterns like Freddy AI-powered routing and complex multi-step workflows can follow later.

Step 1: Configure Auto-Assignment Rules

Auto-assignment routes incoming tickets to the appropriate agent or group. It routes based on category, requester or content. In Freshservice, navigate to Admin. Then Workflow Automator. Then Automations. Create rules that trigger on ticket creation. Define conditions. Category equals “Network.” Source is “Email.” Execute actions. Assign to “Network Team” group. Test with sample tickets before activation. Most ANZ mid-market implementations require 8 to 15 auto-assignment rules. These cover the highest-volume contact categories.

Step 2: Configure SLA Escalation Automations

SLA escalation automations notify agents and managers when tickets approach SLA breach. Configure under Admin. Then SLA Policies. Define escalation rules. Notify the agent 1 hour before SLA breach. Notify the manager 30 minutes before breach. Auto-reassign at breach. Test with backdated tickets. Validate the clock behaviour matches expectations.

Step 3: Build Ticket Categorisation Rules

Categorise tickets automatically based on subject keywords. Use email content or sender domain. This reduces manual triage time. It improves routing accuracy. In Freshservice, configure observer rules within Workflow Automator. They trigger on ticket creation. They evaluate subject content. They populate category fields. Combine with Freddy AI on Pro and Enterprise plans. AI-powered categorisation learns from agent corrections.

Step 4: Configure Scheduled Reminder Automations

Scheduled automations execute on time triggers. Not ticket events. Configure reminders for stalled tickets. Notify the agent if a ticket has not been updated in 48 hours. Auto-close resolved tickets after 5 days of no customer response. This reduces stale ticket clutter. It improves agent focus. Configure under Admin. Then Workflow Automator. Then Time Triggers.

Step 5: Build Service Catalogue Approval Workflows

For catalogue items requiring approval, build approval workflows in the catalogue item configuration. This applies to software requests. Hardware procurement. Access modifications. Define the approver based on the requester’s manager. Or department head. Or specific organisational roles. Configure approval timeouts. These escalate or auto-approve based on policy. Test with representative requests before publishing to end users.

How to Test Automations Before Production

Use the sandbox environment available on Enterprise plans. Or create a separate test agent group with restricted permissions. Submit test tickets matching the automation conditions. Verify the expected actions execute correctly. Check SLA clock behaviour. Validate notifications reach the appropriate recipients. Test with at least 3 to 5 representative scenarios per automation before production activation.

Need help configuring Freshservice automations? Book a free Freshservice optimisation assessment with KlickFlow. We will identify the highest-value automation opportunities for your environment.

Frequently Asked Questions

How many automations should we have?

For ANZ mid-market implementations, 25 to 50 active automations cover the bulk of operational value. They remain manageable at that level. More than 100 typically signals automation sprawl. That produces conflicting rules. It produces unintended behaviour. Quality and governance matter more than quantity.

Can Freshservice automations operate across multiple systems?

Yes. Automations can trigger actions in integrated systems. They use the Workflow Automator’s webhook capability and platform integrations. Creating Jira issues. Posting to Slack. Updating CRM records. Triggering Power Automate flows. Available on Pro and Enterprise plans.

How long does setup take?

For the five high-value patterns above, expect 2 to 3 weeks of configuration and testing for ANZ mid-market implementations. Building the full automation library takes 4 to 6 weeks. Maintenance and refinement is ongoing. The team identifies new opportunities over time.

What to Do Next

Book a free Freshservice optimisation assessment with KlickFlow. We will identify the highest-value automation opportunities for your environment. No obligation.

Sources