Home Configuring Simply Recommended Ticket Stages and Automatic Waiting-Time Tracking

Recommended Ticket Stages and Automatic Waiting-Time Tracking

Last updated on Mar 03, 2026

A clear ticket flow is the foundation of good support. We recommend starting with the standard stages below before customizing your setup. They are broadly usable and work well in most environments.

As an administrator, you can adjust or rename statuses to match your internal processes. However, we recommend working with the standard options for a period first to evaluate how they fit your setup. This helps maintain consistent reporting, automation, and team workflows.

Ticket Stages

Active

  1. New
    Ticket has been created. No agent has interacted yet.

  2. Open
    An agent has started working on the ticket or it is awaiting internal action.
    If internal, it should be reassigned to the correct user.

  3. Pending (Customer)
    Agent has replied and is waiting for customer response.

  4. On Hold
    Waiting on a third party or internal dependency.

Resolved

  1. Solved
    Issue resolved. Can still be reopened if the customer replies within a defined period (e.g. X days).

Final

  1. Closed
    Final state. Cannot be reopened.

Internal notes can always be used for internal communication without affecting the customer-facing status flow.

Automatic Waiting-Time Tracking

To make prioritization simple and transparent, we use two automatic fields on all HelpDesk tickets:

  • Hours Since Last Email (integer)

  • Last Email From (Customer / Support)

Both fields are updated automatically by a workflow approximately every 30 minutes.

Hours Since Last Email

This field shows how many hours have passed since the oldest unanswered customer email in the ticket.

It only counts situations where the customer has written after our last reply.

How it works

  • If a customer writes and no agent has replied, the counter increases.

  • If multiple customer emails are unanswered, we count from the first unanswered one.

  • When an agent replies, the counter resets to 0.

  • If the customer writes again after an agent reply, the counter starts from that new message.

Examples

  • Customer writes 100 hours ago → no reply →
    Hours Since Last Email = 100

  • Customer writes 100 hours ago and again 80 hours ago → no replies →
    Hours Since Last Email = 100

  • Customer writes 100 hours ago → agent replies →
    Customer writes again 80 hours ago → no reply →
    Hours Since Last Email = 80

  • Customer writes → agent replies →
    Hours Since Last Email = 0

This ensures you always know how long a customer has been waiting.

Last Email From

This field shows who sent the most recent email in the ticket:

  • Customer → Action required from support

  • Support → Waiting for customer

Together, these two fields give a quick and reliable overview of where action is needed and how long customers have been waiting.