Skip to main content

Ideas Status Pipeline

Filter by idea status

Filter by product

8832 Ideas

jcapitan-shoreline
Skilled Expert
jcapitan-shorelineSkilled Expert

Attaching Existing Assets to Purchase OrdersNew Idea

The current process for associating existing inventory assets with Purchase Orders (POs) in Freshservice is a significant pain point. We need the flexibility to add assets already in our inventory to an existing PO, rather than being forced to create them from scratch within the PO or resort to cumbersome workarounds.There are two primary scenarios where this limitation becomes particularly problematic: Expedited Asset Entry: Sometimes, we need to get assets into the system quickly. Using the bulk upload option directly within the inventory module is far more efficient than individually adding assets to a PO. However, if these assets are meant to be part of a PO, there's no streamlined way to link them later. Addressing Oversight and Duplication: It's not uncommon for users to forget an active PO exists. They might create, assign, and meticulously log all relevant information for an asset directly in the inventory. Currently, the only way to link this asset to its corresponding PO is to delete the existing asset, losing all its valuable associations and meticulously re-entering the data within the PO. This is a time-consuming and frustrating exercise that leads to data loss and inefficiencies. Allowing users to simply attach or associate an existing inventory asset to an active PO would save considerable time, prevent data duplication, and maintain the integrity of asset records and their associations.

PeterAnderson
Community Debut
PeterAndersonCommunity Debut

Sort tickets by multiple columnsIn progress : Included in Product Roadmap

Currently, when viewing a list of tickets, you can add, remove and rearrange columns using the setting on the right-hand side. You can also sort the list using the setting on the left-hand side. However you can only choose one of the columns to sort by. For example, say you have columns for Priority (low, medium, high) and Status (open, in progress, resolved). You can choose to sort by Priority (asc. or desc.), or you can sort by Status (asc. or desc.) - but not both. If you sort by Priority desc. for example, you get a list of all the high priority tickets first, then the medium ones, then the low ones. But out of all the high priority tickets at the top of the list, the Status of those tickets could be in any order. I’d like to suggest a feature that lets us sort a ticket list by multiple columns. This would mean that, for example, you could sort by Priority desc., then Status desc. This would give you a list of all the high priority tickets first, and out of those, all the open ones would be grouped together, all the in progress ones grouped after that, and then all the resolved ones grouped at the end (followed by the medium Priority tickets, etc.). My desire for this feature is to sort my ticket list in such a way that I know that the ticket listed first is the one I need to work on first (be it the most urgent, the one I haven’t responded to yet, or the one that’s been sitting there the longest (or all of the above!)).

michaelrContributor

Force agents to comment when closing ticket + Mail-submit as a different userClosed for Voting

I have two requests / questions - these might already be possible, but if not would sure be a nice addition. 1. Is there a way to force agents to fill in a comment when closing a ticket? Currently some of our agents are replying with final details on how they solved the issue, and then close the ticket, so the user gets two emails at the same time.. I would cancel e-mail notifications for closed tickets, but other agents might not respond at all when closing a ticket, trusting the ticket-closed-notification to let the user know the problem has been solved.I'm trying to minimise the amount of e-mail notifications the users get, so I would like to be able to either force agents to send a comment before closing a ticket (so I can cancel the closed-notification for users) or send a comment and close the ticket at the same time, so that the user will only get one mail notification.2. Is it possible to mail-submit a ticket as a different user? or alternatively, is there a way for the requester of forwarded-mails to be the original sender and not the person who did the forwarding? We are constantly getting user-requests to our personal or work mails, and when forwarding them to the help-desk, the requester listed for the ticket is the agent who did the forwarding and not the user who originally made the request. Any info on how I can do either of these, or if they are in the future road-map for Freshservice, would be very much appreciated. Thanks, Michael

TomKApprentice

Improve New CSAT response view and dashboard accessNew Idea

We have recently moved to the New CSAT framework in Freshdesk. While the Advanced CSAT report provides the main CSAT metrics, the experience for reviewing individual customer comments and response-level feedback is now less practical than it was in the older CSAT report.At the moment, customer comments can be accessed through the Underlying Data option. This does work, and it allows additional fields such as Ticket ID, requester details, agent, group, and survey name to be added. However, this process is more cumbersome and less intuitive than the previous CSAT response view.The previous CSAT response view was more visual, interactive, and easier to use. It was much better for quickly reviewing customer comments, presenting feedback internally, identifying trends, and following up on specific service improvement opportunities.The current New CSAT response-level view is mainly presented as a standard table, which makes it less effective for quick review and presentation purposes. I also cannot see a straightforward way to add this response-level comments view directly to a dashboard for quick access and visibility.Requested improvement:Please consider adding a dedicated response-level view for New CSAT, similar to the older CSAT response view, with the ability to:View individual customer comments in a clear, visual, and interactive format See associated details such as Ticket ID, agent, group, requester, company, survey name, and response date Add the response-level view or a useful summary widget directly to a dashboard Export the response-level data, including customer comments Make customer comments easier and faster to access from the Advanced CSAT reportFrom a user perspective, the old CSAT response view was significantly better for day-to-day service review work. The New CSAT reporting framework provides the metrics, but the comments and response-level review experience feels weaker and less accessible.I believe this would be a valuable improvement for many Freshdesk customers, especially those who use CSAT comments for service reviews, presentations, customer follow-up, and continuous improvement activity.