Route customer support tickets into five queues

Paylark (fictional) is an Indian payments and expense app for small businesses. Support receives about 9,000 tickets a day by email and in-app chat, in English, Hindi and Hinglish. A small, fast model will route each ticket to a queue. Your system prompt is the only thing you control.

The five queues:

• account_access: cannot log in, OTP not received, password reset, account locked.
• billing: charges, refunds, double debits, invoices, GST invoices, subscription payment failures.
• bug: a product feature is broken or showing wrong data (not login problems).
• cancellation: the customer explicitly asks to cancel the subscription or close the account.
• other: anything else, including feature requests, praise and sales questions.

Priority when a ticket mentions more than one issue:

1. If the customer explicitly asks to cancel or close, use cancellation.
2. Otherwise, if they cannot log in, use account_access.
3. Otherwise, if there is any billing issue, use billing.
4. Otherwise bug or other.

Your prompt will be run against hidden tickets, including mixed-language and adversarial ones. Output is compared exactly.