Ticket triage: is it urgent?
For support queues that must show the tickets that cannot wait first. The judgment reads the ticket’s subject and first message, and the customer’s plan if you have one. When the conversation is an array, it also reads the latest three messages. It does not read the status, the assignee or the tags, so a change to them costs nothing. Sort or get alerts onp or on the urgent threshold.
from_starter: ticket_triage.urgency
Ticket triage: which team should take it?
For routing tickets to a team. The judgment reads the same parts of a ticket as the urgency starter, so Brussle answers the two together. It picks billing, technical, account or sales, or none_of_the_above when none fits. To use your own teams, change the options in the definition that the dry run returns. Usevalue as the answer. Until you post outcomes, the probabilities of a choice are too confident.
from_starter: ticket_triage.routing
Moderation: does this post break a rule?
For posts, comments and reviews that users write. The judgment reads the post’s text and title. The criteria list common community rules. To use your own rules, change the criteria in the definition that the dry run returns. A change to likes, views or replies costs nothing. Hide a post above thehide threshold. Send a post between review and hide to a person.
To also show the post that a post replies to, add a relation. See the referenced document guide.
from_starter: moderation.breaks_rule
Review queue: does a person need to look at this?
For a flow where your system handles most items and a person must look at some. Examples are refund requests, automated replies, applications and claims. The judgment reads the item’s content, and its summary and category if you have them. Send the items above thereview threshold to your queue. To review more items, make the threshold lower.
from_starter: review_queue.needs_review