Freddy AI is enabled on thousands of Freshservice instances that see little to no ROI from it. The problem is almost never the feature — it is the configuration underneath it. Here are the six reasons Freddy underperforms, and what to do about each one.
Skip the manual diagnosis
Connect your Freshservice account and get a scored breakdown of all six areas in under 2 minutes.
Freddy chatbot and article suggestions draw directly from your KB. If article coverage is below 50% of your common ticket types, articles are more than 6 months old, or there is significant duplication, Freddy cannot surface useful answers.
Symptoms
Fix
Audit which ticket types lack KB articles. Write or update articles for your top 10 recurring request types. Set a 6-month freshness review cycle.
Freddy auto-triage needs at least three levels of categorisation (category → subcategory → item) to route accurately. Flat trees, inconsistent naming, and unused legacy categories all erode triage quality.
Symptoms
Fix
Build a 3-level hierarchy. Retire categories unused in the last 90 days. Standardise naming: Service Area → Function → Item.
Freddy AI surfaces canned responses as agent suggestions. If there is no response for a ticket type, Freddy suggests nothing. Duplicate responses with similar wording create conflicting suggestions that agents stop trusting.
Symptoms
Fix
Map one canned response per top-20 ticket category. Deduplicate responses with more than 85% content overlap. Create a tone and format standard.
Freddy AI prioritisation relies on SLA policies to determine urgency. A single catch-all SLA policy means Freddy cannot distinguish priority by service context. Missing escalation rules on P1 and P2 tickets leave critical issues without automated action.
Symptoms
Fix
Create service-specific SLA policies aligned to your service catalogue. Add escalation rules on all P1 and P2 policies. Review breach thresholds against actual business impact.
Freddy auto-assignment improves over time by learning from your historical routing decisions. If most tickets are manually assigned rather than routed through rules, Freddy has poor training data and assignment accuracy stays low.
Symptoms
Fix
Configure automated routing rules in Freshservice before relying on Freddy assignment. Reduce manual overrides. Freddy learns from rule-based routing data more reliably than manual decisions.
Freddy AI self-service and request fulfilment features need items in the service catalogue to route against. Admins with fewer than 10 catalogue items effectively block AI-assisted request fulfilment for end users.
Symptoms
Fix
Build out your service catalogue to cover at least your top 15 recurring request types. Link each item to an SLA policy. Use Freddy service item suggestions to guide end users.
The six issues above apply to most Freshservice instances — but typically two or three are the dominant cause of underperformance. Diagnosing which ones apply to your specific instance requires pulling data from your Freshservice account and scoring it against the thresholds Freddy needs.
Connect your instance
Enter your Freshservice subdomain and API key. Read-only — nothing is written to your account.
We scan 6 dimensions
KB coverage, categories, canned responses, SLAs, routing, and service catalogue — all in under 2 minutes.
Get your scored report
An overall AI readiness score plus the top issue in each dimension. Free. No credit card.
Freddy AI depends on what is underneath it in your Freshservice instance. If your knowledge base has thin coverage, your ticket categories are flat or inconsistent, your canned responses have gaps, your SLA policies are incomplete, your routing relies on manual assignment, or your service catalogue is sparse — Freddy will underperform regardless of which plan tier you are on. Enabling the feature and getting value from it are two separate things.
Freddy chatbot deflects tickets by surfacing relevant knowledge base articles in response to user queries. If your knowledge base has fewer than 50 articles, article coverage does not match your most common ticket types, articles are out of date, or there is significant duplication, the chatbot will fail to find useful answers and deflection rates will be very low.
Freddy auto-triage learns from your ticket category structure. Flat category trees (no subcategories), inconsistent naming, legacy categories no longer in use, and a high percentage of tickets left at the top-level category all degrade routing accuracy. Freddy needs clean, consistent category data to route reliably.
Run an AI readiness audit to identify the specific gaps. The audit checks your knowledge base coverage, ticket category structure, canned response library, SLA configuration, routing rules, and service catalogue — and scores each one against the thresholds Freddy needs to perform. The free audit shows the top issue in each area; the full Readiness Blueprint gives all 18 issues with specific fix instructions.
The free audit connects to your Freshservice account, scores all six dimensions, and shows you the top configuration issue in each area — in under 2 minutes.
Run your free auditFree · Read-only · Under 2 minutes