How to Merge Requesters in Freshservice
How to merge requesters in Freshservice matters because one employee with two profiles will always look like two different people raising two different tickets.
How to merge requesters in Freshservice, step by step
Open the requester list
Find both profiles. Usually one came from your directory sync and one from an email that did not match it.
Merge the duplicate into the primary
Choose the profile to keep, then merge the other into it. Tickets and history move across.
Fix the source
If the duplicate came from an unmapped email address, add it as a secondary address so the same split doesn't happen again next month.
Why this makes duplicate detection better
Requester identity is the strongest single signal that two tickets are the same request. When identities are split, detection has to lean on wording alone, which is weaker and more cautious by necessity.
Tidy requesters, and the built-in tooling gets noticeably sharper, as will Ticket Merger when Freshservice support lands.
Frequently asked questions
How do you merge requesters in Freshservice?
Open the requester list, select the duplicate profiles, and use the merge action to fold them into the primary requester. Their tickets and asset associations move across with them.
Does Ticket Merger support Freshservice yet?
Not yet. Ticket Merger connects to Zendesk and Freshdesk today, and Freshservice is next on the roadmap. Tell us you want it and we will let you know the moment it is ready, since we prioritise by how many people ask.
Can I review merges before they happen?
No. Once a pair matches your rules, Ticket Merger merges it. What you control is what qualifies: requester, the subject keywords you list, the time window, and the groups, forms or tags you exclude. To see how it behaves before it touches everything, point it at one group first and widen from there. Every merge leaves a note on the thread saying what was merged and why.
What stops it merging two tickets that are not the same?
Rules you set. Match on requester, subject keywords, status, priority, category or group, and a time window, and exclude anything you want left alone, like tickets from a specific form, group or tag. Anything that does not clear those rules is left alone.
How long does setup take?
About five minutes to connect, and the first scan of your open queue runs immediately after. Onboarding help is included on every plan.
Clean identities, fewer duplicates
Ticket Merger matches on identity and domain, so tidy requester data pays off the day Freshservice support lands. It's live on Zendesk and Freshdesk now.
Start free trial14-day free trial. No credit card required.