Ticket Lifecycle

Modified on Thu, 20 Aug at 1:13 PM


Ticket statuses help communicate where a request/issue is in its lifecycle and what action is required next. Updating ticket statuses correctly improves visibility, reporting and workload management across services.


Open

Use Open when the ticket requires action from an agent or administrator.

New tickets are created with an Open status by default. A ticket will also return to Open if the requester responds after the ticket has previously been updated or resolved.


Examples

  • New request received.
  • Further investigation is required.
  • Customer has responded with additional information.

Pending

Use Pending when work is currently on hold while additional information, actions or investigation is undertaken by the assigned agent.

This status is typically used when the ticket remains actively owned by the team but cannot progress immediately.


Examples

  • Investigating an issue.
  • Reviewing information before responding.
  • Awaiting internal action before contacting the requester.


Waiting for Customer

Use Waiting for Customer when a response or additional information is required from the requester before the ticket can progress.


Examples

  • Further details have been requested.
  • Screenshots or supporting information are required.
  • Confirmation from the requester is needed.

Waiting for Internal Third Party

Use Waiting for Internal Third Party when assistance or action is required from another internal team, business area or stakeholder.


Examples

  • Approval is required from another team.
  • A subject matter expert is reviewing the request.
  • Action is required by an internal business unit.


Waiting for External Third Party

Use Waiting for External Third Party when assistance or action is required from an external vendor, supplier or service provider.


Examples

  • Awaiting response from a vendor.
  • Logging an issue with a third-party supplier.
  • Waiting for external technical assistance.


Resolved

Use Resolved when a solution has been provided and no further action is currently required from the support team.

A resolved ticket may be reopened if the requester responds with additional questions or information.


Examples

  • Issue fixed.
  • Information provided.
  • Request completed.


Closed

se Closed when the ticket has reached the end of its lifecycle and no further action is required.

Closed tickets remain available for reporting, auditing and historical reference.


Examples

  • Request completed and confirmed.
  • Issue resolved with no further response required.
  • Ticket automatically closed following the resolution period.


Status Selection Tips

  • Keep ticket statuses up to date.
  • Avoid leaving tickets in Open if no immediate action is required.
  • Use Waiting statuses to clearly identify who is responsible for the next action.
  • Select Resolved only when a solution has been provided.
  • Ensure ticket statuses accurately reflect the current stage of the request


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article