Freshdesk Live Chat, and What It Costs to Staff

Freshdesk live chat is the easiest channel to switch on and the hardest to staff. Here's how it fits together, and the sum to do before you launch it.

Start free trial All guides

Where Freshdesk live chat actually lives

Freshdesk and chat have a slightly awkward relationship, and knowing the shape saves a lot of confusion.

The messaging capability is Freshchat, a Freshworks product in its own right. It powers the website widget, in-app messaging, and the messaging channels such as WhatsApp and Facebook. It has its own admin, its own conversation history and its own analytics.

You can buy it separately and connect it, or get it as part of the customer service bundle, in which case agents work chats and tickets in one workspace. The Customer Service Suite guide covers which arrangement you end up with.

Separately, Freshdesk has an embeddable help widget. That's not chat. It surfaces knowledge base articles and a contact form on your own pages, and for a lot of sites it does most of the job chat is bought for, at no extra cost and with no staffing requirement. Worth trying first, genuinely.

Getting the widget live

The mechanics take under an hour. The decisions take longer, and should.

Install the script on your site or in your app. One snippet, usually in the template so it appears everywhere you want it.

Choose the pages. Chat everywhere is rarely right. Checkout, pricing, account and support pages carry high-intent visitors. A blog post from 2019 does not.

Set availability hours and write a genuinely useful offline message. Offline should collect an email address and set an expectation, not apologise.

Decide whether to prompt. A widget that opens itself after ten seconds converts more conversations and irritates a portion of visitors. Test it, don't assume.

Collect identity up front if you support existing customers. An email address or account reference before the conversation starts saves the agent two exchanges and links the chat to the right record.

Then test on a phone. A chat widget that covers the buy button on mobile is a real and common own goal.

Getting chats into tickets

This is the integration question that decides whether chat helps or fragments your support.

A chat conversation that ends with something outstanding should become a ticket, so it enters the queue you already measure and chase. A chat answered in three messages and closed does not need to become anything.

The pattern that works is converting on escalation. The agent decides the issue needs follow-up, converts the conversation to a ticket, and the transcript travels with it. What you want to avoid is every chat automatically spawning a ticket, because your volume metrics double overnight and half the tickets are "hi, are you open on Saturday".

Watch the identity join. Chats from an anonymous visitor create a contact keyed on whatever they typed. If that email differs by one character from their account email, you now have two contacts and a support history split across both. Requiring identification for logged-in users fixes most of it.

Also decide what the customer receives afterwards. A transcript by email is good practice and it gives them something to reply to, which keeps the conversation in one place rather than starting a fresh contact.

The staffing sum nobody does first

Here's the number that determines whether chat is a good idea for you.

Chat is a synchronous channel bolted onto an asynchronous team. Email waits. A chat visitor waits ninety seconds and leaves.

An agent can hold two or three concurrent chats well, four badly. During the hours the widget is live, somebody has to be watching it, and that person cannot be the same person expected to clear the email backlog, because context switching wrecks both.

So before launching, estimate chats per hour during your busy period, divide by two or three, and see whether the resulting number of people exists. If it does not, run chat for a narrow window, say two hours over lunch, and say so on the widget. A predictable two hour window beats an always-on widget that nobody answers.

And set a first response target for chat separately from email. Anything over a minute reads as abandonment to a chat visitor, however reasonable it looks in a ticket report.

Measuring it, and when to turn it off

Track four things and ignore the rest at first.

First response time in seconds, not minutes. Minutes hide the problem.

Abandonment, meaning visitors who opened chat and left before an answer. This is the honest quality number.

Conversations per agent hour, which tells you whether staffing matches demand.

Contacts created afterwards, meaning people who chatted and then emailed anyway. That is chat failing rather than chat working.

If abandonment stays high and the follow-up contacts keep coming, chat is costing you more than it saves and the fix is narrower hours or better self-service rather than more widget. The help desk software overview puts the channel in context, and bots have their own honest treatment in the chatbot guide.

FAQ

Frequently asked questions

Is Freshdesk chat support the same as Freshchat?

Underneath, yes. The Freshdesk chat widget on your site is Freshchat, and Freshdesk messaging and Freshdesk website chat are the same channel described three ways.

Does Freshdesk include live chat?

Chat comes from Freshchat, a separate Freshworks product, either purchased alongside Freshdesk or included in the wider customer service bundle. Freshdesk itself has a help widget that surfaces articles and a contact form, which is not the same thing.

What is the difference between Freshdesk and Freshchat?

Freshdesk handles tickets, mostly asynchronous and mostly email led. Freshchat handles conversations, synchronous and messaging led. Bundled together they share a workspace and a customer record.

Do chats become tickets automatically?

You choose. Converting on escalation is usually better than converting everything, because auto-creating a ticket for every "are you open on Saturday" doubles your reported volume with nothing to work.

How many chats can one agent handle at once?

Two or three well, four badly. Plan staffing on that basis, and shorten your operating hours rather than stretching the same people across chat and the email queue at the same time.

Should I turn chat on if we are a small team?

Only with narrow, advertised hours. An always-on widget nobody answers does more damage than no widget, and the Freshdesk help widget with good articles covers a surprising amount of the same demand.