Hi 🙋🏼, I found that when I checked all our set business rules and workflows, some would be activated but essentially useless because a value used inside a condition for example was altered elsewhere and therefore removed from the condition statement. There is - to my knowledge - currently no other way than checking each rule in depth to see this problem in the flow even exists.Maybe an indicator/warning 🚨could be added in the list-view of business rules and workflows to see at once where such problems inside a rule or a workflow occurred.I think this would greatly improve debugging and make it easier for changes to be made in production.
We currently deactivated the standard requesters notifications in freshservice and are using workflow automators instead for one and only reason: exceptions cannot be configured in the standard notifications settings to avoid notifications being sent to specific requesters. This is needed because some of our requesters are also our suppliers, they're of course using ticketing tools at their side and enabling notifications for them creates loops of notification messages being sent between their system and ours.Would it be possible to add that feature (exceptions list) for each type of notifications so that we could use the freshservice standard requester notifications instead of automators ?
It would be good for agents to have secondary e-mail as well. A customer having there SAMAccount adress as primary login in FS and primary e-mail as secondary for requesters. Customer then need 2 profiles per agents One with the primary e-mail as a requester and agent profile with the login adress. The reason is that the SAMAccount do not change, the primary e-mail can. They have implemented that in their IDP. What happens for agents is Agents can’t see tickets they have emailed in to the system. They then need assume access to see there own tickets. (Solved it using WFA with WR/API to change the requester to the agent profile in FS) Ticket will not be created on the original sender when an agent forwarded an e-mail to FS /FD. (I guess I can solve that with a WFA/RW/API in FS as well.) Converting to agent will delete all the secondary emails of this contact' message | Freshworks CommunityAllow Agents to have a multiple email addresses like requesters do | Freshworks Community Any other scenario you have seen that would simply for if agents would be have secondary e-mail ? @Roxwell @Medic1334 @mbutler @zachary.king
Normally you can clear First Response Due by adding a Public Note on a ticket. However this does not work on tickets that you open yourself and assign to yourself. This means the only way to clear the First Response Due is by emailing yourself after you open your own ticket. This is a silly workflow that just adds an unnecessary step in for the Agent. If they forget to do this, then it messes up statistics on the First Response Times. Please make this make sense and either remove First Response Due all together for self-opened tickets (since if you are opening the ticket for yourself, of course you’re aware of it and no response is needed). Or at least let a public note clear it. Remove requirement to self-email please!
It would be very helpful if the Customer Portal could remember each user's preferred conversation order within tickets.Currently, every time a user opens a ticket, the interaction order resets to the default (for example, "Recent first"), requiring the user to manually change it back to "Oldest first" each time.For customers who frequently review long ticket histories, especially support teams and technical users, reading interactions in chronological order is much more efficient. Having to change the sorting option on every ticket creates unnecessary repetitive work and negatively impacts the user experience.Suggested enhancement:Allow customers to save their preferred conversation order (e.g., "Oldest first" or "Recent first") in their Customer Portal profile. Alternatively, remember the last selected sorting option using the user's account or browser session.
Hello,There's already an idea in this community from 3 years ago that was shot down without reason. I would like to bring it back up as I do not understand why an obvious and basic functionality is missing.In the Knowledge Base/Solutions there is no option to alphabetize your solutions Titles, while there is an option to sort every other option right next to it, see the screenshot below. I would like to see this option implemented because honestly, it's not that much of an ask or hard to do, thank you.The previous idea is located here;
Mer Méditerranée ↓ Suez Mer Rouge ↓ Bab el-MandebGolfe d’Aden → Océan Indien ↙ ↘Somaliland Djibouti | ↙↓↘Bases UAE USA, France, & potentiels Chine, Japon, Italie, Espagne ↓ Positions russes / discussions en Soudan
At Freshworks, we believe in the power of meaningful connections—whether it’s with your team or your customers. What better way to foster those relationships than with a cookout? In this guide, we’ll share creative cookout menu ideas and tips to help you host a memorable event that brings people together. From team-building BBQs to customer appreciation grilling sessions, discover how food can be the secret ingredient to stronger connections. Plus, learn how Freshworks tools like Freshdesk and Freshservice can help you plan and manage your event seamlessly. Let’s fire up the grill and create unforgettable moments!
I like to have the date format a specific way for ease of sorting things. I prefer YYYY-MM-DD, but the fact that it displays the date as Fri, 2026, Jul 17 is not very useful. As I am sure some if not most of you are aware, not all onboarding and offboarding’s come in the order they start or leave. It would be nice to be able to change how the date is formatted. I would like it the title of the journeys to look like this Journey - Offboarding [2026-07-17] - Jimmy Jones #JNY-90
In Admin you can create a location hierarchy which you can then assign to an asset.But there is no way to see this location path or location details in an asset and you can’t even search for a location to find it in admin to see the path or details without clicking through the hierarchy. Assume Location Path as: Country - City - Site - Building - Floor - Room - ‘Rack 15’‘Rack 15’ contains a Network Switch that has an asset and the asset is assigned to ‘Rack 15’ Now have an non admin agent try to find the location of that asset, good luck.Please show the location information somewhere in the asset details view.
The description field at the top of the page - Have this opened by default. With the fact you cannot add images to a content field, I have some information with images and then have to note in the content field to look in the description area. Be able to add images to Content fields - Having images in the content so we can add images to be able to explain things to users. Service Catalog item listing - Being able to change how the list of service catalog items are listed, maybe change to two column’s. The main reason is how limited this area is for text. I have had to rethink some of the word of some to get it down to enough characters so it is not truncated. Edit or disable popular items - I would rather disable to popular items and let users see the full list when they load the page.
When an agent goes in the ticket they need to click on Agent and type their name so the ticket could be assigned to them. How about a button like PICK UP. The same that we have when we mark the ticket in the Common view and just add thet PICK UP button in the ticket it self. This would really improve the Agent’s experience !
How many times have you had a Journey, and the the users start date changes? Today I got a ticket from a journey to do the New hire IT onboarding, but the users start date was pushed out till next week. so, now i have to sit on that ticket for the next week, not a big deal but, I would rather not. My idea was for a situation like this i to close the ticket, then go into the journey select that activity and reset it, so that next week when the user starts, a new ticket is opened
In a ticket view, it’s possible to change the number of tickets showing to either 30, 50, or 100. This same functionality should be added to the Agent Availability widget in the dashboard. Currently, it only shows 10 agents at a time, and we have over 30 agents, so it can be very time-consuming for the managers to check on all of their agents’ statuses. Please consider adding a feature to specify how many agents can be shown in the Agent Availability widget in the dashboard.
Problem / Use CaseCurrently, a CSAT survey can only be sent once (e.g., when ticket status is "Resolved/Closed"). There is a setting for the initial sending interval and survey expiration ("Expire the survey after"), but there is no way to automatically re-send a survey that has already been sent but remains unanswered after a defined period (reminder / re-send). Desired FeatureAn option for Freshdesk to automatically detect when a survey has been sent but not answered within X hours, and then send a reminder or re-send the survey to the customer. Ideally, it would include:Configurable time interval (e.g., "re-send after 48 hours without a response") Maximum number of reminders (e.g., 1–2 reminders) Trigger only for "Unanswered" status (not for "Partially Completed" or "Answered") Optional custom text/subject line for the reminder BenefitsHigher response rates for CSAT surveys and thus more reliable satisfaction data, without manual follow-up required.
Content platforms and tech podcasts receive feedback frommultiple channels such as websites, apps, and communities.A unified CSAT feedback loop inside Freshdesk would helpcreators and support teams analyze user satisfactionmore effectively.We tested a similar feedback workflow on our platform:https://www.smartsplay.com/This approach helped improve response trackingand engagement insights.
We’re trying to do some cross-workspace Service Request functions. One thing I cannot seem to be able to do is MOVE a ticket from one workspace to another as an Action in the automator. I can send an email, but I can’t send the attachments from the request so I need to send a Public Ticket Link. I can create a TASK in their workspace, but they can’t access the ticket details from the task in their workspace. We need the ability for cross-workspace functions in the Ticket Automator so we don’t need to move all of these requests manually.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
