How to Run a Support Ops Weekly Standup
A weekly standup keeps your support team aligned without drowning in meetings. Done right, it’s 15–30 minutes that surfaces the most important issues and sets priorities for the week.
Why a standup, not a full meeting
Full meetings invite tangents. Standups are constrained by design:
- Short — 15–30 minutes max.
- Structured — Same agenda every week.
- Action-oriented — Focus on what changed, what’s blocked, and what’s next.
For a deeper dive on the weekly review, see weekly support ops review.
Who attends
Keep it small:
- Support lead or manager
- Team leads (if you have them)
- Optional: product rep for escalation patterns
If your team is under 5 people, the whole team can attend. Above that, consider a leads-only standup with async summaries.
The agenda (20-minute version)
1. Metrics check (5 min)
Pull up your scorecard or dashboard. Ask:
- What changed vs last week?
- Any metrics in the red?
Don’t explain every number—just highlight changes.
2. Blockers (5 min)
Go around. Each person answers:
- “What’s blocking you this week?”
- “What do you need from someone else?”
Keep it crisp. If a blocker needs discussion, note it and handle afterward.
3. Top issues (5 min)
Review the top tags or categories from the week. Ask:
- Any new patterns?
- Anything that needs escalation to product?
4. Action items (5 min)
- What are we doing differently this week?
- Who owns what?
Write it down. Follow up next week.
Example standup script
Lead: “Let’s look at the scorecard. FRT was 3.2 hours, down from 4 last week—nice. Reopen rate is at 7%, above our 5% target. We’ll dig into that.”
Lead: “Blockers?”
Agent 1: “Waiting on the billing fix from eng. Tickets are piling up.”
Agent 2: “Nothing from me.”
Lead: “I’ll follow up on the billing thing today.”
Lead: “Top tags: ‘checkout-error’ is up 40%. Looks like a product issue. I’ll flag it.”
Lead: “Actions: I’ll chase billing fix; we’ll review checkout-error tickets for root cause. Anything else? No? Great, see you next week.”
Done in 15 minutes.
What to avoid
- Going over time — If you routinely exceed 30 minutes, you’re doing a meeting, not a standup.
- Rehashing every ticket — The standup is for patterns and blockers, not ticket-by-ticket review.
- No metrics — Without a scorecard, the standup is just vibes.
- No action items — A standup that doesn’t produce actions is a waste of time.
Async alternatives
For distributed teams or async cultures:
- Post the scorecard in Slack on Monday.
- Each person replies with blockers by EOD.
- Lead summarizes priorities in a thread.
Works for teams that don’t need real-time discussion.
Making it a habit
- Same time every week — Monday morning or Tuesday after weekend tickets clear.
- Same agenda — Consistency reduces prep.
- Rotate facilitator — Keeps people engaged and builds ownership.
FAQ
Should agents attend or just leads?
Depends on team size. Under 5, include everyone. Above that, leads-only plus async summary.
What if there’s nothing to discuss?
Great! End early. Don’t fill time for the sake of it.
How do I share the scorecard?
Use a dashboard tool (Explore, TicketBoard, Metabase) on screen, or send a screenshot/PDF before the standup.