Freshservice ticket deflection: A complete guide for IT teams

Stevia Putri

Stanley Nicholas
Last edited March 11, 2026
Expert Verified
Every IT team knows the feeling. Tickets pile up faster than agents can handle them. Password resets, software access requests, and "how do I..." questions clog the queue while complex issues wait. Ticket deflection is how you'll break this cycle.
Ticket deflection means reducing support volume by helping employees resolve issues themselves before they ever create a ticket. The math is simple: if your help center handles four self-service interactions for every ticket submitted, your deflection rate is 4:1. That translates to less agent burnout, faster resolution times, and lower support costs.
For Freshservice users, the platform offers several built-in ticketing and automation mechanisms to achieve this. But setting them up effectively requires understanding how each tool works and where it fits in your deflection strategy.
What is ticket deflection and why it matters
Ticket deflection is a customer service strategy that reduces the number of support tickets by providing self-service resources. These include AI-powered chatbots, knowledge bases, FAQ pages, and automated email responses that help users find answers without agent intervention.
Here's why it matters for IT teams:
- Reduced agent workload: When employees solve their own password resets or software questions, agents can focus on complex issues that actually need human expertise
- Faster resolution: Self-service happens instantly. There's no waiting for an agent to pick up the ticket
- Cost savings: Fewer tickets mean you can support more employees without proportionally scaling your team
- 24/7 availability: Self-service doesn't sleep, take breaks, or call in sick
The formula for measuring success is straightforward: Ticket deflection rate = Total users of your help center ÷ Total users in tickets. A rate of 4 means for every four people who self-serve, only one's submitting a ticket.
Industry benchmarks vary, but deflection rates of 20-30% are common for mature knowledge bases. AI-powered deflection can push this significantly higher. Learn more about measuring and improving deflection rates.
Freshservice deflection mechanisms overview
Freshservice offers three primary tools for ticket deflection, each serving different channels and use cases:
Email Bot handles email-based deflection by automatically suggesting relevant solution articles when employees email the service desk. It works within the existing email workflow without requiring employees to visit a portal.
Freddy AI Agent provides conversational deflection through chat interfaces. Employees ask questions in natural language, and the AI either answers directly or creates a ticket if it can't help.
Knowledge Base with Auto-Suggest is the foundation. A well-organized knowledge base powers both the Email Bot and Freddy AI. The auto-suggest feature recommends articles as employees type ticket subjects.
These tools work together for multi-channel coverage: email, chat, and portal. But there's an important caveat: advanced AI features like Freddy AI Agent and Email Bot are only available on Enterprise plans ($99/agent/month) or Pro plans with add-ons. The knowledge base auto-suggest is available on lower tiers. Check the full Freshservice pricing for details.
Setting up the Email Bot for automatic deflection
The Email Bot (also called Smart Article Suggestions) automatically analyzes incoming emails and suggests relevant solution articles in the ticket acknowledgment email. Here's how to set it up:
Step 1: Enable Email Bot
Navigate to Admin → Freddy AI → Freddy Self Service and toggle on the Email Bot feature.

Step 2: Configure solution article matching
The Email Bot uses machine learning to match email content to your knowledge base articles. It automatically selects up to three relevant articles based on the issue described. There's no manual training required: the system learns from your existing articles.
Step 3: Customize the acknowledgment email
Head to Settings → Email Notification → Requester Notification → New Ticket Created. Add or verify the {{solution_url}} placeholder is present. This placeholder appends the suggested articles to the acknowledgment email.
If you remove this placeholder, suggestions won't be added.
How it works in practice
- An employee emails the IT helpdesk about a VPN issue
- Freshservice creates a ticket and sends an acknowledgment email
- The Email Bot analyzes the ticket content using ML
- Up to three relevant solution articles are included in the acknowledgment
- The employee clicks an article link and potentially resolves their issue without agent involvement
Best practices for maximizing email deflection:
- Keep knowledge base articles current and comprehensive (the Bot can only suggest what exists)
- Write clear, descriptive article titles (the Bot uses these for matching)
- Monitor which articles get clicked and which don't to identify content gaps
- Track deflection metrics to measure impact
Note that Email Bot is currently in Beta and requires an Enterprise plan.
Configuring Freddy AI Agent for conversational deflection
Freddy AI Agent takes deflection further by enabling conversational interactions. Instead of just suggesting articles, it can answer questions directly, guide employees through troubleshooting, and even resolve certain requests on its own.
Requirements
- Enterprise plan ($99/agent/month) or Pro plan with AI Agent add-on
- Admin privileges
- A populated knowledge base to train the AI
Step 1: Enable Freddy AI Agent
Navigate to Admin → Freddy AI → Freddy AI Agent and enable the feature.

Step 2: Configure knowledge sources
Select which content the AI can access:
- Solution articles from your knowledge base
- Service catalog items
- Common request types
- Approved documentation
The quality of AI responses depends heavily on the quality and completeness of these sources.
Step 3: Set confidence thresholds
Configure when the AI should attempt to answer versus escalate to a human. Higher confidence thresholds mean the AI only responds when it's very certain. Lower thresholds increase deflection but may result in less accurate responses.
Step 4: Customize the AI persona
Adjust the tone and communication style to match your organization's voice. Configure greeting messages, closing statements, and fallback responses for when the AI cannot help.
Step 5: Deploy across channels
Freddy AI Agent works across multiple channels:
- Chat (web widget)
- Microsoft Teams
- Slack
Configure each channel based on where your employees prefer to get help.
Key metrics to track
Freshservice provides a dedicated Freddy AI Agent Overview report with these metrics:
| Metric | Definition |
|---|---|
| Ticket Deflection Rate | Percentage of queries resolved without human help |
| Total Conversations | Back-and-forth exchanges between employee and AI |
| Resolved Conversations | Successfully deflected issues without ticket creation |
| Conversations Converted to Tickets | Escalated to human agents |
| Top Resolved Topics | What's working well |
| Top Unanswered Topics | Content gaps to fill |
Access this at Reporting → Analytics → Curated Reports → Freddy AI Agent Overview. See the Freddy AI Agent documentation for more details.
Building a deflection-ready knowledge base
All deflection tools depend on one thing: a comprehensive, well-organized knowledge base. Without good content, even the best AI can't assist effectively.
Freshservice uses a three-level hierarchy:
| Level | Purpose | Example |
|---|---|---|
| Category | Broad topic areas | IT Support, HR Policies, Finance |
| Folder | Specific sub-topics | Password Reset, Email Issues |
| Article | Individual solutions | "How to reset your Active Directory password" |
Step 1: Organize your content
Create categories and folders that match how employees actually think about their issues. An employee looking for VPN help should find it under "Remote Access" or "Network" without having to guess.
Step 2: Enable auto-suggest
Go to Admin → Global Settings → Channels → Other Channels → Support Portal and enable "Auto suggest solutions while creating a new ticket." This displays relevant articles based on the subject line as employees type.
Step 3: Create high-impact articles
Start with your most common ticket types. Look at your ticket data to identify:
- Password resets
- Software installation requests
- Access provisioning
- Common error messages
- How-to questions
Each article should:
- Have a clear, searchable title
- Include step-by-step instructions
- Use screenshots where helpful
- Link to related articles
Best practices for knowledge base success
- Scale matters: Aim for 50+ articles before expecting measurable deflection
- Regular reviews: Set review dates to keep content current
- Link to problems: Connect solutions to problem records for known errors
- Monitor failed searches: These indicate content gaps
- Use external document search: Link to external documentation without duplicating content
Measuring and optimizing your deflection strategy
Implementing deflection tools is just the start. Continuous optimization based on data is what'll drive results.
Key metrics to track
| Metric | How to Calculate | Target |
|---|---|---|
| Ticket Deflection Rate | Help center users ÷ ticket submitters | 4:1 or higher |
| Self-Service Score | Total deflected ÷ total tickets | 20-30%+ |
| Article Click-Through Rate | Clicks ÷ impressions | Varies by article |
| Resolution Time | Time to resolve (deflected vs. agent-handled) | Faster for deflected |
| Employee Feedback | Thumbs up/down on AI responses | Track trends |
Where to find reports
Freshservice provides several reporting options:
- Freddy AI Agent Overview: Deflection rates, conversation trends, top topics
- Knowledge Base Analytics: Article views, search terms, failed searches
- Ticket Volume Trends: Overall volume changes over time
Optimization strategies
-
Expand successful topics: If "password reset" has high deflection, ensure comprehensive coverage of all password scenarios
-
Fill knowledge gaps: Top unanswered topics indicate where employees need help but can't find it
-
Adjust confidence thresholds: If escalation rates are high, lower thresholds (if answer quality remains good). If accuracy suffers, raise them
-
A/B test article versions: Try different titles, structures, or content to see what drives more self-resolution
-
Review weekly: Set a recurring calendar block to review metrics and identify improvement opportunities
When to consider alternatives like eesel AI
Freshservice's native deflection tools work well if you're already invested in the platform. But they've got limitations worth considering:
Plan restrictions: Advanced AI features like Freddy AI Agent require Enterprise plans at $99/agent/month. For a team of 20, that's $1,980 monthly just for the platform, before considering implementation and maintenance.
Ecosystem lock-in: The tools only work within Freshservice. If you use multiple help desks or plan to migrate later, your deflection investment won't transfer.
Setup complexity: Configuring Freddy AI Agent involves multiple steps, threshold tuning, and ongoing optimization. It's not a "set it and forget it" solution.
Limited to ITSM: Freshservice is built for IT service management. If you need deflection for customer support, sales, or other use cases, you'll need separate tools.

This is where we come in. At eesel AI, we take a different approach to ticket deflection:
Works across platforms: Our AI integrates with Freshservice, Zendesk, Intercom, and 100+ other tools. You're not locked into one ecosystem.
Instant learning: Connect eesel to your help desk and it learns from past tickets, help centers, and connected docs in minutes. No manual training or configuration wizards.
Progressive rollout: Start with eesel drafting replies for agent review. As it proves itself, expand to sending replies directly. Eventually, it handles full frontline support. You control the pace.
Plain-English control: Define escalation rules and behavior in natural language. "Always escalate billing disputes to a human" or "For VIP customers, CC the account manager." No complex workflows.
Pre-go-live testing: Run simulations on thousands of past tickets before going live. See exactly how eesel would respond and measure quality before touching real customers.
Pay per interaction: Our pricing starts at $299/month for 1,000 interactions, not per seat. A 20-person team pays the same as a 5-person team if their ticket volume's similar.
If you're considering Freshservice's AI features but want to explore alternatives, or if you're already using Freshservice and hitting limitations, our AI agent might be worth a look.
Frequently Asked Questions
Share this post

Article by
Stevia Putri
Stevia Putri is a marketing generalist at eesel AI, where she helps turn powerful AI tools into stories that resonate. She’s driven by curiosity, clarity, and the human side of technology.


