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.
Hey there,It would be nice to have a form field that can be added to service requests items in FreshService that accepts pictures when copy pasted in. Much like the form field that I am submitting this idea in.Thanks!
Currently the only way that I know of to see this detailed chat data is to use the API, which is a time consuming process. I wish to be able to see a detailed table fo the data with key timestamps, and other information about ongoing chats.
Currently we are able to delete attachments sent by the customer, and we are able to completely edit the inital message (the description) sent by the customer. However, if a customer sends us an inline image we cannot remove it. This can be a compliance risk.
For example, right now we can filter by the tag “test” but we are unable to filter to all tickets that do not have the tag “test”. We would like to be able to filter with negative operators.
From a workflow action “add task” on the scroll down option (see below), it would be good to have an “Enter Text” option for us to put a placeholder on Due dates on task creation. This is so we can put due dates from information submitted by the business in the original Service Request A bit like you already have on Reader API’s below.
Dates can be anything at all from 1934 through to 2023 (for example) - no way of validating dates, I.e. Between dates, in the future, in the past etc etc If you have a new starter form, or a any other form with a date field, it should be possible to restrict the date value being entered. Also, it is not always necessary to enter a time as well as a date - should be an option just for a date field.
Freshdesk currently exposes the last names of agents (if set) to customers and provides no means to conceal it beyond manually removing the last name value from each agent profile. This is time consuming and will get overwritten if SSO integration is configured to sync Active Directory. Provide a setting to disable sending agent last names to customers.It is currently possible to completely hide the agent names, but this is not a desired alternative.
Hi all,I know this sounds like an active directory issue but thought I would post something anyways. Hoping someone has seen this issue or has a solution. The problem we are encountering is tickets will come into the dash that are not meant to be routed to our support email. Whether this is spam emails, auto replies, and general messages we have checked within our AD and there is no group or rule in place for these emails that are coming through. We get the full array, amazon replies to one of our employees in a different department, spam, stuff from our vendors meant for someone else in a different region. We have spam filtering on within Freshdesk and cannot seem to find the root cause of this issue, anyone have any ideas? We are going to contact MS as well, but this only occurs within FD so figured I would try both lanes to find a solution, even if it is a minor inconvenience.
There is a post from 10 years ago where a Freshdesk Agent said this would be fixed, but it doesn’t seem to work.When replying to a ticket, the template inserts and moves the cursor to the bottom. This means that the agent has to go in and manually find the part of the response they have to actually fill out.
Quite frequently we involve others when resolving a ticket by forwarding a ticket to them and asking for input. When a forwarded ticket contains attachments these attachments will automatically be forwarded as well and there is no option to remove them. I would love to see this option in Freshservice!
Please let us choose to have the “request for someone else” visible only for agents:
Would love to see a small range of quick buttons when entering time on a ticket. Even better if they could be customizable but something like 5 min, 10min 15min 30min 1hr would be a good start.We often see techs get going too quickly and the system doesn’t record the colon the preface a 5 minute entry with so they end up recording 5 hours by mistake. Reporting helps with cleanup but would be great to have these buttons readily on the page rather than having to open a submenu then type the specific format to indicate minutes vs hours.
Hello! Is it possible to add a filter on the tickets that you are watching? Thanks!
We’re using Freshdesk for internal support and use a custom Dependent Ticket Field that allows us to categorize tickets. The basic layout is “Department->Category->Subcategory”. The user submitting a ticket selects the Department (IT, Facilities, HR”, etc.) which in-turn displays department specific categories. They ten select a subcategory from a list of subcategories specific to the selected department and category.Since it’s not possible to create an SLA based on a custom field, we’d like to create automations that set the ticket due date based on the ticket’s Department/Category/Subcategory selection and priority.I can think or a number of scenarios where it might be very useful to be able to override the default SLA based due dates using ticket specific criteria and having the ability to set it in an automation would be huge.
Please have a PowerBI app template. Zendesk has this, why not Fresh?https://docs.microsoft.com/en-us/power-bi/service-template-apps-samples
I've been looking around, and haven't seen the request for this platform yet.When replying to a new ticket, there isn't an agent assigned yet. You can implement an automatic task linking the agent who replied as assigned agent, but the reply doesn't contain the agent's name.Or you have to type manual (beats purpose of using templates) or you have to manually assign an agent before pushing the reply button.We need session related placeholder (session_agent, session_time, ...).For now, we only have placeholder linked to the section you're working in, with above limitations as a result.
The Slack ServiceBot is a great resource to streamline engagement with our users directly in Slack. Unfortunately, the current ServiceBot’s permissions only allow Slack admins to authorize the app for installation with a Slack org but still requires each user to search for the app and manually install it before they can interact with the virtual agent. This prevents teams from being able to roll out the ServiceBot (or the slack user agent) to groups/teams/company wide. This is due to the ServiceBot missing the following two permissions that is common with most Slack virtual agents: “Start direct messages with people” “Start group direct messages with people”Adding these two permissions would grant the ServiceBot the ability to initiate outreach without requiring users to manually search and add it first after the ServiceBot has been authorized for an org. In practice, orgs that have approved the ServiceBot for use would no longer need to prod users to install the app and instead when a Freshservice ticket is updated, for example, the ServiceBot would start a DM with the relevant users thus introducing itself and allowing new and existing employees to engage with the ServiceBot right away.
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.
