Freshdesk Automations Worth Building
Freshdesk automation splits by when the rule runs. Getting that split right is most of the skill.
The three kinds of Freshdesk automation
Picking the wrong one is the usual cause of a rule that "doesn't fire". A rule that should react to a change will never run if you built it on creation.
The five rules most teams should have
Where the rule engine stops
Every Freshdesk rule evaluates one ticket. There's no condition that expresses "there's another open ticket from this person that says the same thing", which is why duplicate merging can't be built here.
You can tag likely duplicates by keyword and route them to a review queue, and teams do. It catches the obvious ones and creates a queue somebody has to work. See auto merging in Freshdesk for the version that does not.
Frequently asked questions
What's the fastest way to automate Freshdesk?
Start with the dispatcher rules that fire on creation. To automate Freshdesk sensibly you get routing and acknowledgement right first, then add time-triggered rules for chasing and closing.
Why is my Freshdesk automation not firing?
Usually it's built as the wrong type. Creation rules never react to later changes, and update rules never run on arrival.
Can Freshdesk automations merge tickets?
No. Rules act on a single ticket, and merging is a decision about two.
Add the rule Freshdesk can't express
Ticket Merger compares each arriving ticket against the whole open queue, then merges natively.
Start free trial14-day free trial. No credit card required.