Freshdesk and Freshchat
Freshdesk and Freshchat are two products from the same company, which people assume means one system. It doesn't. Here's where the seam actually sits.
Freshdesk and Freshchat: two products, one customer record
Freshdesk is the ticketing helpdesk. Freshchat is the messaging product: website widget, in-app messaging, WhatsApp and social channels, bots, and a conversation inbox that behaves nothing like a ticket queue.
The distinction that matters is the unit of work. A ticket is a durable record with a status, an owner, an SLA and a history. A conversation is a live stream that is either being attended to or it's not. Those need different interfaces, which is why they are different products rather than one screen.
Freshworks connects them through a shared customer identity and a link between the two systems, so an agent handling a chat can see the person's ticket history, and a chat can be turned into a ticket when it needs to become durable work.
Exactly how that connection presents itself depends on which Freshworks bundle you're on, since the products have been packaged in several ways over the years. Check what your account actually includes before designing around a specific behaviour.
What the connection gives you
Three things, in descending order of usefulness.
What it does not give you is a single queue. Chats and tickets are still counted, routed and reported separately. If you were hoping for one number that describes your team workload, you will be assembling it yourself.
When a chat should become a ticket
This is the operational decision that determines whether the setup works. Get it wrong in one direction and your ticket queue fills with resolved chatter. Get it wrong in the other and things get dropped when the customer closes the tab.
The test I would use: does anything still need doing after the customer leaves?
If the answer to the chat is the answer, keep it a chat. If the chat produced work, make it a ticket.
Convert when the issue needs investigation, needs another team, needs a refund or replacement processing, or needs a reply the customer will not be present for. Do not convert a question that was answered in four messages, because then every session becomes a ticket and your volume metrics turn into fiction.
One useful convention: whoever converts writes a one-line summary at the top of the new ticket. A raw transcript is a poor brief for the next agent, and the person who was in the conversation can summarise it in fifteen seconds.
Do you actually need both?
A fair question, and the answer is genuinely no for a lot of teams.
Freshdesk on its own has an embeddable support widget that surfaces articles and a contact form on your site. That's not live chat, but it covers a large share of what people think they want when they ask for chat, which is usually "let customers get help without leaving the page".
You need Freshchat when live conversation is a real part of your service: sales-adjacent support, high-urgency products, or channels like WhatsApp where customers already are. You also need it if you want scripted bot flows with buttons, because those live there rather than in Freshdesk.
The honest cost isn't just licensing. It's a second inbox with its own staffing model, its own routing and its own response expectations. A chat channel nobody is watching is worse than no chat channel, because the widget promises presence. If you cannot staff it during the hours it is visible, hide it outside those hours.
Broader channel strategy, including where each channel earns its place, is covered in the omnichannel guide.
The setup detail that causes double records
Identity matching. Almost every complaint about this pairing traces back to it.
A visitor chats anonymously, gives an email address halfway through, and that email differs by a character or is a personal address rather than the work one on file. Now you have a chat contact and a Freshdesk contact that are the same human and the system doesn't know. Their ticket history does not appear, the agent assumes a first-time customer, and the conversation goes badly.
Two mitigations, both worth doing. Identify logged-in users to the widget programmatically so the identity comes from your own application rather than from typing. And ask for an email early in any unidentified conversation, before the issue rather than after it.
The second failure mode is duplication in the other direction: a customer chats, gets no resolution, then emails about the same thing. Now there is a conversation and a ticket, or two tickets if the chat was converted. Nothing in the platform notices, so somebody has to.
Frequently asked questions
What does the Freshchat integration actually sync?
Conversations and contacts. A Freshchat Freshdesk sync creates or matches the contact and can raise a ticket from a chat, and the Freshchat integration stops short of merging chat history into an existing ticket.
Is Freshchat included with Freshdesk?
It has been packaged in several ways, including as part of broader Freshworks bundles and as a standalone product. Check what your current subscription includes rather than assuming, because the answer has changed more than once.
Can a Freshchat conversation become a Freshdesk ticket?
Yes, that's the core of the integration. The transcript comes across so the ticket has the history. Convert only when work remains after the customer leaves.
Do chats count towards my ticket volume?
Only the ones converted into tickets. Chats and tickets are reported separately, which means any combined view of team workload is something you build yourself.
Does Freshdesk have live chat without Freshchat?
Freshdesk has an embeddable support widget that surfaces knowledge base articles and a contact form. Real-time conversation, bots and channels like WhatsApp live in Freshchat.
Why does the chat agent not see the customer ticket history?
Almost always an identity mismatch. The chat contact and the Freshdesk contact carry different email addresses. Identify logged-in users through the widget rather than relying on them typing an address.
Chat first, then email about the same thing
One customer, two channels, two records. Ticket Merger spots the pair in Freshdesk and merges it into a single thread.
Start free trial14-day free trial. No credit card required.