Using Freshdesk

Most teams migrate to Freshdesk, turn on Freddy, and wonder why accuracy is low. The answer is almost always the same: the data went in the wrong order.Why Freddy fails after most migrationsFreddy AI draws on two sources to do its job: your Knowledge Base and your closed-ticket history. Both matter, but the sequence in which they arrive on the platform matters just as much as the content itself.If you migrate tickets before your KB articles are in place, Freddy starts indexing ticket content that references articles it cannot yet retrieve. The AI routes intent correctly but generates responses from a blank KB — or worse, hallucinates content that isn't there.If you migrate unresolved or low-rated tickets, the problem runs deeper. Freddy's auto-triage and article suggestion features l

Hi Freshworks Community,From my experience, teams avoid disruption when they treat migration as a structured process, not a single technical event.  Here are a couple of practical approaches to help your team migrate smoothly: 1. Plan early and prepare your dataStart planning well in advance. Use this time to clean up outdated records, review workflows, and define what data truly needs to move. 2. Involve your support team earlyPrep work isn’t only technical. Support agents work with tickets every day, so involving them during setup gives them visibility into how the new system works. This helps them understand the “why” behind workflows and troub

Not all your tickets need to migrate. Filtering lets you move only what matters.Most teams migrate everything by default. Then they spend days after go-live cleaning up resolved tickets from three years ago, closed spam, and test records that never should have moved. Data filtering during migration prevents that.It lets you define exactly which tickets transfer to Freshdesk or Freshservice. Less data means faster migration, a cleaner target system, and less noise for agents from day one.Why filtering mattersMoving all your data sounds safe. It isn't always. Here's what unfiltered migrations lead to:Agents waste time in a cluttered system full of outdated or irrelevant tickets

Hello everyone,We would like to understand the recommended procedure for deactivating contacts in Freshdesk.Specifically: Is there a way to deactivate a contact without permanently deleting it? What happens to existing tickets associated with that contact after deactivation? Are there any best practices to ensure reporting and historical data remain unaffected? Is bulk deactivation possible? We want to ensure we follow a clean and compliant process while keeping our historical ticket data intact.Thank you in advance for your guidance.

Every time we reply to a ticket the default text it enters is Hi <Firstname> <Lastname> Is there a way to change this to just the firstname?  Every agent we have the first thing they do is have to edit the first line. 

Using: /api/v2/search/tickets?query=[query]:The official FreshDesk docs provide this limitation: "The number of objects returned per page is 30; also, the total count of the results will be returned along with the result" and "To scroll through the pages, add page parameter to the URL. The page number starts with 1 and should not exceed 10." This implies that I can only account for a maximum of 300 objects (tickets). What if I have more than 300 objects to account for in a specified interval, say within an hour?The ‘created_at’ parameter is strictly a date datatype (YYYY-MM-DD), so I cannot partition the data according to hours, which would otherwise have been a solution that circumvents the pagination limitation. Using: /api/v2/tickets?:Another significant limitation is the ‘updated_since’ parameter. It only applies to tickets that have been updated at least once during their lifespan. Tickets that are not updated will not appear in

Hi, I just newly signed up with the trial account but keep on getting this issue when creating tickets:https://global7925.freshdesk.com/ Appreciate your immediate response on this as this is needed for a client demo. Thanks!

Hi Freshworks Community!Your help desk migration has a blind spot. Every ticket is updated as the data transfers.Businesses lost $3 billion globally in 2025 from poor customer experiences. A migration that drops active tickets contributes directly to that number.The standard approach: freeze ticket activity, move the data, resume work. Tickets still arrive during that window. Agents can't respond. A backlog forms fast, and when migration finishes, updates get missed, conversations get crossed, and SLAs break.Delta migration solves this. It captures every ticket created or updated after your full data migration began, and transfers them to the target system. Your team keeps working on the source the entire time.Why Delta migra

I am submitting this as an enhancement, as this functionality does not exist, to my knowledge. There have been a few requests/questions around this topic, but it appears they have all been archived, or the original need has not been captured. We receive tickets through various channels where we need to set or update the Subject for appropriateness and data governance. When tickets are received/created - the original requester email sets the ticket subject. We need the ability to set/update the subject using Automations, Scenarios, and Canned Responses. That way, when we programmatically or manually respond to the requester, the email subject line appears per our Company Policy and branding guidelines and provide consistency for data governance purposes. Furthermore, it is inefficient for end users to update these manually.

Hello,I am currently unable to reset my password on the Freshdesk portal.When I click on the password reset link received by email, I get the following error:"Sorry, we couldn't locate your account..."I have already tried:- Requesting a new reset link- Using incognito mode- Copy/pasting the URL directly in the browserThe issue persists.Thanks

I recently created an account to use the Freshdesk Support Desk and now this error shows up:“Outgoing emails are blocked for your account. Please contact our support team at support@freshdesk.com”  My account: https://pflegelust-gmbh.freshdesk.com/ Thanks!

Hello everyone,I have a question about custom ticket statuses in Freshdesk.In addition to the standard status values like Open and Closed, I created a individual custom status. The custom status is available in the ticket itself and works there as expected.However, when I try to use this status in an Automation rule, I can only see the standard status values in the dropdown. My custom status does not appear there, so I cannot select it.What I checked so far:The custom status is already created and active It is visible in the ticket status field In Automation, only the default statuses are available in the dropdownMy questions:Is this a known limitation in Freshdesk Automations? Do custom statuses need any extra configuration before they can be used in Automation rules?Has anyone

Hello!I am using Freshdesk, and have multiple customer companies. I have a portal set up for each company, with a custom url.I’m trying to get Freshdesk to be able to associate company A with company A’s portal and tickets, and company B with company B’s portal and tickets. I’d need the system to send the correct activation URL as well in the activation email. I am struggling to figure out how to do this. Is this possible? Should we only have one portal? If only one portal, how will the portal and system know to only show company A’s forms to company A users (and only show them tickets for company A as well). Thank you!

Moving to Freshdesk or Freshservice? Preserve ticket structure, workflows, and automation with accurate data mapping. Your new system runs like your old one—no downtime, no broken processes.Why data mapping mattersProper mapping is crucial for a smooth help desk migration. It ensures data lands correctly, preserving ticket structure and workflows. Key benefits:Protects ticket context, history, and attachments Maintains workflows and automation Keeps required fields accurate Reduces errors in ticket handling

As pointed out by other customers, such as , the ability to convert an Agent to Collaborator or Collaborator to Agent is a glaring gap that was missedThe current advisory to first delete the agent and then make them a collaborator is flawed as it creates a situation that this users tickets are unallocated incorrectly, they are still within the company and did work on these items.Totally get the need to restrict collaborators from being asssigned on tickets going forward, but there are valid use cases for them to remain on historic ticketsSUB FORUM SELECTED IS INCORRECT BUT THERE IS NONE MORE ACCURATE

Is there any way of removing the Customer responded state when all the cust has said is "thanks" etc?I find I have to keep clicking on a case to check if they need to be replied to.Our issue is with things that some groups (such as Developers) will keep in pending status (potentially for quite a long time) and which Support would keep an eye on in case the customer replies and needs a response.At the moment, a "thanks" email will flag it as Customer Responded forever, meaning we have no way to know if a subsequent, more substantive response has arrived without clicking into the case.I have seen Thank You Detector - however it looks to only deal with closed or resolved cases, which we would have no issue with as we can just close or resolve those again.

How have you solved this case?Once an agent has responded to the ticket and are awaiting the customers input, we change status to “Waiting on customer”. After this status has been active for 48 hours, we want a reminder email to go out. Once. I have set up an “Hourly Triggers” automation stating:If hours since waiting_on_customer is 48Actions: Send a reply via EmailIt turns out that the backend job that performs this is run once every hour. It will check if the status of the ticket is EXACTLY 48 hours for this to be true. So if it is 48.2 hours, it will not trigger this atuomation.Freshdesk support suggests a workaround, to add a greater than 48 hours and less than 50 hours condition, and in addition adding a custom ticket field to be tagged - so we dont risk mulitple emails going to the customer. I find it interesting that what is to me a basic use case of a ticket platform requires this approach. Wanted t

Hi,I realize this question is better posted to the FreshservicePS Slack channel, but I haven’t received a response in that forum so I’m trying my luck here.I’m using the FreshservicePS PowerShell module and have a question regarding the data retrieved with Get-FreshServiceTicket. I have a ticket that was created from a Service Catalog form, and when I view the SR in the WebUI the form data is visible but it is not retrieved with Get-FreshServiceTicket.How do I retrieve this data using powershell or via the API directly?Thanks!

I’m looking for a way (workflow or alert) to auto create an incident or service request that's attached to the contracts > contractor feature when a contract is set to expire.