Freshdesk Ticket Routing Intelligence
Weekly AI audit of your Freshdesk ticket routing rules — measures overall accuracy, identifies worst-performing rules, quantifies misroute cost in resolution time, and recommends prioritized fixes.
Weekly aggregate routing rule effectiveness audit from Freshdesk resolved ticket data. 26-node main workflow + 3-node scheduler. 5-dimension routing effectiveness taxonomy. SINGLE-MODEL Sonnet 4.6. 4 agents. Dual-channel delivery: Notion audit brief + Slack digest.
Four Agents. Weekly Routing Audit. Zero Manual Analysis.
Step 1 — The Fetcher
Code-only
Retrieves resolved tickets with assignment and reassignment history from Freshdesk API using paginated calls across the configurable lookback window.
Step 2 — The Assembler
Code-only
Identifies misrouted tickets by reassignment chain analysis. Computes per-rule accuracy, resolution time delta between correct and misrouted tickets, CSAT correlation, and 5-dimension routing effectiveness metrics.
Step 3 — The Analyst
Classification
Performs AGGREGATE routing effectiveness analysis across 5 dimensions: overall accuracy, worst rules, misroute cost, CSAT impact, and fix prioritization. Flags rules below 50% accuracy as REWRITE. Triggers urgent alert if overall accuracy drops below 70%.
Step 4 — The Formatter
Creative
Generates a Notion routing audit brief with per-rule breakdowns and a Slack digest highlighting the top 3 highest-impact routing fixes with expected hours saved and CSAT improvement.
What It Does NOT Do
Does not cluster support topics — use Support Pattern Analyzer (#18) for topic clustering and trend identification
Does not predict SLA breach risk — use Freshdesk SLA Risk Predictor (#45) for forward-looking per-ticket SLA predictions
Does not score individual agent performance — use Freshdesk Agent Performance Intelligence (#50) for per-agent coaching briefs
Does not measure customer effort — use Freshdesk Customer Effort Scorer (#49) for CES scoring
Does not modify routing rules automatically — this is an analysis tool that recommends changes for human review
Does not work with non-Freshdesk helpdesks — this is Freshdesk-specific
The Complete Customer Success Bundle
6 files.
Tested. Measured. Documented.
Weekly 5-dimension routing rule effectiveness audit with misroute cost quantification and dual-channel delivery (Notion audit brief + Slack digest with top 3 fixes).
Freshdesk Ticket Routing Intelligence v1.0.0───────────────────────────────────────────────Nodes 26 (main) + 3 (scheduler)Agents 4 (Fetcher, Assembler, Analyst, Formatter)LLM Calls 2 per run (Analyst + Formatter)Model Sonnet 4.6 (SINGLE-MODEL)Trigger Schedule (weekly Monday 8:00 UTC) + WebhookPattern AGGREGATE (weekly batch)Tool A Freshdesk (httpHeaderAuth) — resolved tickets with assignment historyTool B Notion (httpHeaderAuth) — routing audit briefTool C Slack (httpHeaderAuth) — digest with top 3 routing fixesITP 8 variations, 14 milestonesBQS 12/12 PASSCost $0.03–$0.10 per run
What You'll Need
Platform
n8n 2.7.5+
Est. Monthly API Cost
~$0.03-0.10 per weekly run + Freshdesk subscription.
Credentials Required
- ▪Anthropic API
- ▪Freshdesk (httpHeaderAuth, Basic auth)
- ▪Notion (httpHeaderAuth Bearer)
- ▪Slack (Bot Token, httpHeaderAuth Bearer)
Services
- ▪Freshdesk account with API access
- ▪Anthropic API key
- ▪Notion workspace
- ▪Slack workspace (Bot Token with chat:write)
Setup Track
Quick Start
~15 min
All credentials live, n8n running
Full Setup
1–2 hrs
Needs API config + tables
From Scratch
2–4 hrs
No n8n, no credentials
Freshdesk Ticket Routing Intelligence v1.0.0
$199
one-time purchase
What you get:
- ✓26-node main workflow + 3-node scheduler
- ✓Weekly routing rule effectiveness audit from Freshdesk resolved ticket data
- ✓5-dimension routing effectiveness taxonomy: overall accuracy, worst rules, misroute cost, CSAT impact, fix prioritization
- ✓Automatic misroute identification by reassignment chain analysis
- ✓Per-rule accuracy scoring with REWRITE flags for rules below 50%
- ✓Misroute cost quantification in resolution hours
- ✓CSAT correlation analysis between correctly routed and misrouted tickets
- ✓Top 3 prioritized routing fixes with expected impact (tickets affected, hours saved, CSAT improvement)
- ✓Urgent alert when overall routing accuracy drops below 70%
- ✓Notion routing audit brief with per-rule breakdowns
- ✓Slack digest with top 3 routing fixes and key metrics
- ✓Configurable lookback window, misroute threshold, and alert thresholds
- ✓Full technical documentation + system prompts
Frequently Asked Questions
What are the 5 routing effectiveness dimensions?+
Overall accuracy (% tickets routed correctly on first assignment), worst rules (per-rule accuracy distribution and count below threshold), misroute cost (average additional resolution hours caused by misrouting), CSAT impact (satisfaction delta between correctly routed and misrouted tickets), and fix prioritization (ranked list of rule rewrites by combined impact). Each dimension is scored 1-10.
How does it detect misrouted tickets?+
A ticket is flagged as misrouted if it was reassigned at least MISROUTE_THRESHOLD times (default 2) and the final resolving group differs from the initially assigned group. The reassignment chain reveals where tickets actually needed to go, which informs the fix recommendations.
When does it trigger an urgent alert?+
Two alert thresholds: overall routing accuracy below 70% triggers an URGENT flag in the Slack digest with a prominent warning. Per-rule accuracy below 50% flags that specific rule as REWRITE in the Notion audit brief. Both thresholds are configurable.
How does it differ from Freshdesk SLA Risk Predictor?+
FSRP (#45) predicts SLA breach risk on open tickets — forward-looking, per-ticket. Freshdesk Agent Performance Intelligence (#50) scores individual agent performance. Freshdesk Customer Effort Scorer (#49) measures customer effort. This product audits routing rule effectiveness — retrospective, operations-focused, measuring per-rule accuracy and recommending rule rewrites.
What routing fixes does it recommend?+
The top 3 fixes are prioritized by combined impact (ticket volume x resolution time cost x CSAT delta). Each fix specifies which rule to change, what condition to add or modify (based on where misrouted tickets actually ended up), and the expected impact in tickets affected, hours saved per week, and CSAT improvement.
Does it use web scraping?+
No. All data comes from the Freshdesk API v2 (tickets endpoint with stats include). No web scraping, no page parsing.
Is there a refund policy?+
All sales are final after download. Review the Blueprint Dependency Matrix and prerequisites before purchase. Questions? Contact support@forgeworkflows.com before buying. Full terms at forgeworkflows.com/legal.
Related Blueprints
Freshdesk SLA Risk Predictor
AI-powered per-ticket SLA breach prediction that scores risk across five factors — complexity, customer tier, agent capacity, historical patterns, and escalation signals — and alerts your team before deadlines slip.
Freshdesk Agent Performance Intelligence
Weekly AI coaching briefs for every support agent — scores resolution speed, SLA compliance, CSAT, escalation rates, and throughput from Freshdesk data.
Freshdesk Customer Effort Scorer
AI-powered weekly customer effort scoring that bridges Freshdesk support data with Pipedrive deal value — identifies high-effort, high-value accounts at risk of churning before it's too late.