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.
In the admin screen under companies, you should be able to set the email domain for companies. For example, for 'My Company ABC' anything comes in from '@mycompanyabc.com' automatically gets assigned to the company.
We use the prioritization matrix and would like to be able to prioritize Problems based on priority as determined by Impact and Urgency. Not sure why Urgency was not included.
It would be really nice if when you are looking at the profile of the requester to create a new incident or service request for them. When we are looking at previous tickets the requester had and they are having an issue that is not in the list, it would be able to create a new ticket for that requester right within their profile.
It would be really good if the contact location was automatically brought through from an Active Directory field, such as 'Office' or 'City'.
Hi everyone,When a contract comes up for renewal, it would be good if we could also attach updated contact paperwork etc. Currently, when you create the contact I can upload this, but the only way to get the opportunity again is to delete the contact and create a new one. This then removes the history of the contract.It would be nice if the history contained the attachments for each renewal and the current contact contained the newly uploaded documentsMany thanksSimon
Feature Request, or any alternate way to accomplish this. Using a field to categorize tickets. Have a process that looks at X number of tickets categorized a certain way, that counts how many of those tickets there are within a certain time frame (can be any time frame, but for this example, One Day). Example: So, say 3 tickets come in within an 8 hours period for "Break/Fix -> Computer -> Crash". The process sees 3 of these ticket and alerts us that 3 tickets that are categorized as computer crashes have come in. This would help us start looking into why we are having so many computer crashes. Another example: We have 7 stores call in to tell us they are out of flank steak. The system see 7 tickets for the set category, and alerts us it sees a trend forming. This gives is a heads up that we are having a sourcing issue with Flank Steak, and so we can begin looking in the issue before it spirals out of control. Thanks for listening.
Notifications is a cool feature however it is of limited value because it is not integrated with other processes, notably Change.We are required to notify our customers x hours in advance of a change to their software. I would like to automatically trigger a Notification (for a selected Customer) when a Change is approved and moves into the implementation phase.This feature is vital since Change workflow automation only support emailing Agent Groups and not Contact Groups.
I currently have three Freshdesk accounts. I have a 'normal' account, whatever that isI have an 'agent' accountI have a 'support' account (for writing this ticket). My question is, why all the accounts? Can't we have a single account for interactions with Freshdesk?
It would be nice to be able to hover over a ticket from the ticket view, and see a description of the request/issue, instead of the last note/reply.
It would be good if when you were in a ticket, and mark the resolution to Resolved/Closed, then it returns you straight to the ticket queue after you press Update.
It would be really handy to automatically report on Windows assets that have either 32 bit or 64 bit operating systems.
The default ticket queue view simply says 'created 7 minutes ago'. It would be good if you could display the actual time created instead. This would then make it easier to assign tickets when there is a shift changeover of agents.
The analytics are really good. However, they seem to be missing fundamental functionality....the ability to break down Service Requests by Service Item. Yes, this can be done in the reports section, but this is only a static report at a point in time. It would be good to be able to have this displayed on an analytic dashboard next to all of the other Service Request information.
It would be great if we were able to have a filter option of Service Item down the right hand side. Currently, there is only Category, but this only refers to Incidents.
It would be good to be able to amend dates and times of notes upon creation. This means retrospective/historical actions would have accurate times stamped against them.Possibly with the ability to restrict to certain agent groups, as we wouldn't want everyone having this option.
We have a Global Client that would like to send us Office 365 encrypted emails to FreshDesk, thereby keeping Sensitive information secure and compliant. Currently this is not supported by Freshdesk. Does anyone else think this is a great idea or have a possible solution.
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.
