Review ticket intent, sentiment, and urgency
Use descriptive labels to help staff understand a request without silently changing its priority.
- An open formal ticket and the required write visibility.
Step-by-step walkthrough
- 01
Open a formal ticket and choose Review triage. You need ticket write access and assignment or supervising access; closed or merged records cannot be reclassified.
- 02
Read the available messages and select Intent, Sentiment, and Suggested urgency. Choose Unknown when the evidence is insufficient rather than inventing certainty.
- 03
If a configured AI provider and your permissions allow it, Analyze ticket requests a suggestion. Inspect the cited customer messages and the qualitative confidence before using it.
- 04
Choose Use suggestion in review only if it helps, correct the values, then Save reviewed labels. Generating a suggestion or placing it in the form does not itself save a shared review.
- 05
When new messages arrive, revisit the labels. If the draft is stale, use Reload ticket triage and review the current version before saving again.
A closer look at the interface
These are actual product captures from a fictional demo workspace. Navigation and available controls can differ by role, configuration, or release.
Review ticket triage
- 1Analyze ticket is an explicit provider request.
- 2Inspect the referenced customer messages.
- 3Correct the labels and save a reviewed result separately.
Expected result
Staff-reviewed labels with a reviewer and an explicit saved result.
Important details
Saving reviewed labels does not itself change priority, assignment, SLA, or send a customer reply. Published automation rules can act on a review event separately.
Provider context uses a bounded set of public messages. Pattern redaction is best effort; follow your organization’s AI data-sharing policy.
Need help with this workflow? Contact the team and include this guide’s title.