What are the standard ticket statuses in ecommerce support?

Most help desk platforms use Open (needs action), Pending (waiting on external input), Resolved or Closed (issue addressed), and Reopened (customer followed up after resolution). Some add On Hold or Escalated for additional nuance in complex workflows.

Should I close a ticket or mark it pending when waiting for a customer reply?

Pending is the right status when you\'re waiting for the customer to confirm resolution or provide additional information. Closing too early triggers a reopened status if they reply, which inflates your reopened-ticket rate and can obscure real quality issues.

How long should a ticket stay open before being resolved?

Target same-day resolution for straightforward requests and 24–48 hours for complex ones requiring investigation. Tickets open longer than 72 hours without a pending justification typically indicate they\'ve been overlooked and should trigger an automatic escalation alert.

Glossary

Ticket Status

Ticket status is the lifecycle stage assigned to a customer support request at any given moment — typically categorized as open (unresolved, requiring action), pending (awaiting customer response or external action), resolved (issue addressed), or reopened (a resolved ticket reactivated by follow-up contact).

Book a demo See pricing

What it means

Key insight

Ticket status is the backbone of support accountability — without it, there is no reliable way to know what needs attention and what is done.

Ticket status provides the operational structure for managing support at scale. Every inbound contact is assigned a status that reflects its current state: an open ticket requires agent or AI action; a pending ticket is waiting for something outside the team\'s control (a carrier update, a customer reply, a warehouse confirmation); a resolved ticket has been closed; and a reopened ticket was resolved but subsequently reactivated by a follow-up from the customer. Status transitions drive the support workflow: SLA timers typically pause on pending tickets and resume on open ones; resolved tickets exit the active queue; reopened tickets re-enter with context from the previous resolution. For ecommerce support teams, clear status discipline is what prevents tickets from getting lost in the queue and ensures that every customer who reached out receives a timely resolution.

Why it matters

Ticket status accuracy directly affects two critical metrics: response time SLA compliance (which depends on accurately knowing which tickets are still open) and queue clarity (which depends on resolved tickets actually being marked resolved). Status inflation — keeping tickets open longer than necessary — wastes agent attention on already-resolved issues. Status deflation — marking tickets resolved before they truly are — generates reopened tickets and frustrated customers. AI-assisted support improves status accuracy by automating resolution confirmation and systematically tracking whether a customer has acknowledged their issue as resolved.

How Bookbag helps

Automated Status Transitions

Bookbag automatically updates ticket status based on conversation events — moving to resolved when the AI confirms issue resolution, to pending when awaiting carrier updates, and triggering reopened status when a customer follows up on a closed ticket.

Status-Based SLA Tracking

Bookbag\'s SLA timers pause on pending tickets and fire alerts when open tickets approach breach thresholds, keeping your team focused on what genuinely needs action.

Resolution Confirmation

Bookbag prompts customers to confirm resolution before closing tickets, reducing the rate of tickets incorrectly marked resolved that will reopen when the customer follows up.

Frequently Asked Questions

See Bookbag in action

Join the ecommerce teams resolving more tickets, answering 24/7, and turning support into a revenue channel with Bookbag.