About this block

Ticket Status Tracker is the customer side of a support ticket: a header card with the ticket ID, subject, an In progress Badge, and the opened time, then a vertical five stage timeline from Submitted through Resolved. Done stages get a filled check dot, the current stage a ringed dot, and upcoming stages stay muted, each with a timestamp and a one line note. Below it a latest update card shows the agent avatar, message, and an Add a reply button. A details rail lists status, priority, product area, assigned team, and the next update time.

Stages and detail rows are two typed const arrays; the connector line between dots darkens for completed stages so progress reads at a glance. The rail closes with a note that email covers every stage change, which is what keeps customers from refreshing the page.

When to use

Reach for this block on the customer portal ticket page, wired to your ticketing API by ticket ID. Map your internal statuses onto the five public stages and set the next update time from your SLA clock.

A natural flow around it on an Application Pro page:

Before

• Auth pages
• Notifications

After

• Ticket detail
• CSAT survey panel

What you can display

One strong use is the live support ticket status. Other tracker shapes:

• Order tracker. The same timeline for placed, packed, shipped, and delivered stages.
• Refund request status. Stages for received, reviewed, approved, and paid out.
• Data export progress. Queued, processing, and ready stages with a download link in the update card.

Tip: publish fewer, coarser stages than your internal pipeline has; customers want to know what happens next, not your team structure.