Generally, we prioritize tickets as explained here. In some cases that method fails so we have the following fallback options:
Tickets opened through the app
The tickets will contain the expected priority (at the time when the ticket has been created) as a Client side priority field. We'll manually upgrade them by going through this view. The view shows tickets where the priority field doesn't match the client side priority field.
Tickets opened before upgrading to the paid tier will be stuck at the old priority level
Community questions opened on the forum
These questions will only be prioritized based on the email
Emailing our support email directly
Same thing as in the 2. case.
For 1.ii:
Since it's not possible to manually specify the organization of a ticket, I'll put up a PR that will send the organization ID as a ticket field value to Zendesk. I'll need to check with the Growth team if we can get a webhook to Zapier if an organization upgrades to a paid tier, to upgrade all existing tickets as well.
For 3.i We should automatically close all tickets that have been created directly through email and respond with something like Please open a ticket through the app instead
Cases:
Generally, we prioritize tickets as explained here. In some cases that method fails so we have the following fallback options:
Client side priority
field. We'll manually upgrade them by going through this view. The view shows tickets where thepriority
field doesn't match theclient side priority
field.For 1.ii: Since it's not possible to manually specify the organization of a ticket, I'll put up a PR that will send the organization ID as a ticket field value to Zendesk. I'll need to check with the Growth team if we can get a webhook to Zapier if an organization upgrades to a paid tier, to upgrade all existing tickets as well.
For 3.i We should automatically close all tickets that have been created directly through email and respond with something like
Please open a ticket through the app instead