Using Freshdesk

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 Reporting gets skewed by historical data that no longer reflects current performance Migration takes longer, increasing the window of risk Storage costs in the new system grow from day oneFiltering gives you a cleaner starting point.One important thing to understand firstThe filters available during migration depe

Most enterprise help desk migrations run on standard shared infrastructure. It means multiple organizations, one common environment, data processed in a pool that your security team doesn't control. For enterprises without strict regulatory obligations, that's workable. For those that do, it's a non-starter.Private Cloud Help Desk Migration is built for enterprise teams operating under strict security policies, data residency mandates, or regulatory frameworks that shared infrastructure can't satisfy. If your legal, security, or compliance team needs to sign off on how and where your data is processed during a migration, standard tooling typically can't give them what they need .If your team is asking questions like "where exactly is our data processed during the transfer?" or "can we guarantee it doesn't leave a specific region?" — shared infrastructure doesn't have a satisfying answer. That's the gap Private Cloud Help Desk Migration exists to fill.What actually changes with Private

Hello Freshworks Community,I’m reaching out here because I have an urgent billing/invoice issue and I have not received any response from the official support channels.I have already contacted:support@freshworks.com billing@freshworks.comHowever, I have not received any reply so far, and my issue remains unresolved.This is becoming quite frustrating as I need clarification on my invoice urgently for finance reconciliation purposes.Could anyone please advise:Is there another support channel or escalation path for billing issues? Is there a direct account manager or escalation email for urgent cases? Has anyone experienced faster resolution through a different Freshworks contact method?I would appreciate any guidance from the community or Freshworks staff on how to escalate this properly.Thank you.

Hello Freshworks,I use the font Verdana and set the font size to 14, but It looks 9 in the article.Why is it inconsistent?On google docs, the font is still showing correctly.    

I’m looking to see if anyone is using Freshdesk for internal tickets, as well as customer tickets.We have Freshdesk deployed, and despite only being 3 months in, we’re using a lot of functionality.I’m looking to see if we can decomission the tool that we use for internal tickets, but I can’t see how I can associate an agent with our internal company - to then create some views/email alerts for internal tickets.Currenty, an agent can log a ticket against thier own name, but it gets lost within the customer tickets.Is anyone doing this, or have you a seperate instance of FreshService (or another tool), for internal tickets?

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.

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.

Hi everyone,I have a question regarding a change that took place not too long ago—with an update that I believe occurred in November of last year—where FCR, DSR, and Unable tickets are no longer recognized as non-violations. This is affecting our metrics. What are the possible ways to resolve this? Thank you in advance

I’m looking to better understand how many people use the Auto Email feature in Freshdesk.In it’s current form it’s an On/Off option and you are unable to limit what Groups or other ticket fields it can be enabled for. I’ve raised on the Ideas Forum () however I’d like to know if any other companies are using the feature.I don’t want to enable it on all tickets, and instead limit it to doing First Response on non SLA contracted questions/account problems, rather than big P1 total loss of service tickets.Thoughts? 

I've reduced my images' size, but they're still getting cut off on mobile. I can't shrink them further. Is there any code or workaround I could use to fix this?

Hello Folks!Here’s a quick look at what’s new with Freddy AI for Customer Service this month. These updates are aimed at improving both agent productivity and admin control—plus, a few exciting features are now in public beta! What’s new with Freddy AI for customer service this month? There’s a lot of new updates and enhancements that we’re rolling out to customers using our customer service products with Freddy AI! Here’s a quick summary for everyone here. Reply Suggester is now in Public Beta:  Agents now have access to AI-powered reply suggestions (generated using solution articles) to respond to incoming customer queries, resolving tickets faster and more accurately.Learn more |  Freshdesk and  Freshdesk Omni Freddy AI Agent can evaluate itself: AI agents will generate a diverse set of customer queries to self-test their responses to identify knowledge gaps that need to be patched with more knowledge sources.Learn more |  Freshchat and  Freshdesk Omni  The enhancements that are hap

when I send latest public comment in email, it sends the attachment as hyperlink and not as an attachment which is causing issue of logging in again to freshworks. Can you suggest any way to send comment attachment through API or email?

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 learn from the interactions you feed them. Open tickets have no resolution, so they add noise rather than signal. Low-CSAT tickets teach Freddy the patterns behind your team's worst responses — the apologies

We have tried to add dependent fields to our ticket form, but they will not drop down when you go to submit a ticket in the portal. Does anyone have any solutions or similar problems?

Hi! My company has a portal for Solutions (articles) and another for Support (tickets). I would like to have a place to present videos and other information for new customers to explain them how account configuration works and guide them. Should I create a new portal or a custom section in the theme (we have a custom theme with Breezy)? I’m not sure what is possible.    

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 troubleshoot issues faster after launch. 3. Communicate internally and define escalation pathsKeep teams aligned on timelines and clearly assign responsibility for technical and customer-facing issues. 4. Train your team by roleProvide role-specific training for agents, admins, and managers to reduce friction after go-live. 5. Test thoroughly befor

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 the API response, further restricting the data that

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!