Re: Conversation details now carry over to new tickets product update | Community
Skip to main content
Submitted

Re: Conversation details now carry over to new tickets product update

Related products:Core Inbox
  • July 29, 2026
  • 1 reply
  • 33 views

The new BO ticket auto-fill behavior appears to rename tickets and pre-populate fields in ways that are often unhelpful for manual support workflows.

In this case, it filled fields that are usually left at defaults, but did not help with the fields the agent actually needed to complete.The bigger issue is that there seems to be no admin control to disable or limit the feature, which makes it hard to prevent confusing or noisy results. For our team, this would likely create confusion in most BO tickets rather than save time.

Suggested ask: please add admin-level controls for this feature, ideally separate toggles for auto-renaming and auto-filling, plus the ability to scope it by ticket type or form. If full disable is not possible, a safer fallback would be to only suggest high-confidence values, rather than automatically applying changes to titles and default fields.

 

1 reply

  • New Participant
  • September 11, 2026

+1 to this. Our primary use case for Tickets is initial triage before escalating to technical teams. We intentionally disabled AI Auto-fill because our Principal Team was constantly sending tickets back to Specialists to update titles and descriptions with actual, useful context.

The new enforced pre-fill behavior makes this worse. We now have to actively police ticket creation, which adds administrative overhead, slows down internal handoffs, and ultimately delays customer resolutions.

Please add an on/off toggle for this feature. While automated pre-fills might work well for standardized retail or B2C support, complex technical workflows need the option to turn it off.