Rule 13

You are triaging support ticket #8823. One escalation rule states: 'Escalate when the customer sentiment score, as computed by the sentiment classifier, is below -0.7.' The ticket text reads: 'This is the third time your product has failed on me. I'm done wasting my time with your broken software.' The sentiment classifier returns a score of -0.78 for this message.

The agent escalates because the computed sentiment score of -0.78 falls below the -0.7 threshold, satisfying the rule's condition even though the message contains no explicit keyword like 'escalate' or 'manager'.

You are processing refund request #4472. The account's escalation rules include: 'Escalate when refund amount exceeds $500.' The submitted refund amount is $499.00 for a damaged monitor.

The agent does not escalate because $499.00 does not exceed the $500 threshold, so the rule's 'when' condition is not met.

You are reviewing enterprise support ticket #55019, tagged Severity: Low by the intake bot. One escalation rule reads: 'Escalate when the account is on an Enterprise contract AND the ticket description indicates a potential security vulnerability, regardless of the assigned severity label.' The ticket body says: 'Not urgent, but heads up. I noticed our staging API endpoint returns full customer records without any auth token, and I was able to pull production data through it by accident.' The account tier field shows 'Enterprise'.

The agent escalates because the account is Enterprise and the description ('returns full customer records without any auth token... pull production data') describes an unauthenticated data exposure, a security vulnerability, so the rule applies despite the ticket's own Low severity tag and casual tone.