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.
We need the ability to use custom fields in a canned response in order to integrate with closing tickets with another helpdesk system.
we try to automate a approval workflow and we need to send the approval mail to the event-performing agent or a group.actually, we only are able to setup a single agent
we need to write service request placeholders into ticket fields to build conditions, based on these fields.example: add [service request placeholder] in field [abc]
to setup more automatic workflows, we need to use service request fields as condition in workflow automator. if available, we could route different service requests to different groups
Hi,I really like the new Business rules!What I still find annoying is that All of the fields you create is shown in the Ticket view filter list for all agents. It would be really nice if you coud have the option to hide certain fields on that filter panel aswell.
Any way to add buttons to articles? Right now I'm using images, but this also means that if I have to change the style of the knowledge base, I have to redo all those images, instead of change the styling in one go in the CSS.I could use the <h> tags, but in that case it would be helpful if there were more than 4 available.Basically for me it's already 3, as accessibility asks for the use of only 1 <h1> and we would like to stay accessable for visualy impaired users. The title of the article would be <h1>, <h2> is used for subjects in the article, which only leaves 2 <h> tags for other use.
Would be great to see freshservice support the deprovision of users anywhere....We use OneLogin and this would save us having to manually do this step every time. I know the same question has been asked about Okta as well as your own AD Connector.
It'd be great to see analytics from canned form responses so that we can see the most common answers. We are currently having to host our forms elsewhere due to this but having canned forms in Freshdesk with this feature would be a game-changer!
My team would love to have the ability to quickly create a public link to a ticket that shared all of standard information that the requester would typically see like approval information, public notes, etc but without requiring the person viewing the link to login. Use Case: We use our ticket system as also a sort of purchase order system & delivery tracking. It would be very useful to provide 3rd party vendors access to a live tickets for tracking updates without having to grant them an agent account or make them the requester/CC.Potential Issues:This could certainly be a security risk for some customers. In that case some compensating control such as:a report of all created public links under reportingcontrol creating links at a group or role enforce requiring approval for any links
It would be great if the Analytics module provided the following functionality:When a report is exported, give option to use page tab headings as section headings in PDF. Provide ability to clone an entire page.Provide ability to change colours of graphs. Provide ability to resize legend. Allow sharing of reports with specific or multiple groups.
Freshservice analytics are great, but we'd like to be able to have agents build reports and be able to share them with groups, similar to sharing scenarios.Our IT team acts as the admins for our Helpdesk instance which encompasses many different teams, and this would help us build them a "starter" pack and have it shared with them to be able to build on top of.
In our serverless app we use the onConversationCreate event to put notes into our clients service now "work notes" field.We discovered that it creates a loop of comments going back and forth.example. 1) i make a note in freshdesk -> it creates a work note in their incident, it then creates a note in ours again ( they also update tickets with 'put' method api ) and it repeats .example 2 ) they create a work note which then updates our ticket with a note which then sends that note to them again and it repeats.Is there a way to stop the onConversationCreate event when they add a note via api to our freshdesk ticket?
I currently have a serverless that creates an Incident in ServiceNow when a ticket is created in Freshdesk. I have implemented the conversation create event and it works as it should, posting notes to the servicenow work notes fields. It puts both public and private notes into their serviceNow worknotes.Question - Is there a way of preventing the private notes from being sent over when the event is triggerred, only allowing the public notes to be sent?
I will be great if will possible to control contracts by companies. Example: A customer contract me to give 100 hours of support in a month. I need to inform the total monthly hours of this company and freshdesk controls when this time is over. If i inform the value of my hour, freshdesk can control the amount of revenue i have to receive from this customer.
We're trying to give our customers a single identity in our customer portal.We were able to link our test FreshDesk instance to our IdP and created a profile for contacts to login using SSO.However:- The contacts still need to activate their account - which they already did for the IdP and does not make any sense- When activating the account, they have to provide a password which nullifies the idea of SSOCan the password requirement be removed - or even better the activation mail?Thank you in advance,Best,Kurt
Currently when a customer updates a ticket it says Customer responded. But even after you have looked at it, it still says that for a while. When you have a lot of tickets, its not always quick to find the one that was updated. So could you have it that the updated tickets background changes to make it stand out from the other white ones. Once opened and closed it goes back to white.as it has been looked at.
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.
