Find, vote on and share ideas for Freshworks products. Here is how it works and what happens next.
Every idea has a status. It shows where the idea is today.
Not every idea makes it to the end. Some stay open for votes as Future consideration. Others are Closed.
You get an email each time the status of an idea you posted, voted on or subscribed to changes.
No. Planned means the idea is on the roadmap. Timing can change as priorities change. We update the status when work starts and when the idea ships.
Six questions most people ask before they post.
An idea is a request for a feature or improvement that is not in the product today.
Something broken? That is a bug. Please contact Support so they can help you.
Yes. If a similar idea exists, vote and comment on it instead of adding a new one. Duplicate ideas split the votes, so no single idea shows how many people want it.
You get an email when the status of your idea changes. To follow an idea you did not post, subscribe to it.
An idea can be closed for one of these reasons:
Closed ideas stay searchable, so you can still read the comments.
The quickest way to make an impact is to back an idea that already exists.
Open the idea and select the vote button. Voting shows us which ideas matter to you. You need to be signed in to vote.
Open the idea and add your comment. The most useful comments say:
"I agree" helps less than a short example from your own work.
Select Subscribe on the idea. You get an email when the status changes or when someone replies.
Submit a new one. Use a clear title and describe the problem, not only the solution. Then we can see what you need, even if there is more than one way to solve it.
Have a bug or a question about how a feature works? Contact Support instead.
Scenario: A customer creates a ticket and I forward the ticket to a fellow agent for their input. Currently if they reply to this it inputs their comment as a public note. The customer then receives an email with the public note included.I would like to request the feature to be added that if an agent in your organization replies to an email for a ticket it is entered as a private note.Or if an agent replies and it is still entered as a public note, a way to turn off external notification of public notes to people outside our company while still allowing our agents to receive public note notification.Thank you.
When a customer uses the helpdesk, a lot of the time they only provide their email address instead of signing in with Google/Facebook etc. This means I only have their email address and I can't address them by name. I've noticed that by searching their email address in the Gmail search bar, it actually finds their Google profile even without any previous correspondence from them. Is it possible to integrate something like this? A service similar to Smartr (Xobni) would be awesome but I understand that is pretty complex. I believe uservoice have a "customer dashboard" or something similar which works like this - it basically just tries to fetch social profiles by email address and gather a bit of info about the person and sometimes even a picture.
I'd like to make a rules with tickets, which assigned to certain Agent or group, or unassigned (for example I need to send a email to the group)all my rules can be more flexible if we have "Agent" and "Group" in "When should this rule be applied?"
It would be great if you could add a customer number or customer reference box for the customers.I.e when you edit a customer there would be a box saying Customer Number : ________It would be even better if that were searchable as well.Any large scale organisation uses a reference or number so I can't imagine we'd be alone in finding this useful.
it's a bit like this one - Move open tickets at the top of the ticket status page
Our developers would really like to see a way to work with a release planning. Incoming tickets from our customers are now tagged with "releasenumbers" to group them.What we would like is a way to - Add a duplicate functionality to tickets to group different features with eachother for the new release- To group tickets underneath one ticketAre there any features from Freshservice that will become available to in Freshdesk?
I think that you should allow removing the helpdesk title on all paid plans. This is because some companies have logotypes (stylized text as logos) and so after adding the logo the company name is displayed twice.I realise this can be changed on the garden and estate plans, but I think that like adding a logo, it should be available on all plans via a checkbox.
Explanation: The FreshDesk system currently has a message that says "user already exists" and forces you to choose the existing user while attempting to add a requester with more information than the same existing requester. If the "new requester" has more information than the existing user, the new information is forgotten and is not appended to the existing user.Example: Existing Customer has First Name and Email only. New requester (same Customer) has First Name, Last Name, Email, Company, and Phone number. All the additional information from the "new requester" will be forgotten and will not be merged into the exiting Customer that we were forced to select.Additionally, sometimes the existing Customer/Company information is misspelled or incorrect. There is no easy way to quickly edit/merge/overwrite/duplicate/delete this information on-the-fly while creating the ticket. A busy call center does not always have time to go back in and manually edit/merge/overwrite/duplicate/delete information. In this case many false duplicates are created and the ticket history is "lost" (disconnected from the "real" Customer/Company history) if the false duplicate is not later found and manually corrected.Summary: Our Customer/Company database is full of duplicates, incomplete and/or incorrect Customers/Companies, and contains scattered tickets that don't point to where they should. While the issue is mostly agent/data entry error, FreshDesk does not make it possible to make corrections, merge entities, or overwrite requester data while making a new ticket. In fact, it almost works against you by forcing you to select the incomplete/incorrect existing requester without the possibility of adding/merging the correct/additional information. Since each new ticket has the potential to create a new false duplicate Customer/Company, my request is to make the requester field more functional allowing for agents to edit/merge/overwrite/duplicate/delete existing Customer/Company information on-the-fly while still inside the New Ticket submission screen.
When using the Chat Transfer feature, in addition to Available Agents list, would be helpful if agents could transfer to a group defined in the Help Desk.
Hi,Currently there are many types of save button in the agent portal and this is confusing - for better usability it would make sense to only 2 buttons.[Save] [Cancel]This will cause much less confusion (the save and close button is often misunderstood as a "Save this button and close this window" button)For adding lots of tickets on bulk I would suggest adding a checkbox under or beside the button that asks you if you would like to create another ticket after this one - as below.[ Save ] [ Cancel ][ ] Create another ticket upon saveSave and close seems pointless as this can be done by setting the status to closed within the window. but if you needed to keep this action then, again this would be better dealt with as a Check Box.[ Save ] [ Cancel ][ ] Create another ticket upon save[ ] Automatically Close this ticket upon saveThis provides a much less confusing interface for people and I would think make it easier for everyone.
We don't bill support time spend, Our clients are all in Costumer support time contract, Our Agents don't get paid by the time spend. WE just need an automatic way to know how much time a n Agent spend resolving the tickets, so we can measure performance or time spend on clients also is useful to know which clients hogs more of our Agent's Time. Simple, after the Agent do the first repones or since is the ticket assign to him (able to choose this variable will be nice) so until the ticket is resolve or closed (also able to choose which of those states stop time will be nice). See? so we can click on any ticket and see how much time took to resolve or if is still open how much time has taken so far. But with no input from the Agent, but automatic, since I don't want the control of time on hands of the agent. Thanks.
Hi,We have situations where we have large companies with different departments and also have another third party supporting them.They only want their tickets seen by the people in that department and the person from the third party who looks after them as well and will also log tickets on their behalf.All of the company have the same email address eg. @company.comThird party are @thirdcompany.comIs it possible for the Contacts to have a department\project filedThe project field you can assign to any user no matter which company they are in and allow them to view all tickets from that project\department etc...The other way would be to have the option to create a group and add the users who are releveant to the tickets. You would then add the group to the tickets to give them access. (like having an access control to individuel tickets)Currently we are trying to work around this by creating the companies as the projects however this is a problem for people who are in both projects and require access to both areas as you cant assign them to two companies....Is it possible to two another fields added to the contacts for their departments and optional projects and only allow the to view all tickets related to that department or project.Would also be nice if could also allow 3rd party companies to also view certain
Loading your ideas...
This ideas board reflects customer feedback and our current thinking, and is provided for informational purposes only. Roadmap decisions, including AI-related capabilities, are influenced by many inputs beyond customer votes, such as technical feasibility, security, compliance, and market conditions. They are subject to change without notice. Idea status labels (such as “Under Review” or “Planned”) do not constitute a commitment, promise, or legal obligation to deliver any feature, functionality, or timeline, and are not part of any agreement with Freshworks. Development and release of any product or feature remain at Freshworks’ sole discretion.
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.
