Discussions

is Oauth token expiration for oauth using client credentials grant type also? I am trying to create a new OAuth client using client credentials to test token expiry and obtain new tokens. But get not a valid grant type error. Is the grant type restricted to only one oAuth client?URL used is url = "https://gsmls.zendesk.com/oauth/tokens”If i use the existing Oauth client to get token  get below error“{"error":"unauthorized_client","error_description":"The authenticated client is not authorized to use the access grant “

(New to Zendesk :)) We are bringing a particular assignment process into Zendesk. Our agents are assigned to clients individually and rely on a “Show Name" field to ensure correct work is being accomplished, per show. Our agents do not have faith our clients can consistently write their show names in manually (they are probably right) and are looking for something to automate the process so the correct Show Name is appearing on the ticket for work in our system. We are looking at the use of Organization Fields. “Show Names” field would house their past/current/future show names. We also have a written text field “Show Name” that is exposed to the End-Users. We cannot expose all of our clients show names, due to privacy. Is there any way to automate the "Show Name” field into the ticket for end-users to select (based on which Organization they are in)? Or is there a way to automate the written field to match that internal Show Names field via tags and triggers or Action Builder?  Thank

Hi allI’ve read and re-read the Action Flows articles and tried to make some basic ones of my own but I just don’t understand what I’m doing wrong or what all the technical terms mean. I’m not a developer, I’m an admin trying to build basic things like “If a ticket has a specific tag added to it, add this task list to it” but I just can’t figure it out. The inputs, variables and all the other things are so complicated to understand.I don’t see an Academy course for Action Flows and all the videos I can find that talk about it are very high level and don’t explain everything that I’m seeing. Is there any content I’m missing or can an Academy course be made for this? I like to think I’m at least of average intelligence but I just can’t wrap my head around Action Flows!Thanks!

Hi,I'm looking for a way in Zendesk to group edit and reorder macros. We have over 500 macros in our account, and doing it manually takes a lot of time and is tedious. Is there a way to fasten this process?

Hi, we are trying to connect our AI Agent to a custom crm api connection that we created within Zendesk, but the current documentation seems to reference how it was done before the merge of Advanced AI Agents into the base AI. Does anyone know how this is currently connected?  Thanks in advance John

I’m scanning through the recommendation from Admin Copilot and there are a number of “Create an article” suggestions. These are recommendations that I create articles for FAQs for which we already have articles. And when I click in the “Related tickets” for the recommendation, it’s quite clear that the AI Agent (Essentials) has replied appropriately to the end-user’s request based on the existing Help Center articles.Our Help Center is 98% locked down - the only 2 anonymously viewable articles are “How to Use this Support Site” and “Legal Notices”. Everything else requires authentication, which is required by our InfoSec team due to the subject matter in our Help Center. Is Admin Copilot basing its recommendations solely on anonymously viewable articles? If so, it’s basically useless for us, and in fact, a distraction (since most of its recommendations are to create articles that exist).

Today I got a 2nd email announcement about the coming end-of-life for AI Agents-Essential. This email notes that the changes are rolling out starting April 27 (i.e., 2 days ago). But if you link to the announcement post, you’ll note that the rollout has slipped a month (to May 25-June 12) with no change to the end-of-support/end-of-life dates.The post also notes “In the coming months, we’ll share detailed timelines, transition plans, and guidance to help you transition to the upgraded AI agent experience.” (emphasis added). Those details, plans, and guidance should be in place now. The schedule has barely 2 months from the end of the rollout window until the end-of-support date.We have a Professional instance - no sandbox. Any changes we need to make are to our production environment. This is fraught with risk. Setting up AI Agents-Essential for email was trivial and works well. Reading the documentation for email for AI Agents-Professional makes my head spin with the level of complexi

I am trying to prepare for the end-of-life of AI Agents-Essential, and since we are Suite Professional, not Suite Enterprise, I have to do this in my production environment. So the risk of breakage is very high. I’ve built a set of automations and Agent SOP around the AI Agents-Essential behaviors and I cannot find sufficient documentation on the new AI Agent email behaviors to have any idea how to make things work the same way.For example - I have triggers for the ar_suggest_true and ar_suggest_false tags being set on a ticket. to guide my Agents? When a ticket is tagged ar_suggest_true, the Agent reviews the AI Agent’s response and unless it’s clearly something they need to manually address, move the ticket to a custom Deferred status, taking no further action unless the end-user indicates that they still need help. Conversely, a ticket tagged ar_suggest_false gets priority because no response has been sent to the end user.Do these tags still exist with the new AI Agent? Is there som

I've figured out how to schedule replies in Zendesk!! Using a combination of triggers, tags, automations, and ticket types, it actually is possible to send with an approximate delay.  Because automations run only once each hour (at the same time every hour for your own account), this won't be exact; it's accurate to within about an hour. For example, if I'm replying on Saturday morning (but I don't work weekends!), I can delay the email 47 hours to have it sent Monday morning.  Similarly, if I work Sunday afternoon, I can set the email to wait 18 hours and show up on Monday morning...and so on. Here's how to set it up: Step 1: Decide what your tags will be to manage this I used "delay1", "delay2", etc. Adjust these times based on when you're likely to be writing replies, and when you want the emails to be sent. I've set up my preset delays to be 1, 2, 4, 8, 12, 18, 24, 36, 42, and 47 hours.  This will allow me to work any time I want, and then have the email be

Hello! I’m working on setting up some advanced AI agents right now for email. We have patients & staff both send questions to the same channel. Ideally, I’d like my AI agent to only respond to questions from patients, not from staff members. However, although I’ve set up instructions & use cases for this, it continues to just respond to every question during testing. Does anyone have suggestions on how I can get it to automatically send questions that don’t pertain to set up use cases directly to live agents?

Hello, with the new Suggested Assignees EAP (no group created in Zendesk Community) it recommends users who are no longer agents in Zendesk. We typically remove the agent license and adjust them down to End User, however, I also attempted to suspend the user but they were still recommended.

Hey Community! Today we’re hosting a Digital Desk webinar on Admin Copilot, and I’d love to keep the conversation going here!For those using Admin Copilot, I’d love to hear what’s working for you:How are you using it in your instance? Any helpful insights, recommendations, or cleanup opportunities you’ve uncovered? Any tips you’d share with other admins?We’re also hosting the webinar again on July 23rd, so I’ll link the registration here for anyone who is interested!Looking forward to learning from this thread!- Emma CollinsSr. Content Manager, CX Programs

Hi, hope you are doing well!The metrics I check most often in Zendesk are CSAT, first response time, and resolution time. They help me understand how satisfied customers are and how efficiently support requests are being handled.I usually set goals by looking at past performance and making small improvements over time, rather than aiming for unrealistic numbers. Reviewing reports regularly helps me spot trends, like recurring issues or slower response times, so I can improve workflows or update help center content when needed.I don't rely only on numbers. Customer comments are just as important because they explain the reason behind the ratings and often highlight areas that need attention. For me, the best way to measure success is by combining performance metrics with customer feedback to continuously improve the overall customer experience.  ThanksIfra Saqlain  

Problem StatementThe iFrame app is a ticket sidebar application that provides embedded access to external web content directly within the ticket context. It dynamically renders a configurable URL inside the sidebar, allowing agents to interact with external tools and workflows without leaving the ticket view. Location: nav bar. PromptCreate a nav_bar app called "Iframe" that embeds an admin-configured external website inside Zendesk Support, allowing agents to quickly navigate to an external resource and return to their tickets without interrupting their workflow.The app requires one install-time setting: **Iframe URL** (parameter name `iframeURL`, type: url, required). This is the external website address the admin enters during installation. On load, retrieve the setting by calling `const metadata = await zafClient.metadata()` and reading `metadata.settings.iframeURL`. Do NOT use `zafClient.get('setting.iframeURL')` — that is not a valid ZAF path and will throw an APIUnavailable erro

Hello. Following this announcement https://support.zendesk.com/hc/en-us/articles/10955445787546-Announcing-outbound-calling-restrictions-by-agent-group-for-Voice, it is now possible to configure which groups are authorised to make outgoing calls by line. Is it possible to apply the same settings to external numbers? (which are, in fact, only used for outgoing calls) 

Hi Zendesk team,I’m currently building reporting around our use of Agent Copilot (Auto Assist), and I’m trying to better understand how to accurately define and extract “eligible tickets” for AI suggestions.Specifically, I’m looking to identify:The set of tickets where Copilot could have generated a suggestion, regardless of whether a suggestion was actually surfaced or accepted.I’ve reviewed the available dashboards and metrics, including:“Enriched tickets” in Intelligent Triage Auto Assist usage metrics (auto assist vs non-auto assist tickets)However, I’m not sure if either of these directly represents the population of tickets where AI suggestions were eligible to appear.My questions are:Is there a field, attribute, or dataset in Explore that identifies whether a ticket was eligible for Copilot suggestions? If not, what is the recommended way to approximate this population for reporting purposes? Is “enriched tickets” the closest proxy, or is there a more accurate method?My goal is

For our team, it's really about balancing the numbers with the overall experience. Metrics are important, but they don't tell the whole story.The metrics we watch most closely are first response time, time to resolution, ticket volume by category, and CSAT. First response time lets our users know we're engaged, while resolution time helps us identify where processes might need improvement. Looking at ticket trends is especially valuable because recurring issues often point to opportunities for better documentation, training, or system improvements.Our targets are based on the priority of the request rather than trying to fit everything into the same SLA. A critical issue affecting multiple users is going to have a much different response expectation than a routine service request.One of the biggest benefits of tracking this data is being able to spot patterns. If we notice an increase in tickets around a particular application or process, we can often address the root cause before it b

I learned how to use the clock to see a timeline of the history on a ticket.

Welcome to the third installment of Zendesk Voices, where we highlight the expertise of Zendesk customers and partners. This time, we want to hear how you measure customer experience. What metrics matter most to your team, and what targets guide your work?We’d love to hear about the metrics you track, why they matter, how you set goals, and how you use data to improve the experience.Share your story right here in our community, then visit the Spark reward hub for full details and to make sure you are eligible for rewardsOnce we review and approve your post, you will receive points.

When support teams work in Zendesk and engineering teams work in Jira, the integration between both platforms becomes critical to ensure the success of service delivery. A customer issue reported in Zendesk often needs an engineering investigation of Jira team. Status updates, priorities, comments, attachments, and resolution details need to move between both systems without the need for manual data entry.The native Zendesk–Jira integration is a useful starting point. It helps teams create Jira work items from Zendesk tickets, link existing Jira issues to support tickets, view Jira details inside Zendesk, and share updates between both platforms.For simple workflows, that may be enough.But as teams scale, support and engineering collaboration usually becomes more complex. Organizations start using custom fields, Problem and Incident tickets, advanced Jira workflows, multiple projects, different priority models, and stricter reporting requirements. That is where the native integration c

I am unable to select the Collect BSAT reply use case from the list….how can I set up an after call survey to gather insights on satisfaction?

Hoping the community can help.  When I was uploading our data, I chose to upload my contacts as “Deals” based on the Zendesk Documentation which explained that Leads are companies that you have not communicated with, and Deals are companies that you have communicated with before. Deals also suits me better, because I can use the pipeline to show where each company is in the sales process, % of winning etc.  However, I cannot use the “Log a Visit” button in a Deal contact. It is the most frustrating thing. Why would we suddenly NOT visit potential clients, once they move from “lead” to “deal”? One of the biggest selling points for Zendesk to our company was the ability to log visits. I am now facing one of two options - unless someone can enlighten me?  1. Bulk delete all my companies from “Deals” and re-import them as “Leads” - which means I will lose all my sales pipeline data. OR2. Inform my MD that having spent a huge amount of money on this Zendes

Hello WFM Magicians! Here's a list of Workforce Management (WFM) related resources that we've put together to help you understand the importance of WFM in customer service. We have categorized these so you can get started with WFM in your business, improve your existing WFM process and learn more from best practices.Feel free to bookmark anything you find useful here or suggest more useful links in the comments. We will continuously update this list.Be sure to hit the follow button to receive email notifications as shown in the screenshot below: Blog What is workforce management? What is a workforce manager? (+ How to become one) How to forecast in 4 simple ways 5 ways WFM for agents is great, explained by a former agent  Customer stories Ingram Content Group: how they're using WFM and AI to boost agent performance, efficiencies, and forecasting capabilities. Sendle: how they increased productivity with omnichannel CX and WFM tools Tembici: how they reached 30% cost s

 In many teams, support and sales are still handled in separate tools. Support agents work in Zendesk, while sales activity (tracking deals, follow-ups, or renewals) happens in a CRM.This separation often leads to missing context, extra tool switching, and slower communication between teams. Because of that, some teams try to bring basic sales activity closer to where support already happens inside Zendesk Support.Using a CRM and Deals app, it becomes possible to keep visibility on sales opportunities directly alongside support tickets. This helps when:A customer contacting support is also in an active deal process You need to track potential upsells or renewals during conversations Support agents should be aware of customer status without switching tools Sales and support teams need shared visibility on the same accountCRM and Deals App