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.
On our website, we have a contact form requesting a customer to give us his phone number with his message. This contact form send an email in Freshdesk -> creating automatically a new ticket -> creating automatically a new contact in Freshdesk database with the email of the customer.Is it possible to automatically add the phone number in the Freshdesk database ?Exemple, when a new ticket is created, we receive : Name : FrédéricEmail : frederic@cozic.frPhone : 06xxxxxxxxMessage : blablablablThe new Freshdesk contact contains only the email frederic@cozic.fr without a name our a number.I would like the new Freshdesk contact contains email + Name + Phone Number.It's an important feature for us, because we also use Freshcaller and that's a way to regroup email contact and phone contact.Thanks for the help
I'd find it useful to support sending message to more than 20 slack channels, as we're going to be having around 50-150 groups and slack channels.To make it simpler to setup slack notifications via slack instead of email, I'd be keen to be able to set each group to have an optional slack channel. Then I can setup integrations, if there's a new reply or ticket assigned to the group send a message to the slack channel for the group, without having to setup a separate automation for every group.
We've submitted several times from the Feedback widget we've embedded in our website, and receive the 'Thank you for your feeback' message. But these submissions never come through to our Freshdesk dashboard, or our email.The website is herehttps://www.saca.org/
Need login and my password or my email is incorrect and I don’t know what do
Hi guys,doest it SSO work as automatic login or you have to fill username and passowrd too ?Is there any way how to automaticly read credential from logged profile?Thx and bestMartin
Facebook comments and messages can currently be converted into Freshdesk tickets and thus answered via Freshdesk. However, we can not implement Facebook into Freshdesk until all of Facebooks other features to handle comments can be handled directly in Freshdesk: Like Reply Hide Comment Embed Comment
I have configured SAML SSO with G Suite as my idP . This works fine.BUT users can still navigate to /login/normal, and login with a uname/pwd. if they have no password, they can hit 'Forgot Password' and are sent a reset link where they can set a password.The purpose of SSO is to centrally manage accounts and authentication.There is no point if users can simple go AROUND the idP and generate their own login credentials.Is it possible to DISABLE normal login when SSO is active?
Distinguish between Firstname and Lastname In the system we now enter 1 Full name But over here we sometimes use only the Firstname, sometimes the last name: It can also differ per product ...... The system should have 2 fields, or at least a second field called "Shortname" so we can use this as a placeholder too https://snag.gy/IbK82M.jpg
When a FD user who is also an agent fwds an email, a ticket is created on behalf of the original sender (assuming this option is turned on). The issue is that if the FD user adds some commentary to their forward, this is included as a part of the ticket and would be included in the Agent' reply and visible in the ticket to the requester. This commentary could include notes meant ONLY for internal eyes so this presents a huge problem. It would be ideal if this text could be put in a private note instead. Anyone have any solutions to this?
The general idea seems that you can use [#TICKETID] in your subject line to append said email to an existing ticket.This works, HOWEVER, if you forward a longer email the actual email content does not get added in the ticket, only whatever you type before you forward the email (at the very top of the email chain).Any way to easily forward an email to a ticket?
Automatically select a group based on the 'from' e-mail address when creating a 'new e-mail'. When creating a new e-mail, the first thing you have to select is the 'from' address. Later on you have to select the group. In our case, one e-mail address is linked to only one group. It would save a lot of time if the right group is automatically selected based on the e-mail address.
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.
