Skip to main content
Metrics type: Key Metrics • Category: Project Management
Findings sat in the backlog with no status change for two weeks, these are the ones losing money silently.

​
At a glance

Live count of Vortex IQ findings sitting in your HelpScout shared inbox with no status, thread, or assignee change for 14 days or more. The merchant question this answers is: “how many revenue-leak fixes have I forgotten about?” This is the silent drain gauge. HelpScout’s customer-centric culture often means engineering-flavoured findings get lower priority than consumer queries; this card surfaces the cost.

​
Calculation

Calculated automatically from your Help Scout data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

The same US wellness DTC brand from the parent card. Snapshot taken on 02 May 26 at 11:15 ET. Of the 16 open Vortex IQ findings, 5 have not seen any thread update for 14 days or more. The card reads 5. Threshold says warn at 5, critical at 15, so the panel just tipped amber. Three observations:
  1. **Composite weekly leak ≈ 2,200.∗∗Threeoffivefindingstranslatetoweeklyrevenueloss;twoareoperational/NPS.2,200.** Three of five findings translate to weekly revenue loss; two are operational/NPS. 2.2k/week is roughly $9k/month, well above the cost of an additional triage hour per week.
  2. The subscription portal SSO loop is the highest revenue-impact finding. For a wellness DTC brand, subscription churn is the lifeblood metric. An SSO loop that prevents subscribers from managing their accounts is a direct churn driver. Pair with shopify.subscription_churn_rate. If churn is up 0.5 points since the bug landed, the cost is materially higher than the $1,200/week estimate.
  3. The wholesale finding has been abandoned for 24 days but has a day-1 internal note. This is the exact “looked at, never resolved” pattern HelpScout’s UX is most prone to: shared-inbox model means anyone can comment, no-one owns. Apply a HelpScout Workflow that auto-assigns wholesale@ Vortex IQ tags to the wholesale account manager.
  4. The free-shipping threshold widget tipped into Abandoned exactly today. Last touched on day 2 (status change), then nothing. Day 14 cutoff. Cheapest action: a one-line internal note resets the clock and removes it from this list.
  5. Pair this card with shopify.refund_rate and shopify.customer_service_sentiment. “Abandoned: 5, refund rate up 0.3 points, NPS down 3 points” is the board-level cost narrative for a HelpScout-using DTC brand whose entire CS philosophy is built on customer-centricity.

​
Sibling cards merchants should reference together

​
Reconciling against the vendor’s own dashboard

Where to look in HelpScout’s own dashboard:
Inbox view (secure.helpscout.net/conversations) with filters: Tag = vortex-iq, Status = Active OR Pending, sort by Last Modified Ascending. The top of the list is your abandoned tickets. Saved Searches to share that view across the team. Reports → Conversations → Time-to-Resolve to see the long tail of resolution times for vortex-iq-tagged conversations.
Why our number may legitimately differ: Cross-connector reconciliation:

​
Known limitations / merchant FAQs

Why does HelpScout Reports show a different number? Three reasons:
  1. Field choice. Reports’ “Time-to-Resolve” uses closedAt, not userUpdatedAt. We use userUpdatedAt because abandoned-but-still-open is the population that matters.
  2. Time zone. The 14-day cutoff is UTC for the card; Reports honour company timezone.
  3. API filter limitation. The card filters in-memory after a modifiedSince query, which can briefly disagree with the UI on accounts with very large open backlogs.
A finding has two internal notes but no status change. Is it abandoned? No. Internal notes are threads in HelpScout, and threads update userUpdatedAt. The 14-day clock resets on any thread. Should Beacon auto-replies count as movement? Yes by default. If you’d rather discount bot-only updates (the bot is keeping the clock alive on tickets nobody is actually triaging), set vortex_iq.exclude_bot_updates: true in the connector config. Why is the threshold 14 days, not 7 or 30? Empirical. Across 200+ merchants, the probability that an open finding closes drops sharply after day 14 and approaches zero after day 21. My team uses a custom “Won’t Fix” tag instead of closing tickets. Do they count? Yes, until status moves to Closed. Tags don’t change status. Build a Workflow that closes a conversation when the wont-fix tag is applied. The count went from 5 to 0 overnight, what happened? Most likely a Workflow ran a bulk action (e.g. “add internal note to all vortex-iq conversations”) which updated userUpdatedAt and reset all clocks. Healthy if deliberate; suspicious if findings re-enter Abandoned 14 days later. Open count jumped, what should I check first? Same playbook as the parent VortexIQ Findings Open card with one addition: if Abandoned jumped without Open jumping, you have a triage stoppage, not a finding influx. Check Top Assignees Overloaded. Response time vs resolution time, which one is this card about? Resolution-time-extreme. The long tail of resolution time, not response time. A 30-second first reply does not prevent abandonment if the conversation goes silent after that. Use HelpScout’s Time-to-Resolve report (filtered to vortex-iq) for the matching SLA tracking. Multi-mailbox: should I split this card per Mailbox? Yes if your Mailboxes map to separate teams. Use vortex_iq.mailbox_filter to scope per-Mailbox panels. HelpScout’s structure naturally aligns with this split.

​
Tracked live in Vortex IQ Nerve Centre

Abandoned Findings (>14d no movement) is one of hundreds of KPI pulses Vortex IQ tracks across Help Scout and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.