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 trying to move departments into Business Workspaces successfully, it would be a BIG win for these Agents to be able to download all attachments in one click. Sometimes they are sent 10+ documents and they have to click to download each one individually. As you can imagine, this can be time consuming AND they have to remember each document they downloaded before going to the next one. I’m hoping that the development team will consider adding a “Download All” in the attachment section for Agent efficiency. Adding the image below as a location ‘suggestion’ for this button in the red box: Thank you for your consideration.-Leighanne
I moved all of our public data from a MediaWiki server to FreshService solutions. For the most part, people love it. However, I have found some issues that I’d like to bring up:Automatic Expiration of articles - Articles shouldn’t expire. I should have the ability to modify this so it is not an automatic thing that occurs. This has caught us a couple of times already where a page has returned to the Draft status and is no longer publicly available. E-mail Notifications - I should receive a notification when a solution goes from Published → Draft status. Right now, there is no way for me to know when an article gets unpublished by FreshService. Workflows - There should be an event “Solutions Article becomes unpublished”, where I can take a custom action if I would like to. Subscribe to Page/Site - I have customers that want to know when a change occurs. They would like to receive an email when a page they are interested in changes. This was easily done with MediaWiki, but isn’t an option in FreshService
When adding properties for subtypes in Assets there is a space that says the Hardware properties will be displayed there but it doesn’t show what those properties are. It would be nice if that area were a collapsible view of the Hardware Properties the subtype is inheriting for those of us who don’t/will never have it all memorized.
I just wanted to add this in as a feature request.Obviously with a busy support team, a queue can change every single time you view it.One of the most disappointing outcomes is when you finally revisit a ticket and notice that the user has replied on the ticket hours before, however, there was no clear notification that they had done so.If there were some type of Replied tag that would be visually noticeable on tickets that users have replied to (as the latest reply), this could be a major plus to stay on top of response times and resolution times as well as customer care in general.
Hi!I have found, that our requesters can’t read English! OMG! Yeah, they can switch their laguage setting to language of their liking, but it is so complicated for them, that I have written the manual for them in the knowledge base of the helpdesk (= Solutions) and I have made several translations in other languages too.BUT! Requesters are not able to read the manual (How to switch language) in their language, because they don’t know how to switch the language!So I’m asking you: Please, make the freshdesk avare of language setting in the browser and switch the language based on this (with the setup overide like any other modern app) or at least do language switch on the front page “…/support/home”.Thanks and have a nice day :)Sincerely,Karel
We currently have two groups set up in FD, with agents assigned to each, and some agents being part of both groups. Due to the volume of tickets, we need to unassign an agent from one group so they only receive tickets for the other group they are assigned to. However, unassigning them also removes their name from all open tickets in the group they were removed from.
We are implementing the CIS Critical Controls within our environment – one of the aspects of that which we need to consider is FreshService.For our agents, we utilize SSo to control the aspect of agent logins – however, for requesters/contacts, they simply use a FreshService username/password that they have registered with.One of the CIS Critical Controls is to disable/delete accounts where 45 days of inactivity have occurred. However, after pulling a requester record from the API, I noticed that are zero fields associated with the last login or “Days since last login”. Instead, you only get the creation date/time and the last update date/time.Is there a way to also add “Last Login” to the output of the requester API call?"requester": { "active": true, "address": null, "background_information": null, "can_see_all_changes_from_associated_departments": false, "can_see_all_tickets_from_associated_departments": false, "created_at": "2024-04-09T12:45:59Z", "custom_fields": { "alternate_phone": null, "fax": null, "notes": null, "alerts": null, "active": null }, "department_ids": [], "department_names": null, "external_id": null, "first_name": "John", "has_logged_in": true, "id": ######86458, "is_agent": false, "job_title": null, "language": "en", "last_name": "Doe", "location_id": null, "location_name": null, "mobile_phone_number": null, "primary_email": "John.Doe@SomeCompany.com", "reporting_manager_id": null, "secondary_emails": [], "time_format": "24h", "time_zone": "Eastern Time (US & Canada)", "updated_at": "2024-04-09T12:52:45Z", "vip_user": false, "work_phone_number": null, "work_schedule_id": null }}
Hello, I just noticed that liquid filter aren’t supported in webhooks in CRM automations. It works in Freshservice and freshdesk so why not in Freshsales CRM?
This is a quick how add Approval URL to API Bespoke Approval RequestsLike me, if you want to make a bespoke approval request via the API it says on the page https://api.freshservice.com/#create_ticket_approvalNote: "email_content" is an optional parameter for sending approval. If not provided, the default approval notification will be sent to approvers.Now it does not say much about how to add the “{{approval.portal_url}}” placeholder into your emails or approval requests via the API, which means when you send an email with a non standard “email_content” JSON it will not put this in automatically. However, a way has been found and I am posting it here so others do not get stuck scratching their heads for a day like me. I did this in PowerShell so convert to what ever language you are using. Convert this to how you wish. When hyperlinking, ensure you put an extra curly brackets on the placeholder for the ticket.$apiKey = "api_key:X"$headers = @{ "Content-Type" = "application/json"}$emailbodynote = @" <p>Dear {{ticket.requester.name}}</p> <p><b>Ticket: </b><a href=`"$({{{ticket.url}}})`">{{ticket.url}}</a></p> <p> This is an approval </p> <ul style="list-style-type:square;"> <li>Please click <span style="color: green;"><b>Approve</b></span> if you would like this call queue to be renewed.</li> <li>Please click <span style="color: red;"><b>Reject</b></span> if this call queue is no longer required.</li> </ul> <p>Please use the link below to Approve/Reject the request</p> <p><b>Approval Link:</b> | <a href=`"$({{{approval.portal_url}}})`">{{approval.portal_url}}</a></p> <p>Thanks Your Support Deptartment</p>"@# Approval Type ## $To_be_approved_by_Everyone = 1# $To_be_approved_by_Anyone = 2# $To_be_approved_by_Majority = 3$To_be_approved_by_First_Responder = 4$ownerIdOwner = 000000000001$body = @{ approver_id = $ownerIdOwner approval_type = $To_be_approved_by_First_Responder email_content = $emailbodynote} | ConvertTo-Json$test_ticket = 000001$myDomainURI = "https://domain.freshservice.com/api/v2/"$ApprovalURL = ( "{0}/tickets/{1}/approvals" -f $myDomainURI, $test_ticket )do { try { $response = Invoke-RestMethod -Uri $uri -Method Post -Headers $headers -Body $body -Authentication Basic -Credential (New-Object System.Management.Automation.PSCredential("", (ConvertTo-SecureString $apiKey -AsPlainText -Force))) $success = $true } catch { if ($_.Exception.Response.StatusCode.Value__ -eq 429) { Write-Host "Received 429 Too Many Requests. Waiting for 60 seconds before retrying..." Start-Sleep -Seconds 60 $success = $false } else { throw $_ } }} while (-not $success)I hope this helps anyone trying to do this.
The Advanced CSAT module looks great, and allows you to ask a question in the survey with a free text field for reply. We used this successfully in the old CSAT module and reading customer comments was very valuable to us. Support have just told me that the New Advanced CSAT doesn’t have a facility to see text responses! I can ask for them, but not see them!This was a basic and core functionality of CSAT previously, could it be added to the new advanced csat please.
Dear All,Greetings!We have received customer feedback regarding an issue with viewing attached files. Specifically, the zooming functionality is not working correctly when using mouse scroll buttons on desktop, forcing them to download the files instead.I kindly request that you add zoom in and zoom out buttons to the image below, similar to those found in Gmail. This would provide users to adjust the image size using these buttons.A screenshot of the image is attached for reference.
I would like to be able to subscribe to a rss feed and automatically create a ticket from the feed.We use rss feeds to monitor security incident feeds and receive alerts if they might impact us. Currently, I have to use a seperate mailaccount, subscribe it to the RSS Feed to receive updates and then forward them to the servicedesk.
Hi.Adding a Note would be an interesting feature to be available in Supervisor rules actions.Currently, such option is missing, and I can see I’m not the only one with this need, so, here it is:Please add the capability of adding a Note to the actions in Supervisor rules.Ref.:
It would be nice to scroll through a list of my assets based on manufacturer as well as filter on manufacturer.
Use case:Before you leave for holiday, add a colleague as watcher to all tickets assigned to yourself. You can already do this with a scenario. When you return, it's not possible to the same thing but remove watchers. It would be great to have at least one scenario action where you can remove all watchers.
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.
