Recently active topics

For a few months now, the “print ticket” function has not been working for me in Firefox. Current browser version is 149.0.2 on Windows 11. Printing tickets used to work in my Firefox browser several months back; I don’t remember exactly when it stopped working.Behavior: When I click “Ticket drucken” (“Print ticket”), as shown in the screenshot, the pop-up window simply closes and nothing further happens.When I switch to Google Chrome, the function works flawlessly.

Please give a quick overview of your product feature request or feedback and note who in your organization is affected by this issue [ex. agents, admins, customers, etc.] (2-3 sentences)When creating views in the Admin < Workspaces < Views, the names of the views are hardly readable as the table shown in this overview does not fit to the screen size/resolution of my monitor. You cannot expand the column width. I use the :: to create folders in the views, e.g. Customer Success::Felix::All open tickets, which is hardly readable. I would need to hover my mouse over the name to view it.What problem do you see this solving? (1-2 sentences)It would help with keeping a better overview of all the created views and their “folders” When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences) It occurs constantly, there’s no workaround. Are you currently usin

I sincerely welcome the launch of the new Zendesk Community.Based on the announcement I read, I was especially encouraged by the following statement:“Improved moderation standards & capabilities, so you no longer need to wait for a human to approve your post.” This is a wonderful improvement, and honestly, it was one of the reasons I felt hopeful and excited about the future of the new community.However, based on my actual experience, this improvement seems to apply only to creating new posts.When I try to reply to an existing post with a comment, I still receive a notification saying that my comment will be reviewed by a moderator before it is published. This has created a very real and serious challenge for me.I am located in Korea, and when I reply to another user’s question via a comment, the moderator responsible for approval appears to be in the United States. Because of the time zone difference, moderators are often asleep when I post my response. As a result, my comment is

Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. (2-3 sentences)I would like to be able to collapse the call transcription, when created in a talk ticket. it makes sense to be able to do so as some calls can be very lengthy, with the transcription taking up so much room.What problem do you see this solving? (1-2 sentences) It will stop ticket lengths being longer than they should be.When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)We turned off the option to see transcripts, not utilising the feature and its benefits.Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)No current work around or option to choose this, to my knowledge.What would be your ideal solution to this proble

When viewing Users list under Organization > Users there is no visual indication if User is active or not. Both Active and Suspended users are displayed in the same way in the list. It would be very helpful if any kind of visual indication of User status would be visible in this list so Agents and Admin viewing the list could easily distinguish Active from Suspended users. 

On the agent dashboard --> Customers ... any customer who has had their account suspended shows "Suspended" beside the customer name. I was wondering if the same thing could be applied at the "Organization" view of the "Customers" list? 

We sometimes have people spoofing our execs and I do a sweep through user accounts to see if there's any more that pop up.  When I do a search for a user name, in the example below, I see 9 hits.  Only one of them is legit, the other 8 are all bogus entries that I've suspended.  There's nothing on the screen here to tell me I've already looked at them (because they are already suspended).  Can we:1) have some option for additional fields here, or include whether or not a user is suspended in this list, and2) have an additional option to filter users in the filter tool for active vs suspended?  I have to manually open all of these to verify I've suspended them.  I should be able to see this at a glance.

Presently, there is a filter to show Suspended users only, by means of a checkbox. That means it is impossible to view non-Suspended users only. In fact, I often want (and I expect many folks often want) to see only non-Suspended users (that is, to hide Suspended users), and I would prefer to set that as the default.

I have been trying to jump into the Deletion Schedules pool this week and have found some extreme things lacking.  Hopefully I can build a case for these 4(ish) suggested features: 1) Out of the box, there are only two conditions you can set (unless you buy an advanced package) to control what is included.  The first is hard coded.  It shouldn't be hard coded.  Let us have two conditions that we choose please.  Zendesk has selected “Last Updated”.   That's not a bad selection, but when you look at the previewed results, you don't even see that field.  The field you see with a date is “Last active”.  This is confusing.  (A preview, by the way, should at minimum also include the Ticket ID, pretty please?).  I was hoping for some way to identify tickets in my case that were created from 0 to July 31, 2022.  There's no way to do that.  Or, alternately, to be able to set a condition by the Solved date.  That would be nice

Working in Support, I have a preference of opening up multiple tickets at a time, so they appear as their own, separate tabs, in order for me to visualize and prioritize the work tickets i have to take action on. Example below:

Human could make mistake. Agents cannot avoid such situation. Hope Zendesk can consider the Unmerge function to allow solving of human mistake.     

Please give a quick overview of your product feature request or feedback and note who in your organization is affected by this issue [ex. agents, admins, customers, etc.] (2-3 sentences)https://support.zendesk.com/hc/en-us/requests/new?ticket_form_id=7299885911962 - please don’t clear the "Description" field when returning the form to the user on errors. Everybody who can sign up for a Zendesk account is affected. What problem do you see this solving? (1-2 sentences)https://support.zendesk.com/hc/en-us/requests/new?ticket_form_id=7299885911962 - when I submit this form with, e.g. “Which product do you need help with?” not filled in, then it comes back a) with an according error message - OK, b) with the "Description" field cleared and all my input there gone - NOK. When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)Yesterday. I had to retype the

We're requesting the ability to explicitly set a ticket field to null (empty/cleared) using the built-in "Update ticket" action node in Action Flows. This affects our entire support operation, as the flow in question runs on every single ticket and is responsible for dynamically setting field values based on other field conditions.What problem do you see this solving?There is currently no way to clear a ticket field value through the "Update ticket" node, which means action flows can only add or change values — never remove them. This makes it impossible to build fully reversible automation logic where a field should be unset when certain conditions are no longer met.When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business?This affects us continuously, as the flow executes on every ticket. The core issue is that when an agent sets a field value by mistake, the action

1. We have many custom object lookup fields but due to this limitation mention in this articlehttps://support.zendesk.com/hc/en-us/articles/4408824384538-Reporting-with-custom-fields?Z2_EN-US%5Bquery%5D=custom%20object#topic_glv_tww_23bWe are unable to report of custom object lookup fields.2. The custom object records page is limited in its display options. Currently, it only shows the default columns: Name, Created at and Last updatedIt does not provide the ability to add other object fields as columns for viewing. 

I can see this has previously been flagged here: https://support.zendesk.com/hc/en-us/community/posts/4409222690586-Restrict-agents-from-changing-Display-Name  But i want to take the opportunity to re-raise this issue.  From a point of legal and admin concern whereby we notice numerous agents incorrectly changing their name or alias for one reason or another. Not only does this cause issues for reporting and admin but also potential PR concerns as aliases are user facing.  Due to the size of the organisation, flagging and chasing agents is unproductive and we'd need a more tech supported solution.   

We're requesting that the Help Center Redirect Rules API be updated to support passing query parameters from the source URL through to the redirect target. This affects our support operations and web development teams, who use vanity URLs and dead urls that may redirect or end up at Help Center web forms. Without query parameter passthrough, we lose the ability to pre-fill ticket fields via URL parameters after a redirect fires.What problem do you see this solving? (1-2 sentences)Currently, redirect rules strip all query parameters during the redirect, which means any context embedded in the URL — such as pre-filled ticket fields, form IDs, or tracking parameters — is silently lost. This forces end users to manually re-enter information that could have been populated automatically.When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)This issue aff

Currently, AI agents can only be edited by an administrator.We believe that it is a security issue that only administrators can operate an AI agent, which is a single function, so we would like to see the ability to assign privileges through custom roles, etc.

Based on https://support.zendesk.com/hc/en-us/community/posts/360046933933/comments/360011763093 Submitted on behalf of myself and @Maggie St. Clair Feature Request: Add the ability to mark all users of an organization as suspended Description/Example/Use Cases/Proof of End-Users Requesting: https://support.zendesk.com/hc/en-us/community/posts/360046933933/comments/360011763093 Use Case: When an organization is no longer a customer, my company has to go through every single user individually in that organization and mark them as suspended. This is time consuming and can lead to missed users.