What is Freddy AI in Freshdesk?
Freddy AI is the name Freshworks gives its AI inside Freshdesk. It comes as three parts: Freddy AI Copilot, which helps agents with summaries, reply drafts and triage; Freddy AI Agent, which answers customers on chat and email; and Freddy AI Insights, which spots trends in your support data and lets you ask analytics questions in plain language.
Is Freddy AI the same as Freshchat?
No. Freshchat is Freshworks' messaging product. Freddy AI is the AI layer, and a Freddy AI Agent can be deployed on web chat, WhatsApp or email from inside Freshdesk. You can run Freshdesk with Freddy and never use Freshchat.
Does Freddy AI replace Freshdesk's automation rules?
No, the two work together. Automation rules carry out fixed logic, such as assigning by type or escalating on an SLA. Freddy reads and writes language: it summarizes, drafts, and recommends field values. A dependable setup lets Freddy suggest and lets rules enforce the things that must always happen.
Can Freddy AI see data outside Freshdesk, like order or billing status?
Copilot works from the ticket and your solution articles. An AI Agent can reach further, because AI Agent Studio workflows can use API actions and Actions Library integrations. The action still needs a system on the other end that returns the right order or invoice, and building that service is integration work, not a Freddy setting.
Is Freddy AI included in every Freshdesk plan?
No. Copilot is a paid add-on on Pro and Enterprise. AI Agent sessions are available on Growth, Pro and Enterprise, with 500 included once per account and more bought in blocks. Insights is part of Enterprise. Freshworks changes these, so the Freshdesk pricing page is the place to confirm.
What does n-frames build for a Freshdesk AI rollout?
The data Freddy can't reach on its own. We build the order, refund and subscription lookups an AI Agent's API actions call, the syncs that keep plan and invoice fields current on tickets for Copilot users, and the reporting that shows which escalations a missing data source is causing. For the Freshdesk side of that work, see our Freshdesk API guide.