Skip to main content
Nerve Centre KPIs · Audit Profile · Sentiment Settings Surfaces the daily ops questions a merchant or web agency lives with in Height: is the API key still good, is our backlog drowning, are people overloaded, and (most importantly) are the findings we filed actually getting resolved or quietly dying in the queue? Height’s AI auto-grouping and real-time triage clear faster than legacy trackers, so a stagnating queue is a stronger signal here than elsewhere.

​
What this audit checks

​
Authentication & access

  • API key still valid (auth on /workspace)
  • Outbound List(s) tagged for VortexIQ findings exist and are writable
  • vortexiq_finding_id custom-field template resolvable via /fieldTemplates
  • Height rate-limit headroom > 30%

​
Backlog health

  • Open task count vs 30-day baseline (sudden growth = drowning signal)
  • Blocked-task count + change WoW
  • Oldest open task age (>90 days = backlog rot)
  • Unassigned tasks > 5 (work that nobody owns)
  • Backlog-by-priority skew (mostly Lows = no one is grooming)

​
VortexIQ findings lifecycle (the stickiness test)

  • Abandoned findings - VortexIQ-created tasks, not completed, no activity >14d
  • Finding resolution rate over rolling 90d (target >75%)
  • Avg time-to-fix for completed findings, by severity
  • Findings cancelled without comment (silent dismissals)
  • Regression rate - findings that reopened after completion

​
Team capacity

  • Assignees with >10 open tasks (overload signal)
  • Assignees with zero completed tasks in 14d (parked work)
  • Cycle time degradation > 25% week-over-week
  • Cycle scope-creep (tasks added after Cycle start)

​
Cross-connector signals

  • Critical findings from sibling connectors (shopify/bigcommerce/adobe/cybersource) older than 7 days with no Height task - coverage gap
  • Height tasks referencing decommissioned/archived integrations - stale work

​
Severity thresholds

SignalWarnCritical
vortexiq_findings_abandoned515
vortexiq_finding_resolution_rate7550
blocked_tickets38
unassigned_tickets520
oldest_open_ticket_age_days6090
cycle_time_change_pct2550
rate_limit_headroom_pct3010

​
Data sources

  • GET https://api.height.app/workspace - API key + workspace info
  • GET https://api.height.app/lists - Outbound-list access + writability check
  • GET https://api.height.app/fieldTemplates - Resolve vortexiq_finding_id custom-field template id
  • GET https://api.height.app/tasks - Filter-driven backlog reads (open count, blocked, abandoned, by-assignee, etc.)
  • GET https://api.height.app/activities - Status-change history for cycle/lead time + abandonment detection
  • GET https://api.height.app/users - Assignee resolution + capacity calc