Rank support load by account

Combine errors, complaints, affected users, and plan data to show which accounts are consuming the most support attention.

Published

difficulty intermediate · time to value 5 minutes
#analytics #errors #customer-support #account-health #b2b #revenue

Start from this 

Rank accounts by support load for the last 30 days using errors, affected users, complaint events, and plan or revenue tier.

Why this matters

Support load is not evenly distributed. One account can dominate support because of one unresolved bug, bad onboarding, or a product mismatch.

What you get

  • Accounts ranked by tickets, errors, and affected users
  • Top topics or fingerprints per account
  • Revenue-aware prioritization
  • Follow-up action for CS or engineering

Walk through it

You

Which accounts are generating the most support load?

Agent

I’ll join support events and error impact by account.

Endpoint: POST /v1/projects/:project_id/analytics/query
Exact shape: /v1/openapi.json?path=%2Fv1%2Fprojects%2F%7Bproject_id%7D%2Fanalytics%2Fquery&method=post
Custom HogQL goes in the OpenAPI-defined `query` field.
Concept fields:
  query: "SELECT properties.account_id AS account, countIf(event = 'support_ticket_opened') AS tickets, countIf(event = '$exception') AS errors, count(DISTINCT distinct_id) AS affected_users FROM events WHERE timestamp > now() - INTERVAL 30 DAY GROUP BY account ORDER BY tickets DESC, errors DESC LIMIT 30"

The output

The agent returns accounts by support load and explains whether the likely fix is product, engineering, documentation, or CS.

Setting it up

Send support-ticket events from your help desk webhook or backend. Use the same account_id as analytics and errors.

Variations

  • “Only show enterprise accounts.”
  • “Which support topics correlate with churn?”
  • “Create a weekly support-load dashboard.”

Related playbooks

ops 10 minutes

Review composite account health

Score every B2B account on usage, revenue, and support load. Return the at-risk accounts and the missing signals before deciding whether a shared URL is useful.

debugging 30 seconds

Diagnose a customer complaint in 30 seconds

Paste a customer message. The agent pulls their session, finds the error they hit, walks their funnel, and tells you what to reply.

debugging 2 minutes

Rank errors by revenue impact, not raw count

Multiply users-affected by their plan ARR to surface the bugs costing real money. Stop triaging by event volume.

Adapt this playbook in your own agent.

Ask your agent to map the starter prompt to your saved signal map, live events, and the current HTTP API before answering.

Set up Agentry in this repo by following https://agentry.sh/install.md. I authorize you to: run its device-code login and save the key to ~/.agentry/credentials.json, read this repo, propose an instrumentation plan for my approval, and edit code after I approve it.

+ Full access
5.5 Extra High
  1. 1. Open your repo in Codex, Claude Code, Cursor etc.
  2. 2. Paste the install prompt.
  3. 3. Your agent reads the install doc and shows you an implementation plan for approval.
← all playbooks