Choose the right ticket priority

Match priority to the situation

Low suits a non-urgent question or improvement with no active business impact. Normal suits routine support and planned changes. High is appropriate when important work is blocked or significantly degraded. Urgent is for a serious active interruption or a security concern that needs prompt human attention. Priority helps the team organize work. Actual response commitments are defined in your service agreement; selecting a priority does not create a new guaranteed response time.

Explain the impact clearly

1. Identify the affected service and business process.
2. State whether one person, a team, or all customers are affected.
3. Explain what cannot be completed.
4. Note any workable temporary alternative.
5. Include the start time and a real deadline if relevant.

“Checkout is failing for every customer” gives more useful context than “Very urgent.” If the scope is unknown, say what you have observed rather than guessing.

Update the same ticket

Reply when the impact changes, a workaround fails, or the service recovers. Explain the change and ask the team to reassess priority if necessary. Opening several copies of the same issue splits the evidence across conversations.

For an active incident

Follow any additional escalation channel agreed for your organization. Do not wait for an automated article response to confirm a suspected security incident or serious outage. Keep the original ticket as the record of observations and follow-up.