Ticket Merger

The Freshcaller Freshdesk Integration

Freshcaller is the Freshworks phone product, and the point of the Freshcaller Freshdesk integration is simple: a call should leave a record on the ticket, automatically.

Start free trialAll guides

What the Freshcaller Freshdesk integration gives you

Freshcaller is the cloud telephony product in the Freshworks family, now generally sold as part of the contact centre offering. Connected to Freshdesk it does four things worth having.

Calls become records. An inbound or outbound call can create a ticket, or attach to an existing one, so the conversation isn't lost the moment the handset goes down.
Context on answer. The agent sees who is calling and their recent tickets before they say hello, which removes the worst part of phone support: asking a customer to repeat what they already wrote to you.
Click to call. A phone number in a ticket or contact record becomes clickable, and the dialler places the call. Small feature, meaningful time saving, fewer misdialled numbers.
Recordings and voicemail attached. The audio and the transcript, where enabled, sit on the ticket rather than in a separate system nobody opens.

Packaging has shifted as Freshworks consolidated its products, so check the current Freshworks docs for what is included in your subscription versus what is a separate purchase.

Deciding what a call creates

This is the configuration decision that shapes everything downstream, and it is worth ten minutes of argument up front.

One ticket per call sounds tidy. In practice it produces a queue full of thirty second records with no content, because plenty of calls are "is my order shipped" and are over before anyone types. It also wrecks your volume reporting.

The alternative is attaching calls to existing tickets where the caller already has an open one, and creating a ticket only for calls that need follow-up. Cleaner queue, better numbers, slightly more agent judgement required.

A call that resolved in ninety seconds doesn't need a ticket. A call that ends with "I will check and get back to you" absolutely does.

Whichever you pick, be consistent, and make sure missed calls and voicemails always create something. A missed call that leaves no record is a customer nobody will call back.

The setup order that works

Numbers first. Buy or port the numbers you need, and check availability in your countries before promising anything internally. Porting takes longer than any project plan allows for.
Then business hours and the out of hours path. Voicemail to ticket, an announcement, or a redirect. Decide before go-live, because the default behaviour won't match your promise.
Then routing. Map queues to Freshdesk groups so a call and an email about the same topic reach the same people. Splitting them by accident is how two agents answer the same customer differently.
Then agent setup. Devices, browser permissions for the softphone, and the availability toggle. Agents who forget to go unavailable generate missed calls that look like a staffing problem.
Last, recording and consent. Announcements, retention periods, and who can play a recording back. This is a legal question in most jurisdictions, not a preference.

What changes for the team

Voice is not email with sound. Adding it changes how the queue behaves, and pretending otherwise causes the usual problems.

Phone is synchronous, so an agent on a call isn't working tickets. Plan capacity for that or your email response times will slip in week one and nobody will connect the two events.

Wrap-up time is real work. If an agent has to write a note after every call, budget for it. Skipping it's how you end up with call logs that say nothing except that a call happened.

And measure the right things. Call metrics, answer rate, abandon rate, average handle time, live alongside ticket metrics rather than inside them. An average resolution time that mixes a two minute call with a four day email thread is a number with no meaning. The wider design questions are in the contact centre guide.

What to check before you rely on it

Four tests, all quick, all worth doing before you publish the number.

Call in as a known customer. Does the agent screen show the right contact and their open tickets.
Call in from an unknown number. What gets created, and is the contact record usable or a bare phone number with no name.
Leave a voicemail out of hours. Confirm a ticket appears with the audio attached and lands in a group somebody watches.
Click to call from a ticket. Confirm the outbound call attaches back to that same ticket rather than creating a new one.

If you are running a different phone system rather than Freshcaller, the same questions apply and the answer route is different. That is the CTI framework territory, and the 3CX integration guide covers one common example.

FAQ

Frequently asked questions

What lands on the ticket after a call?

Freshdesk call logs with duration, direction and a recording link. That Freshcaller ticket integration is the whole point of a Freshdesk phone integration: a call that leaves no record may as well not have happened.

What does the Freshcaller Freshdesk integration do?

It attaches calls to tickets, shows the caller and their history before an agent answers, adds click to call from ticket and contact records, and stores recordings and voicemail against the ticket.

Does every call create a ticket?

That's configurable. One ticket per call fills the queue with empty records and distorts volume reporting. Most teams attach calls to existing tickets and create new ones only where follow-up is needed.

Is Freshcaller included with Freshdesk?

It's a separate Freshworks product, now generally sold within the contact centre offering. Check the current Freshworks pricing and docs for what your subscription covers.

Can agents take calls in the browser?

Yes, through a softphone in the agent view, which needs microphone permission and a stable connection. Desk phones and mobile options exist too, depending on your setup.

Are call recordings stored on the ticket?

Recordings and voicemail attach to the ticket where enabled. Recording consent, announcements and retention are legal questions in most jurisdictions, so settle those before switching it on.

Called, then emailed

Customers who phone and then email create two tickets for one problem. Ticket Merger detects the pair and merges them automatically.

Start free trial

14-day free trial. No credit card required.

Keep reading

Freshdesk Contact Center: Voice, IVR and Routing
How Freshdesk Contact Center works after the Freshcaller rename: getting numbers, designing an IVR, routing calls, and how a call becomes a ticket with a recording.
3CX Freshdesk Integration: Calls That Log Themselves
How the 3CX Freshdesk integration works: what click to call and screen pop actually do, how call logging into tickets behaves, and where it stops.
Freshdesk Omnichannel: What the Omni Bundle Adds
What Freshdesk Omnichannel adds over standard Freshdesk, how the channels fit together, what it costs, and whether the bundle is worth it for your team.
Freshdesk Facebook Integration: Pages to Tickets
How the Freshdesk Facebook integration works, what becomes a ticket from comments and Messenger, the response windows to know, and where moderation ends.