Route New Freshdesk Tickets With Ordered Automation Rules

Ticket creation rules can assign new work before an agent opens it. Design the order around the most specific condition and measure how your first-match or all-match setting behaves.

Worked example

Test three incoming cases

Subject = Duplicate charge on order 401. Type = Billing → Payments disputes
Subject = Can I have a receipt? Type = Billing → Billing questions
Subject = Product arrives scratched. Type = Product → Regular intake

Steps

  1. List the routing inputs that exist on creation, such as the submitted ticket type and subject. Decide which request type takes priority when two rules match.
  2. Create a narrow rule for duplicate or incorrect charges and a broader rule for billing questions. Give each a group assignment that staff can verify.
  3. Choose a matching mode and order the rules deliberately. In a first-match setup, put the catch-all Billing rule after the Payments dispute rule.
  4. Create one ticket per rule and a dual-match ticket. Check the actual assignment on each case and inspect activity to confirm which rule ran.

What to check

  • Create fresh sample tickets. Editing an old one is a different event from ticket creation.
  • Check strong and weak signals together. A receipt request that quotes a previous dispute can trigger a subject-based rule unexpectedly.

View Freshdesk

References