Freshdesk Contact Center

Freshworks sold a standalone telephony product called Freshcaller. It was renamed Freshdesk Contact Center, and it also turns up as the voice channel inside the wider customer service bundle. Same underlying thing, three names in the search results, which is why documentation from different years reads oddly.

Functionally it is cloud telephony that lives next to your ticket queue. You rent numbers from Freshworks, calls route through their infrastructure, and agents answer in the browser rather than on a desk phone.

The reason to use it rather than a general telephony provider is the attachment. A call arrives with the customer record already open, and the call itself becomes part of the support history rather than a separate log nobody joins up.

The interactive voice response menu is where most contact centres go wrong, and the mistake is always the same. Too many options, too deep.

Every layer of menu you add moves a caller further from a person and closer to hanging up and emailing instead.

Three rules I would hold to. Keep the top menu to four options or fewer, because people cannot hold more than that while listening. Never go more than two layers deep. And always give a route to a human, usually by staying on the line or pressing zero, even if you do not announce it loudly.

Put the most common reason first, not the most important to you. If sixty per cent of calls are order status, that is option one. Ordering the menu by department org chart is how you get callers pressing three options before they find the right queue.

One genuinely useful trick: state the expected wait before the menu, not after. A caller who knows it is four minutes makes a decision. A caller who finds out after two minutes of menus feels tricked.

This is the part that justifies buying voice from your help desk vendor rather than anyone else.

An answered call can create a ticket against the caller record, with the call metadata attached and, where enabled, the recording and a transcript. Agents can add notes during the call, so the summary is written while the conversation is fresh rather than reconstructed an hour later.

Missed calls and voicemails can also generate tickets, which is the setting I would check first. Without it, a missed call is a line in a report that nobody works, and the customer's second attempt lands as a brand new contact with no history.

Two behaviours worth knowing about. Calls tie to the contact by phone number, so a caller phoning from a number that isn't on their record creates a new contact, and now one customer has two records. And a customer who calls, gets no answer, then emails about the same problem produces two separate tickets covering one issue, which is a duplicate in every sense that matters even though the channels differ.

The channel picture as a whole is covered in the omnichannel guide, and the general product shape in Freshdesk as help desk software.