Customer support
Waiting on customer workflow for ball-in-court tickets
Learn how to manage ball-in-court support tickets with a Waiting on customer filter, clear ownership, and a 15-minute weekly follow-up ritual.
Half your open tickets are not waiting on you. They are waiting on the customer: a screenshot you asked for, a billing approval, a "try this and tell me if it worked" step.
Those threads are not done. They are also not active work in the same way as a new urgent message or an engineering blocker. When they sit in the main inbox, they inflate your mental backlog, distort first-response metrics, and make triage feel heavier than it is.
Ball-in-court is the shorthand: who must act next for the ticket to move. When the court is the customer's, your job shifts from drafting replies to managing follow-up, without letting threads go cold or reopening them by accident.
What "waiting on customer" actually means
A ticket is waiting on the customer when the next substantive step requires their input before you can investigate, fix, or close.
Common examples:
| Situation | Why it is ball-in-court |
|---|---|
| You sent repro steps | They need to run them and report back |
| You asked for an invoice PDF | You cannot verify billing without it |
| You offered two workaround options | They must pick one |
| You requested access or a test account | Engineering is blocked until they send it |
| You sent a draft contract change | Legal or procurement on their side |
It is not waiting on the customer when:
- You owe them an update and have not sent one.
- Engineering is investigating and you have not told them.
- You are hoping they forget (that is avoidance, not workflow).
Be honest about ownership before you move a ticket out of active triage. Mislabeling "waiting on customer" when you are actually stalling trains customers to chase you harder.
When to move a ticket to Waiting on customer
Move a thread when you have:
- Sent a clear ask, one action, one deadline if appropriate.
- Set status so the team knows it is parked (see tags below).
- Recorded context in an internal note if the handoff spans people or days.
Keep it in the main inbox when:
- The customer just replied and you have not read it yet.
- Your ask was vague and you expect confusion.
- The thread is emotionally heated and needs a human check-in soon.
A useful rule for small teams: if you would be surprised to see the ticket still open in five business days, it belongs in a follow-up queue, not mixed with net-new work.
Use a Waiting on customer filter as your follow-up queue
initdesk includes a predefined Waiting on customer filter so ball-in-court tickets have a home outside your active-work views. It shows conversations waiting on a customer reply, with a count so the queue stays visible without pretending those threads need the same attention as new messages.
The filter is organization-shared by default. Admins and owners can rename, reorder, edit, or delete it, so use the name your team recognizes while preserving its “waiting on the customer” criteria.
See predefined inbox filters for small teams for the current workflow and the custom preset filters product update for what shipped. The older Waiting Customer tab update remains useful product history, but that fixed tab has been replaced by customizable filters.
Why a separate view helps:
- Triage stays honest: your "open work" list reflects tickets that need your next move.
- Follow-ups do not disappear: parked threads have a named place instead of sinking in a sort order.
- Nudges become a habit: you review one queue on a schedule instead of re-scanning the entire inbox.
Pair the filter with tags your team already uses. Tags like
waiting-on-customer make handoffs readable; the filter makes the queue scannable. First response norms for small teams covers tag habits in more detail.A weekly nudge ritual (fifteen minutes)
Ball-in-court tickets fail in two ways: no follow-up (customer forgets, issue festers) or too much follow-up (five pings in three days). A short weekly pass fixes both.
Once per week, open your Waiting on customer filter and walk the list:
| Step | What to do |
|---|---|
| 1. Sort by age | Oldest waiting threads first |
| 2. Check the last outbound message | Was the ask clear? Did they partially reply? |
| 3. Decide: nudge, resolve, or escalate | One action per ticket |
| 4. Log it | Internal note if ownership changes |
Nudge when the thread is still live and your ask still stands. One polite reminder with the original ask restated beats three vague "just checking in" messages.
Resolve when the customer never replied and the issue is low impact, or when your policy says unanswered threads close after N days. Say so in the closing reply when you have a contact: "We have not heard back, so we are closing this for now. Reply anytime to reopen."
Escalate back to active when they replied, when the deadline passed and the issue is urgent, or when you realize the ball was never really theirs.
Fifteen minutes is enough for most SMB queues under a few dozen waiting tickets. If the filter count grows every week without resolution, the problem is usually unclear asks, not lack of reminders.
Draft nudges without rewriting the same paragraph
Nudge emails are repetitive by nature. You are restating context the customer already has. That is a good fit for AI drafts with a short instruction line, see Steer AI drafts with a few words.
Example instructions:
friendly nudge, restate we need the screenshot from Tuesday's messageclose politely, no reply in 10 days, invite them to reopenconfirm they tried step 2, offer call if still stuck
For policy-heavy closings or exact legal wording, use a saved reply instead, When to use saved replies instead of AI drafts walks through when locked text beats paraphrase.
Keep ownership visible on handoffs
Waiting-on-customer queues break when nobody owns follow-up. The assignee who sent the ask should stay assignee until the ticket resolves or explicitly hands off.
When you pass a parked thread to a teammate, use the handoff pattern in Hand off a support thread without losing the customer: assignee, internal note with what you asked and when, tags for urgency.
If product work is linked in Linear, the ticket can wait on the customer while engineering ships a fix, but the customer still deserves a dated update. Waiting on them does not mean waiting in silence.
What to avoid
Do not mark resolved while you still need something. Closing to shrink the queue creates reopen surprises and erodes trust.
Do not leave ball-in-court tickets unassigned. Unassigned parked threads are how "we thought someone was following up" happens.
Do not nudge without re-reading the thread. Customers often reply in ways that do not match subject lines, partial answers, attachments on a different message, replies from another email address.
Do not treat Waiting on customer as archive. It is an active follow-up queue. If a ticket has been waiting ninety days with no policy, close or escalate it deliberately rather than letting it sit as inventory.
A Monday-morning checklist
Before you dive into new tickets:
- Glance at the Waiting on customer count, did it jump since Friday?
- Run the weekly nudge pass if it is your scheduled day.
- Confirm every waiting ticket has an assignee and a tag that matches reality.
- Pick one stale thread to resolve or escalate, compounding small clears beats heroic inbox zero.
initdesk is an AI help desk for small teams: shared inbox, customizable ticket filters, AI-drafted replies, tags, internal notes, and Help Center deflection when customers can self-serve. Browse the blog for more SMB support patterns, or Product Updates for recent releases. Questions welcome on X @initdeskhq.