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 Freshdesk queue with no status, comment, assignee, or tag 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. Every ticket here was important enough to file but has not been touched, which usually means it has fallen off the team’s mental backlog.
Calculation
Calculated automatically from your Freshdesk 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 UK fashion SMB from the parent card. Snapshot taken on 02 May 26 at 14:20 BST. Of the 17 open Vortex IQ findings, 6 have not seen any update for 14 days or more.
The card reads 6. Warn at 5, Critical at 15. Just over the warn threshold, panel is amber. Three observations:
- Composite weekly leak ≈ £7,000. Five of the six findings translate directly to weekly revenue loss; the sixth (returns SSO) is operational cost. £7k/week is roughly £30k/month, which exceeds the cost of an additional CS triage agent on a typical mid-market SMB. The card is your business case for adding capacity.
- The Klarna finding is the single most expensive abandoned ticket. £4.2k/week dwarfs the others. It’s been sitting for 16 days with one “investigating” comment from day 1. This is the classic “looked at, never resolved” pattern. Apply a Freshdesk SLA Policy that triggers an automatic escalation if a Vortex IQ ticket sits in the same status for 7 days.
- The 27-day-old Algolia “midi dress” finding is the most diagnostic. A category-defining search term returning zero is a leading indicator of a much wider catalogue indexing gap. Pair with
shopify.search_zero_results. If sitewide zero-result rate is up, this single finding is hiding a larger issue. - The free-shipping threshold widget tipped into Abandoned exactly today. It was last touched on day 2 (status change), then nothing. Day 14 cutoff. The cheapest action: a one-line “still scoped for next sprint” internal note resets the clock and removes it from this list. Visible movement is the cheapest abandonment-prevention.
- Pair this card with
shopify.refund_rateandshopify.customer_service_sentiment. “Abandoned findings: 6, refund rate up 0.4 pts, NPS down 4 points” makes the cost legible at the board level.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in Freshdesk’s own dashboard:Tickets list with filters:Why our number may legitimately differ:Tag = vortex_iq,Status IS Open OR Pending,Last updated more than 14 days ago. Save as “Vortex IQ abandoned findings”. Admin → Workflows → Ticket Filters to make this a shared view across the team. Analytics → Curated Reports → Aging Tickets with the same filters.
Cross-connector reconciliation:
Known limitations / merchant FAQs
Why does Freshdesk Analytics show a different number? Three reasons:- Field choice. Freshdesk’s “Last Activity” field can be configured to exclude private notes; we always use
updated_atwhich includes them. - Time zone. The 14-day cutoff is UTC for the card; Analytics honours dataset zone.
- Search API page cap. Counts above ~300 may lag the bulk API briefly during refresh.
updated_at, so the 14-day clock resets. We treat any update as “the team is still thinking about it”. Abandonment is silence, not lack of resolution.
Should Freddy AI updates count as movement?
Yes by default. If you’d rather discount Freddy-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+ Vortex IQ-connected merchants, the probability that an open finding closes drops sharply after day 14 and approaches zero after day 21. 14 is the latest day at which intervention typically rescues the ticket.
My team flags some findings as “won’t fix” via a custom status. Do they count?
Yes, until the status maps to Resolved or Closed. “Won’t fix” custom statuses sit in the open bucket from the API’s perspective. To exclude them, map your won’t-fix custom status to Closed or add a workflow that resolves them automatically.
The count went from 6 to 0 overnight, what happened?
Most likely a bulk update via Freshdesk’s “Edit Multiple Tickets” function added a comment to all matching tickets. That resets updated_at and clears Abandoned. Healthy if it was deliberate triage; suspicious if findings re-enter Abandoned 14 days later (gaming).
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 (someone left, on holiday, deprioritised) rather than a finding influx. Check Top Assignees Overloaded.
Response time vs resolution time, which one is this card about?
Resolution-time-extreme. This card is the long tail of resolution time, not response time. A ticket can have a 30-second first response and still be abandoned if the conversation goes silent after that. Use Freshdesk SLA Policies’ “Resolution time” target (not “First response time”) for Vortex IQ-tagged tickets.
Multi-product: should I split this card per Product?
Yes if your Products map to separate engineering teams. Use vortex_iq.product_filter to scope per-Product panels.