The Freshservice chatbot (Freddy AI) can significantly reduce ticket volume — but only if the configuration underneath it is ready. This guide covers the prerequisites, the pre-go-live checklist, and how to diagnose your readiness before switching it on.
Check readiness before go-live
The free AI readiness audit scores your knowledge base, categories, and service catalogue against Freddy's requirements — in under 2 minutes.
Knowledge base
RequiredThe chatbot deflects tickets by surfacing relevant KB articles. Without adequate coverage, it returns generic non-answers and users log tickets regardless.
Ticket categories
RequiredChatbot-raised tickets need to route to the correct team. Flat or inconsistent categories mean Freddy cannot triage accurately, and agents end up manually reassigning.
Service catalogue
RecommendedIf you want users to raise requests through the chatbot (not just find KB articles), service catalogue items are required. Without them, the chatbot can only point users to documentation.
SLA configuration
RecommendedChatbot tickets need their own SLA treatment. Users who self-serve expect faster acknowledgement than traditional channels — a shared SLA with other channels will produce misleading breach metrics.
Instead of manually working through this checklist, connect your Freshservice account and get a scored breakdown of every prerequisite in under 2 minutes. The audit reads your configuration data directly — no ticket content, no personal data, read-only access.
Knowledge base
Article count, coverage, freshness, duplication rate
Ticket categories
Hierarchy depth, naming consistency, unused categories
Service catalogue
Item count, SLA linkage, approval configuration
The Freshservice chatbot (Freddy AI) needs three things to deliver value: a knowledge base with sufficient article coverage for your common ticket types, a service catalogue with items users can request through the chatbot, and ticket categories that allow Freddy to route chatbot-raised tickets accurately. Without these, the chatbot will give generic non-answers and ticket deflection rates will be very low.
There is no hard minimum, but meaningful deflection typically requires at least 40–60 articles covering your most common ticket types. Articles should be structured with a clear title that matches the language users would type, and updated within the last 6 months. The chatbot surfaces articles by matching user query language against article titles and content — thin or stale articles result in poor matches.
Freddy AI chatbot is configured through the Freshservice Admin panel under IT Service Management → Channels → Freddy Self Service. Before enabling it, ensure your knowledge base has adequate coverage, your service catalogue includes the items you want users to request via the chatbot, and your ticket categories are structured to handle chatbot-raised tickets correctly. Run an AI readiness audit first to identify configuration gaps before go-live.
Low chatbot deflection rates are almost always caused by knowledge base gaps. The chatbot deflects by finding a relevant KB article and presenting it to the user. If the article does not exist, is outdated, or is written for agents rather than end users, deflection fails. Secondary causes include service catalogue gaps (users cannot request through the chatbot because the item does not exist) and poor category structure (chatbot-raised tickets route to the wrong queue).
The free AI readiness audit tells you in under 2 minutes — scored across knowledge base, categories, canned responses, SLAs, routing, and service catalogue.
Run your free auditFree · Read-only · Under 2 minutes