Feedback: Do not enable a feature thats going to break after 5 uses by design. | The place for Zendesk users to come together and share
Skip to main content
Feedback submitted

Feedback: Do not enable a feature thats going to break after 5 uses by design.

Related products:AI
  • February 18, 2026
  • 2 replies
  • 11 views

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)

 

This feedback concerns a recent announcement about the Copilot AI writing tools.

Introducing Copilot AI writing tools for Professional plans and above
 

I don't want this enabled by default. I don't want to enable a feature in my environment that's going to stop working after a limited number of uses. This should be DISABLED by default.

 

What problem do you see this solving? (1-2 sentences) 

I currently do not have the Copilot addon, so I do not have a way to pre-emptively disable or limit this feature to specific groups ahead of time. 

The announcement says to go to this article to find instructions, but the instructions can't be followed until the feature is already rolled out to my users. I'm guessing I'll have the option to disable this after the feature is enabled in my instance, but that's not really clear.

 

What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)

Don't enable features by default that will break after a limited number of uses.  From what I can tell, this is just Grammarly, but only for Zendesk. We already have Grammarly, which works across all applications. Why would I want this? 

 

I don't want something like this enabled by default, then break after x number of comments, and then have 240 support agents Slacking me about this error.

This message efficiently says “Slack Chris when you see this error”. 

2 replies

Shawna James
  • Community Manager
  • February 19, 2026
Hey Christopher! Thank you for taking the time to provide us with your feedback. This has been logged for our PM team to review. For others who may be interested in this feature request, please add your support by upvoting this post and/or adding your use case to the comments below. Thank you again!
 

I immediately disabled this capability when it appeared in our instance (I've been checking daily since the announcement). I find it ludicrous that this is enabled by default for all groups. Not just due to the usage/cost model (spamming agents to have their admins upgrade? ridiculous!). Our corporate policies require that our InfoSec team validate every AI tool before it is operationalized due to data privacy concerns. I do not ever want any of these AI capabilities enabled by default. I went through formal reviews before implementing Generative Search and AI Agents-Essential, and I have now initiated one for Copilot capabilities, and we won't even consider enabling this until I receive approval from InfoSec. I imagine that ours is not the only enterprise that requires that AI tools be vetted before use.