The Freshdesk Freddy Bot
The Freshdesk Freddy bot is a brand covering several features, not one product. Knowing which one you're configuring saves a lot of confusion.
What the Freshdesk Freddy bot actually refers to
Freshworks puts the Freddy name across its AI capabilities, and the same word covers jobs with very different audiences.
For a support team, the first two are what people mean when they say Freddy bot. Exactly which of them your account has depends on plan and bundle, and Freshworks has moved these around more than once, so check the current Freshworks docs rather than a comparison table from last year.
Where its answers come from
This is the single most useful thing to understand about it.
The customer-facing answer layer reads your published knowledge base. It is retrieval over content you wrote, presented conversationally. It's not a general model answering from the internet, and that is a feature, not a limitation, because it means the bot cannot invent a returns policy you never had.
The practical consequence follows immediately. If an answer is missing, wrong or written for internal readers, Freddy inherits every one of those problems. There is no setting that fixes thin content.
You don't train this bot in a bot screen. You train it by writing better articles.
A second consequence people miss: article visibility matters. Content restricted to logged-in users or to agents will not be served to a general visitor. If the bot seems to know nothing, check what is actually published before you file a support ticket about the AI.
Training it in practice
Here is the loop that works, and it is unglamorous.
Do this monthly for a quarter and the difference is obvious. Do it once and never again and the bot ages badly, because your product changes and the content does not.
Guardrails worth setting
Scope is a safety feature. A narrow bot that's right beats a broad one that is plausible.
Keep it away from anything where being wrong costs money or trust: refunds, cancellations, disputed charges, account deletion, anything security related. Those should route to a person even if the article exists, because the customer wants a commitment, not information.
Always leave a visible exit to a human. Always pass the context the bot collected onto the ticket. And tag escalations by origin so you can tell later which contacts started as bot sessions.
One more, easy to forget: decide what happens out of hours. A bot answering at 2am is genuinely useful, but only if the escalation path sets an honest expectation about when a person will reply. Silence after a failed bot conversation is how you generate a second ticket.
Measuring whether it works
Four numbers, and only one of them appears on a vendor dashboard by default.
If you're also weighing up a scripted flow or a custom build, the AI chatbot guide walks through those routes. Freddy is the lowest effort option and, for most teams with a decent help centre, the right first move.
Frequently asked questions
What is Freddy self service?
Freddy self service is the customer-facing half: the bot answering from your solution articles before a ticket is created. The agent-facing features share the Freddy name and do a different job.
What does the Freddy bot answer from?
Your published knowledge base. It retrieves and presents your own content, so it won't invent policies, and it will not know anything you have not written down.
How do I train the Freshdesk Freddy bot?
By improving articles. Write one problem per page, include the literal error text customers paste, use their vocabulary, and review what the bot served against what still escalated.
Why does Freddy say it can't help?
Usually missing or unpublished content. Check the article exists, is published, and is visible to the audience asking. Agent-only or login-restricted content won't be served to a general visitor.
Which plans include Freddy?
AI capability is tiered and Freshworks has repackaged it more than once. Check the current Freshworks docs and your own subscription rather than relying on any published comparison.
The duplicate the bot leaves behind
A customer who tries the bot and then emails creates two records for one question. Ticket Merger spots and merges them automatically.
Start free trial14-day free trial. No credit card required.