How to automate ticket routing in Freshdesk

How to Automate Ticket Routing in Freshdesk

Freshdesk provides three automation layers for ticket routing: Ticket Creation rules (Dispatch), Time-Triggered rules (Supervisor), and Event-Triggered rules (Observer). As of April 2026, automation is available on all Freshdesk plans, with advanced automation features on Pro ($49/agent/month) and Enterprise ($79/agent/month).

Step 1: Access Automation Settings

Navigate to Admin > Automations (under Helpdesk Productivity). Three automation tabs are available:

• Ticket Creation (Dispatch Rules) — Run once when a ticket is first created
• Time Triggers (Supervisor Rules) — Run on a schedule checking ticket conditions
• Ticket Updates (Observer Rules) — Run when a ticket property changes

Step 2: Create a Dispatch Rule for New Ticket Routing

Click "New Rule" under Ticket Creation. Define conditions:

• Subject or Description contains — Route by keyword ("billing" → Billing team, "bug" → Engineering)
• Source is — Route by channel (email, chat, phone, social)
• Type is — Route by ticket type (Question, Incident, Problem, Feature Request)
• Contact group is — Route VIP customers to a priority team
• Product is — Route to product-specific support groups

Conditions combine with AND/OR logic. Matching is case-insensitive.

Step 3: Define Assignment Actions

Set what happens when the conditions match:

• Assign to Agent — Route to a specific agent
• Assign to Group — Route to a team (Freshdesk assigns to the least-busy agent in the group using round-robin)
• Set Priority — Auto-set priority based on keywords or customer tier
• Set Status — Change ticket status (for example, auto-close spam tickets)
• Add Tag — Apply tags for reporting and further automation
• Send email to group — Notify a team when tickets match certain criteria

Step 4: Set Up Time-Based Escalation (Supervisor Rules)

Switch to the Time Triggers tab and create escalation rules:

• "If ticket is unassigned for more than 2 hours AND priority is Urgent, assign to Support Manager"
• "If ticket has no response for more than 4 hours AND SLA is breached, escalate to Team Lead"
• "If ticket is pending customer response for more than 7 days, set status to Resolved"

Time triggers run hourly, checking all tickets that match the defined conditions.

Step 5: Enable and Order Rules

Activate each rule by toggling it to "Enabled." Rules execute in order from top to bottom; only the first matching rule runs for Dispatch rules. Drag rules to reorder them by priority.

Practical Example: Multi-Tier Support Routing

1. Rule 1: If Product is "Enterprise" AND Contact is VIP → Assign to Enterprise Support Group, Set Priority Urgent
2. Rule 2: If Subject contains "billing" or "invoice" or "payment" → Assign to Billing Group
3. Rule 3: If Type is "Bug" → Assign to Engineering Support Group, Add Tag "bug-report"
4. Rule 4: Default → Assign to General Support Group using round-robin

This ensures enterprise customers receive priority treatment, billing queries reach the right team, and all other tickets are evenly distributed.