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.
Hello When viewing the incident list we would like to be able to filter our custom fields to show ONLY those that have the custom field blank. We have been able to get around this using a dispatcher rule to automatically set our custom fields to the entry 'Blank' but this feels a little dirty. Thanks
When replying to a ticket, "To" field is auto filled with the client email address. But the "To" field is locked and can not be edited. My suggestion is to let "To" field unlocked and a staff user can edit that field.
The ability to Add additional requester in the case is critical item for us. A lot of times we add multiple people in the TO field. Use case: A group of people (but doesn't have group email address) are supposed to work on the ticket. If the email is sent to them then one of them will respond to the ticket. Do you have this feature request in the pipeline and if yes then what is the timeline?
Is there a way to block customers from making their own incidents or tickets? I only want this program for internal use and possible future emails to update customers about the progress. I noticed that one of my customers logs into the system and makes their own tickets, dont want them to do that.
We have recently started a push to make sure no one can access our Support portal without have proper paid maintenance. As such, we turned off the ability for customers to sign themselves up for the portal, this was step 1. However, since anyone that emails our support@ email address automatically gets an account created for them, this causes a security loophole. By the time we realize this has happened, they could have access something sensitive, such as software downloads. I had the idea to create a Company called "Approved Customers", problem there is you only allow a Contact to be associated with more than one Company on the Estate and above, we are not big enough to need that, we have 7 agents. I know you can restrict access to Solutions and Forums by certain companies, however, I am not going to go in there and type in each of our companies to all of our Forum or Solutions articles, that would be way too time consuming. Any other people running into similar issues have something they have done as a work-around?
I saw the integration for TeamViewer and would love to see an integration with ScreenConnect.
I'm leveraging the PagerDuty integration to send SMS notifications to my team. The integration works great to create incidents that I can configure for custom notification schedules. I've set up Dispatch'r rules that send to PagerDuty on Incident Creation and Incident Closure. Here's my problem: The communication to PagerDuty isn't anything other than "create incident". If the ticket is updated in any way in FreshService, such as moved to a different Status, Priority, or even reclassified as a Service Request, PagerDuty doesn't get notified. Conversely if I acknowledge the incident in PD, FreshService doesn't get that update at all. Is there something I'm missing or is this the best there is?
I am using the {{helpdesk_name}} tag in the open calls email ... my question, was not it to return the name of one of our technicians instead of returning the company name?
Hi,I´m starting my own HelpDesk company, and all my clients are external companies.Is it possible to have any of this points working?1. Multiple portals (custom logos, names, and colours for each client) with different ticket creation forms for each client (company), but using just one Dashboard, so we could have all tickets in one place2. Chat (When a client submit a ticket the "Chat Opinion" should be available)Thanks and keep the good work!
When an agent deactivates a customer profile (deletes) The customer should receive an email informing them of the task completion (Deletion) Hope to see this added
At the moment when either a Requester or a CC replies to a ticket, the same notification is triggered: Email Notifications > Agent notifications > Requester Replies to TicketI believe that a new 'CC Replies to Ticket' notification should be added. I also believe that at least 2 extra placeholders should be available for this notification (for 'CC name' and 'CC email') with more welcome (ie for 'CC phone', 'CC company' etc)
Is it possible for me to change the current items shown in the Ticket view @ the dashboard? I would also like a option to shows how many open tickets there are atm.
We have customers with their own Azure AD domains that we support, and it would be wonderful to let them log into our support portal directly from their own Office 365 account. Today, when we turn on SSO, we can integrate with our own company domain, but of course our customers who don't have accounts on our domain can't log in. If we could do separate SSO configuration per customer portal, it would seem to solve this.
I would like to see a function where we can sort Ticket templates and Scenarios by Topic/Group using a drop down menu. Agents could then first choose the Topic/Group and then select for the Template or Scenario. Search option becomes less efficient when you use multiple templates and scenario's.
I do a lot in asset management right now since we just purchased and haven't rolled it out to the users yet but I would like to see something in the reporting section being able to view reports based off the custom fields we add inside the asset. Also I know they are working on adding columns in the asset list but I hoping the IP address can get added and it will allow us to search via computer or device IP
It would be nice on Admin>Companies to search a pattern on the table, to find the company/department more quickly
It would be nice to customize portal on Garden plan as it's kind of inconvenient for my customers to use as they are always complaining. Also, Would benefit my business and there should be no add on fee. Hope this gets fixed soon
Hi, We have some services that send error mails to the servicedesk when somthing happens. Mostly this are external systems not under our admin. When it comes in its mostly from a no repy address. So when we accept the ticket or close it send a repy to the sender. When the mail address is configured to reply with a message you cant repky this can give a ticket storm... Mails bouncing back and fort ... So it would be nice if we can just select if we can choose to mute a ticket so it will never get replys in the mailbox for this ticket. And then we can make a rule if from requester mute ticket ... I dont know why this isnt a feature already does no one have this problem ? Tips are always welcome .... Kind Regards, David
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.
