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.
| What it counts | Conversations in the hel_vortexiq_findings_open population whose userUpdatedAt (HelpScout’s “last user activity” field) is older than now() - 14 days. |
| API endpoint | GET /v2/conversations?status=active,pending&tag=vortex-iq&modifiedSince=<14_days_ago>&embed=threads, then invert to find conversations whose userUpdatedAt < cutoff. The API does not natively support “modified before X”, so the connector pages all open Vortex IQ conversations and filters in-memory. |
| Conversation-state filter | Active + Pending (Closed/Spam excluded), same as the parent. |
| What counts as “movement” | Any thread added (customer reply, agent reply, internal note), status change, assignee change, tag change. HelpScout’s userUpdatedAt is the source field. Just opening the conversation in the agent UI does NOT update it. |
| Bot-handled conversations | Beacon auto-replies and Workflow auto-actions create threads, which update userUpdatedAt and reset the 14-day clock. |
| Multi-mailbox aggregation | Aggregated across all Mailboxes. |
| Time window | RT, refreshed every 60 seconds. |
| Alert trigger | Warn at >5, Critical at >15. Absolute counts, not percentages. |
| Sentiment | Threshold gauge: 0-5 healthy, 6-15 warn (amber), 16+ critical (red). |
| Time zone | Account timezone. The 14-day boundary computes in UTC and offsets for display. |
| Roles | owner, operations |
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.| Finding | Mailbox | Age | Last activity | Estimated revenue cost |
|---|---|---|---|---|
| Subscription portal SSO loop on Safari 17 | hello@ | 18 days | Filed, no thread | $1,200/week (subscription churn) |
| Wholesale pricing tier missing on 22 SKUs | wholesale@ | 24 days | Internal note “looking into it” on day 1 | Unknown; quoted manually so visible cost is zero |
| Refund-portal “where is my refund” macro responds in 4h | returns@ | 16 days | Filed | NPS impact, no direct revenue |
| Klaviyo abandoned-cart link 404 | hello@ | 20 days | Filed | $300/week (recovered-revenue gap) |
| Free-shipping threshold widget renders $0 | hello@ | 14 days | Status changed once on day 2 | $700/week (AOV down 4% on cart-aware sessions) |
- **Composite weekly leak ≈ 2.2k/week is roughly $9k/month, well above the cost of an additional triage hour per week.
- 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. - 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. - 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.
- Pair this card with
shopify.refund_rateandshopify.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
| Card | Why pair it with Abandoned Findings | What the combination tells you |
|---|---|---|
| VortexIQ Findings Open | Total backlog. Abandoned is a subset. | Abandoned ÷ Open is the “stale ratio”. Above 30% means triage broken; below 10% means team healthy. |
| Finding Resolution Rate (90d) | Throughput. | Abandoned rising while resolution rate steady means team picks easy tickets, lets hard ones sit. |
| Avg Time-to-Fix | Resolution latency. Abandoned is the long tail. | If avg is 5 days but Abandoned is 15, distribution is bimodal. |
| Top Assignees Overloaded | Capacity bottleneck. | If 60%+ of abandoned tickets share an assignee, reassign or add capacity. |
| Refund Rate (Shopify / BigCommerce / Adobe) | Downstream revenue cost. | Abandoned >10 + refund rate climbing equals direct evidence audit programme is broken. |
| Customer Service Sentiment (Shopify) | NPS-side cost. HelpScout users care intensely about this metric. | UX-flavoured abandoned findings predominantly impact this. |
| Datadog Operational Health Score | Technical findings should map to Datadog signals. | Abandoned “checkout error” finding + Datadog steady = possible false positive. |
Reconciling against the vendor’s own dashboard
Where to look in HelpScout’s own dashboard:Inbox view (secure.helpscout.net/conversations) with filters:Why our number may legitimately differ: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 forvortex-iq-tagged conversations.
| Reason | Direction | Why |
|---|---|---|
| Time zone | Boundary day off | The 14-day cutoff is computed in UTC by Vortex IQ; HelpScout Reports honour the company timezone. |
| In-memory filter | Ours equals theirs in steady state | The Conversations API does not natively support “modified before X”, so the connector pages all open Vortex IQ conversations and filters in-memory. Brief lag during refresh on accounts with very large open counts. |
| Trash inclusion | Ours lower | Trashed conversations are excluded from GET /v2/conversations; UI shows them for 30 days. |
| What counts as movement | Ours stricter on bot-only updates | We use userUpdatedAt, which Beacon auto-replies update. Some HelpScout views differentiate human vs bot activity. |
| Multi-mailbox aggregation | Either | Card aggregates across Mailboxes; per-Mailbox views are subsets. |
| Card | Expected relationship | What causes the divergence |
|---|---|---|
shopify.refund_rate / bigcommerce.refund_rate / adobe_commerce.refund_rate | Abandoned findings often correspond to chronic refund drivers. | Refunds up + abandoned >10 = audit programme broken. |
shopify.customer_service_sentiment | NPS slowly degrades as abandoned count climbs. | Lag between abandonment and NPS dip is typically 4-8 weeks. |
Known limitations / merchant FAQs
Why does HelpScout Reports show a different number? Three reasons:- Field choice. Reports’ “Time-to-Resolve” uses
closedAt, notuserUpdatedAt. We useuserUpdatedAtbecause abandoned-but-still-open is the population that matters. - Time zone. The 14-day cutoff is UTC for the card; Reports honour company timezone.
- API filter limitation. The card filters in-memory after a
modifiedSincequery, which can briefly disagree with the UI on accounts with very large open backlogs.
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.