Use Freshdesk's Freddy AI for Smarter Ticket Handling

What This Does

Freshdesk's Freddy Copilot is built into Freshdesk's ticket interface — it automatically categorizes incoming tickets, suggests responses from your KB, summarizes ticket history, and can generate complete response drafts. For help desk analysts working in Freshdesk, it reduces the cognitive load of writing responses from scratch.

Before You Start

• Your organization uses Freshdesk (Growth plan or above)
• Freddy Copilot is enabled by your Freshdesk admin (check Settings → Freddy Copilot)
• You're logged in as an agent

Steps

1. Review AI-suggested ticket categorization

1. When new tickets come in, Freshdesk's Freddy AI automatically assigns:

   • Category (hardware, software, access, network, etc.)
   • Priority (urgent, high, medium, low)
   • Suggested assignee based on ticket type
2. Review the AI's categorization in the ticket header — confirm or adjust as needed

What you should see: Auto-populated fields in the ticket. When the AI's categorization is accurate (which it usually is for common ticket types), you can skip the manual triage step entirely.

2. Use Freddy Copilot to draft a response

1. Open a ticket
2. Click in the Reply text area
3. Look for the Freddy icon or "Assist" button above the text area
4. Click Generate reply — Freddy reads the ticket and drafts a response using your KB articles

What you should see: A draft response in the reply area. Review it carefully — Freddy's responses are good starting points but always need a human review before sending.

3. Get a ticket summary

1. In any ticket with multiple updates, click Summarize in the Freddy panel
2. Freddy generates: what the original issue is, key troubleshooting steps so far, and current status

What you should see: A 3-4 sentence summary useful for handoffs, escalations, and context when picking up old tickets.

4. Use the suggested KB article panel

1. When working a ticket, Freddy automatically surfaces relevant KB articles in a side panel
2. Click any suggested article to open it in a popup
3. If the article resolves the issue, click Insert in Reply to add the steps directly into your response

What you should see: A right sidebar showing 2-4 KB articles ranked by relevance to the current ticket's content.

Troubleshooting: If suggestions are irrelevant, your KB articles may not be tagged correctly. Ask your Freshdesk admin to review KB article categorization and ensure tags match common ticket categories.

Real Example

Scenario: 10 tickets come in Monday morning. Instead of reading each one carefully and manually categorizing, Freddy has already:

• Categorized 8 of them correctly (password resets, a software install, two network issues, printer problems)
• Flagged 1 as "Urgent" (a VIP user can't access email)
• Drafted responses for 5 of them based on matching KB articles

What you do:

1. Review Freddy's categorization — confirm the 8 correct ones with a click each
2. Open the urgent VIP ticket first (Freddy surfaced it to the top)
3. Open each other ticket → review Freddy's drafted response → adjust if needed → send
4. Skip the 5 fully-drafted tickets' manual writing entirely

Time saved: Morning triage goes from 45-60 minutes to 20-25 minutes.

Tips

• Freddy's response quality improves as your KB grows. Every AI-assisted ticket closure is an opportunity to add a KB article (use the Level 1 KB article prompt to write it quickly).
• Use Freddy's ticket Sentiment Analysis feature to identify frustrated users early — tickets flagged as "negative sentiment" can be escalated proactively before the user sends a complaint.
• If Freddy's responses are consistently off for a specific ticket type, improve the relevant KB article — that's usually the root cause.

Tool interfaces change — Freshdesk updates Freddy Copilot features regularly. If a feature has moved, look in Settings → Freddy Copilot or check the agent dashboard panel.