Discuss ideas, submit feedback, and track what's next
Feature requestToday, the source of an auto assist suggestion is only shown to agents who have permission to view that specific procedure. In practice, this means only Knowledge admins can see which procedure was used. Agents without Knowledge admin access only see the rationale and a generic “Learn more about other sources” link.Our use caseWe have several published auto assist procedures for our Support team. Our team leaders review auto assist suggestions daily and help us identify inconsistencies so our Knowledge team can improve the procedures.When a leader sees a suggestion, they can read the rationale (for example, “The procedure states that...”), but they can’t see which procedure was used. To find out, they have to escalate to an admin, who reproduces the scenario. We confirmed with Zendesk Support that this is expected behavior and that there’s currently no separate permission for this.The only way to give them visibility today is to enable “Manage knowledge” on their role. That grants full Knowledge admin access, including editing and publishing articles and procedures, which is much more than they need.What we’d likeA view-only permission (for example, “View procedure sources in auto assist”) that lets agents in custom roles:see the title of the procedure used in a suggestion; open the procedure in read-only mode;without being able to create, edit, publish or delete knowledge content.Why it mattersLeaders and senior agents can give precise feedback on procedures, which improves auto assist quality over time. Admins don’t need to reproduce tickets just to identify the source. It keeps the principle of least privilege, since we wouldn’t have to grant admin access only for visibility.
We would like more control over when intent is applied to tickets, beyond channel and whether the ticket was created by an agent. Please allow intent to be restricted based on additional conditions, such as: Brand (e.g. only apply intent for specific brands) Potentially other ticket attributes (ticket group, ticket form, etc.) ReasonSome tickets are created as receipt/confirmation tickets, where intent is not needed.When these tickets are created, a large number of triggers run, and the intent update can interfere with other updates happening at the same time. More granular control would prevent conflicts on these tickets and would be much appreciated.
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)We request adding "Seconds" as a time unit option to the Wait block in Zendesk Bot Builder alongside minutes, hours, and days. This directly impacts our bot admins who design automated conversation flows, as well as our end users who expect timely responses in chat. Currently, administrators cannot build brief pauses into custom action flows to accommodate short backend processing times.What problem do you see this solving? (1-2 sentences)It bridges the gap between instantaneous actions and long pauses by allowing the bot to wait briefly for an asynchronous worker to return data. This prevents premature fallback errors and eliminates unnatural 60-second delays in live chat conversations.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 encountered this issue this week while deploying an automated custom action connected to an external worker that takes roughly 3 to 5 seconds to process user data. Because the minimum available wait duration is one minute, users either faced an unacceptably long silence or the bot moved to the next step before the data was ready, triggering failure messages. This impacts every customer who uses this automated flow across hundreds of conversations per day. The resulting drop in deflection rates frustrates customers and causes unnecessary ticket escalations to human agents.Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)Yes, we currently force a minimum 1-minute wait or rely on synchronous API calls that frequently risk timeouts. Both options result in high user drop-off and a degraded messaging experience.What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)The ideal solution is adding "Seconds" to the duration unit dropdown in the Wait step, supporting values from 1 to 59. The bot would pause execution for the designated number of seconds before executing the subsequent action or polling step.
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)The embedded templates supported by the Advanced AI do not currently support automatic translations, compared to the Essentials bot builder. I would like to suggest for this feature to be added for embedded templates. What problem do you see this solving? (1-2 sentences)Withe the Essentials bot builder we only had to create the flow in English and could rely on the automatic translations for all the languages we support in. We have two brands, one supporting in 16 languages and another one supporting in 39 languages. While I understand that some industries may wish to use manual translations due to sensitive terms being used, I find that removing completely the automatic translations from this feature is impacting a lot of customers who could actually benefit from this in the embedded templates.We could make a lot of use of these embedded templates, but are currently limiting our workflows to use as few as possible because manual translations are time consuming especially in our case. Not to mention that whenever we make a small change in the default English template this has to be manually changed for each language individually. 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)The embedded templates have been released without automatic translation and impacted us as soon as we started migrating to Advanced AI as our planning did not take into account time needed and costs for manual translations. Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)As a workaround, we are trying to avoid using templates and have only created them if absolutely necessary. What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)Ideally, the templates should support automatic translations with the possibility to add manual ones for customers who might require precise translations for more sensitive areas as health or IT services.This would allow all customers to benefit from using templates in the best way suitable for their business.
Hi,We’re using Intent detection, and one limitation we keep running into is that intent seems to be based only on what the requester writes.In many cases the real intent becomes clear after the agent has asked follow-up questions, or when the agent summarizes the issue in their reply.It would be really useful if intent could be generated based on: the full ticket conversation, and/or the agent’s messages (agent-side intent) This would improve both routing and reporting, especially for more complex tickets where the first customer message is vague.
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)We need a way to exclude specific users from the AI agent (Advanced) on a given channel, based on criteria such as user tags, user segments, organization or custom user fields. For example, on WhatsApp we want customers with a specific tag to skip the AI agent entirely and go straight to a human agent. This affects our admins, our agents, and the customers who should never be handled by the bot. What problem do you see this solving? (1-2 sentences)As an intermediary between customers and ticket and activity providers, some of the people contacting us need a human from the first message, and an automated conversation creates friction for them. Being able to filter who the AI agent responds to would let us keep the bot for the general public while protecting these specific relationships. 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 happens every time one of these tagged users contacts us through WhatsApp, because the AI agent activates for everyone on the channel with no way to filter. They have to go through the bot before reaching an agent, which delays resolution and gives a poor experience to contacts we want to treat with priority. Since we can’t segment the AI agent, we are forced to choose between deploying it on the whole channel or not using it there at all. Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)No, we haven’t found a reliable workaround, since the AI agent’s activation can’t be conditioned on user data. What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)An audience or eligibility setting per AI agent and per channel, where admins can include or exclude users based on tags, user segments, organizations or custom fields. Excluded users would bypass the AI agent and be routed directly to a human agent.
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)We would like to user an AI agent (Advanced) to reply to customer reviews that arrive through the Trustpilot channel integration, and every reply it publishes ends with a fixed footer: “This email was automatically generated using AI.” There is no setting at account, agent or channel level to remove or customize it, and “Display sources for generative replies” is disabled. This affects our admins, who can’t control the content of public replies, and our customers and prospective customers, who read these replies on Trustpilot. What problem do you see this solving? (1-2 sentences)It would let us publish AI-generated review replies with wording that is accurate for the channel and consistent with our brand. Today the footer refers to an “email” on a public review platform and stays in English regardless of the reply’s language. 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 happens on every single reply the AI agent publishes on Trustpilot, so we are affected daily. Each reply appears publicly with a footer that calls it an email, which looks like an error to anyone reading our reviews. Since review replies are one of the most visible parts of our brand to potential customers, this undermines the quality of our public communication. It also makes it hard to justify using AI agents on public-facing channels at all. Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)No, we haven’t found any workaround, since the footer isn’t part of our instructions or procedures and can’t be edited. Our only alternative would be to stop using the AI agent on this channel. What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)An option to enable, disable or customize the AI footer per AI agent and per channel, with support for localized text. We’re happy to disclose AI use; we just need to control the wording and where it appears.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.