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.
Hi,To have some sort of availability calendar for agents to include holidays, lunch hours, and shift patterns would very useful. The auto-assigning of tickets could then omit the times the agent isn't available. At the moment, we would be reliant on agents to manually switch the 'do not disturb' option on and off several times a day.
Placeholders on the fields when setting up Service Catalogue items. We would like to have more descriptive information in each of the fields on a Service Catalogue Item to direct the Requester in exactly what information we need from them. Having to 'suggest' what information we need by have a long Field Description isn't very end user or designer friendly
We currently have a need to share some views with multiple Groups of Agents. Currently we only have the option share a view with "Myself", "All Agents", or "Agents in a Group".I would propose changing "Agents in a group" from a basic drop down to a multi selector dropdown (like the filter text boxes).In our scenario, we have multiple locations. We have a Building 1 Team which we built a custom view for so that they see all unresolved tickets at that Building. However, we have some other teams that would like to be able to see this view too instead of having to manually filter each time.To facilitate this, we would have to create this custom view twice right now and share the first one with Building 1 Team and the other with Building 1 Escalation Team. Literally double the work any time we want to modify the view or create new ones for new locations.
Hi there. I am a new Freshdesk customer and like a lot of the features. One issue that I have found to be a problem.I have an an Timed Ticket automation setup to automatically email certain customers after a period of time. Everything works just fine (email is sent) but the auto-email is not shown in the ticket thread. I can see it was sent if I click on "Show Activities" button but I can't see it in the thread. I don't think this is a new issue - I found this support thread about it:https://support.freshdesk.com/support/discussions/topics/35025This seems like something that should have been fixed a long time ago. Is there any way to make this work?Thanks!Miles
Hello,One of the most requested changes when we onboard a new customer is to give them admin access to all their company tickets. At the moment this is something only the Agents can do but it is impractical. It would be a lot better if the company users were given an admin console where they can give different access/viewing rights to different users, depending on their needs.Regards,Gabriel
Hi,we have a problem with the email sender name on an automatic reply from freshdesk for a new ticket. How can we set the sender's name to be the desired name and not the default "support"?In short, we want the subject of the email to be Infenso Support and not the default "support", a picture is attached.Kr, Leo
Is it possible to set up an automation based on tickets where I am the watcher? If not, could I automatically add a tag to a ticket when I am added as a watcher?
A feature our organization uses a great deal is Ticket approvals. We're a school district, and when a Ticket is created at one of the schools, the principal must review and approve it first. They don't need the full power of an agent, just some view access to tickets in their buildings and the ability to approve or deny a work order - with notes would be a nice touch. Added bonus - implement the approval process without having to make the principals "agents" to save some money!
We would like to have an action available in the Observer Rules to remove a tag.This would allow us to implement some workflows that are not currently possible.
Hello There, I find the inventory module to be very basic and hence limiting in terms of use cases that it can serve. For example, It's only obvious that I would want to hide some of the assets from some of my agents/users. But the only two ways I could find to do that is by using either of these 2 flags (see screenshot below). while defining my `Roles` Now, firstly this is a non-feature disguised as a feature. Because the combination of two flags only allows you to either:-- show everything to everyone or - Show agents only the assets that are assigned to their Group. There is a reason ITIL defines Asset Management specific roles. You cannot disregard them completely and still call a product ITIL compliant. This all or nothing approach for Asset Visibility is not only limiting, it starts dictating (as a side effect of missing adequate Asset Roles) how I should design my Support Groups. In our setup, we have created Groups so that I can hide certain assets from other agents. I don't want my Asset Visibility feature to start dictating the design of my support group, I am forced to do this because the tool doesn't have a sophisticated asset visibility mechanism. I guess I'm repeating myself here, I hope made the point!?!Not only this, the tool assumes that a `Group` is a way to segregate ’items’ in ITSM tool. A complete misappropriation of the concept of Groups in ITIL. A Group (Support Group) should only be to segregate tickets. Assets can be managed at different levels by different people in different ways. Few examples, I might want to give different levels of visibility to people in the same Support Group. A team lead might have access to all the items on the Group while a team member may only need access to fewer assets. This applies to the "Asset" level as well as "attribute" level. Say a team member can only see the serial numbers but not the asset ID or something like that. At the attribute level, it might look too specific but still desirable. There is a fundamental design problem here that is handled in a “let’s reinvent the wheel” way. We don’t have to. ITIL has already done that for us, so let’s just stick to what works. Why should my use case to hide assets govern how I design my support system? (Support Groups in this case). Support Groups and Asset Visibility are two different concepts and should be decoupled. It pains me so much that basic things like these have to be reported in order for FS to consider it as a feature. I am obviously pointing out only the Inventory Module here but these patterns (or rather lack of it) are spread across all the modules. Problems that ITIL has solved are being tackled very wild-west ways. This sets the product on a very unpredictable trajectory, a roadmap that is anything but ITIL/ITSM. And this scares me. Some day when I run out of patience I might write a long post for all the other modules as well. But for now, this should serve the purpose I hope. Is it just me? Or others feel the same way? Feel free to call me out if I sound like a snowflake.
When our agent tries to CC one of our third parties, we receive "Message not delivered -Message bounced - Temporary error" from them. I inquired further and they investigated server logs and saw the following :===email server paste===2020-08-19 15:22:33 ProxyMatch, ProxyDeny: SMTP Classified as confirmed SPAM, pri=6, disp=Deny, policy=SMTP.IN.02-00, protocol=smtp/tcp, src_ip=3.120.181.192, src_port=60529, dst_ip=195.244.65.20, dst_port=25, src_intf=0-SoneraOut, dst_intf=105-Net65.0Mask27, rc=595, proxy_act=SMTP-Incoming.smtp, sender=bounces+1.1472028-asiakaspalvelu:liikku.freshdesk.com@emaileuc.freshdesk.com, recipients=laskutus@cash-in.fi, 1BFF-0019, geo_src=DEU; geo_dst=FIN===end===They whitelisted IP 3.120.181.192 (which seems to be the Freshdesk server), but the error still persists and our agents are unable to send emails.
Are there plans to include a gmail gadget like the one in freskdesk?
Half of the default sources do not apply to me, and also they default to sources which are not correct (for example email creates ticket, but ticket says source was portal).I'd like to modify the sources to suit our company's needs.
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.
