Findings sat in the backlog with no status change for two weeks, these are the ones losing money silently.
At a glance
Open Vortex IQ-tagged Gorgias tickets that have had no status, assignee, or message change in the last 14 days. The silent-leak subset of the open backlog: findings that were filed, never picked up, and are quietly compounding revenue risk while the team focuses on live shopper queries. On Gorgias merchants this card is particularly important because the team’s daily rhythm prioritises live chat / email response times over ticket-style finding triage; without this card, the abandoned bucket grows unnoticed.
| What it counts | Open Gorgias tickets tagged vortex_iq whose last_message_datetime is older than 14 days AND assignee_user has not changed in 14 days AND status has not changed in 14 days. Each criterion uses Gorgias’s audit timestamp on the matching field. |
| What counts as movement | Any of: agent reply, internal note, status change, assignee change, tag change, macro applied. Customer reply does not count (Vortex IQ tickets rarely have customer-facing replies, but vortex_iq tickets in some merchant setups do; if the customer replies, the abandonment clock does NOT reset because the team has not yet acted on the customer’s reply). |
| Project / board scope | All tickets across all Gorgias Integrations (Shopify domains) the connector token reads. Multi-store merchants see a blended count by default. |
| Status filter | status:open only. Gorgias has only two terminal states; closed tickets drop out. |
| Issue type filter | All Vortex IQ-tagged tickets included. Sub-tags (vortex_iq:checkout, vortex_iq:catalogue) do not filter the count. |
| Resolution counts | N/A on this card; abandonment is about the open population only. |
| API endpoint | GET /api/tickets?tags=vortex_iq&status=open&order_by=last_message_datetime&order_dir=asc, paginated; client-side filter on the 14-day cutoff against last_message_datetime, assignee_user_id_updated_at, and status_updated_at. |
| Time window | RT, refreshed every 60 seconds. The 14-day staleness clock evaluates on every webhook event and on a 5-minute scheduled refresh as a safety net. |
| Alert trigger | >5 warn, >15 critical. The warn threshold catches early stagnation; the critical threshold reflects systemic execution failure (more than 15 findings going stale on a Gorgias merchant means the team is fully consumed by live shopper work and cannot absorb the audit programme). |
| Sentiment key | Threshold-based, {warn: 5, critical: 15}. |
| Time zone | Account timezone in Settings, Account, Timezone. The 14-day cutoff aligns to the account timezone, not UTC, so the abandonment boundary matches the team’s working calendar. |
| Roles | owner, operations |
Calculation
Calculated automatically from your Gorgias data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A US DTC apparel brand on Shopify Plus running Gorgias Advanced. Two storefronts (US main + DTC outlet). Snapshot taken on 02 May 26 at 14:25 ET.| Storefront | Open Vortex IQ tickets | Abandoned (>14d no movement) | Notes |
|---|---|---|---|
| US main | 13 | 5 | Three checkout-error findings from the 18 Apr release; one returns-policy URL drift; one cart-page metadata regression. |
| DTC outlet | 9 | 4 | Catalogue findings from a recent migration; assignee-on-leave the entire window. |
| Total open | 22 | 9 | At warn (>5) but below critical (>15). |
- Abandoned doubled vs the 30-day average. This is the warning signal; the headline open count (22) hasn’t moved much, but the queue is stagnating. The team is filing Vortex IQ tickets at a normal rate; the close rate is what dropped.
- The DTC outlet cluster has a single root cause. Four findings stagnant since the catalogue lead went on leave. The fix is not “close the findings”, it is “reassign the queue today”. Open Gorgias’s Tickets, Group by Assignee and confirm.
- The three checkout-error findings on US main are post-release debt. Filed shortly after the 18 Apr release and never picked up. Checkout findings on Shopify Plus brands map directly to conversion-rate impact; pair with
shopify.ecommerce_conversion_rateto quantify the cost. If conversion rate dipped after 18 Apr, the unfixed findings are likely contributing. - The returns-policy URL drift is the single highest-revenue-risk item. Returns-policy mismatches between footer, knowledge base, and checkout are a known conversion killer on DTC apparel. This single finding likely costs more revenue per day than the other 8 abandoned items combined.
- The right action is a triage meeting today, not a hire. Gorgias merchants typically run lean ops teams; the playbook is a 30-minute weekly “abandoned review” with one ops lead. Mark anything with no real merchant impact as
closed(which is Gorgias’s only terminal state). Reassign the rest into the next sprint or week. We see Gorgias-using merchants close 30 to 50% of abandoned findings on this triage; the remainder being correctly prioritised is the actual win, not the count. - Pair with
gor_open_ticketsfor context. If global Gorgias backlog is also elevated, the team is overloaded across the board (likely a promotional push or a returns spike); the audit programme is being deprioritised under load. If global tickets are flat but Vortex IQ abandoned is rising, it is specifically the audit work that is being deprioritised.
Sibling cards merchants should reference together
| Card | Why pair it with Abandoned Findings | What the combination tells you |
|---|---|---|
| VortexIQ Findings Open | Abandoned is a subset of open. The ratio is the steadier read. | Abandoned ÷ Open above 30% means a third of the queue has gone dormant. |
| Finding Resolution Rate (90d) | Resolution rate drops first; abandoned count rises second. | Resolution falling for two weeks then abandoned spiking is the textbook capacity-collapse sequence. |
| Open Tickets (all) | Total Gorgias backlog. | Both elevated = team overloaded across the board; abandoned in isolation = audit deprioritised specifically. |
| Avg First-Response Time | Gorgias’s headline merchant metric. | FRT rising + abandoned rising = team straining; FRT flat + abandoned rising = team prioritising shoppers over findings. |
| Tickets by Assignee | Tells you whether abandonment concentrates on one person. | If 70% of abandoned findings sit on one assignee, the fix is reassignment, not hiring. |
| Shopify Conversion Rate / BigCommerce Conversion Rate | The downstream truth metric. | Abandoned rising for 14+ days predicts a conversion rate dip in the following 2 to 4 weeks; the lag is shorter on Gorgias merchants than Zendesk merchants because Gorgias-using brands skew Shopify Plus / high-traffic where regressions show fast. |
| Refund Rate (Shopify / BigCommerce) | The retention-side cost metric. | Refund spikes drive most audit findings; abandoned findings on returns-policy clusters drive refund spikes back. |
| Customer Service Sentiment | NPS-side outcome. | Sustained abandoned >10 for 4+ weeks predicts CSAT drop of 3 to 5 points within a quarter. |
Reconciling against the vendor’s own dashboard
Where to look in Gorgias’s own dashboard:Gorgias Tickets list, filterWhy our number may legitimately differ from a saved Gorgias view:tags:vortex_iq AND status:open. Sort byLast activity ascending. The tickets at the top are the most stale. Manually count those withLast activity > 14 days agoto reconcile. Views, build a saved View fortags:vortex_iq AND status:open AND last activity older than 14 daysand pin it. Gorgias supportslast activity older than X daysas a filter primitive. Statistics, Tickets does not have a direct “abandoned” report; this card is the canonical reading.
| Reason | Direction | Why |
|---|---|---|
| Time zone | Boundary days off | Gorgias Statistics use account timezone; agent UI uses each agent’s profile timezone. The card uses account timezone. For a 14-day cutoff this rarely shifts the count by more than one ticket. |
| Last-activity definition | Either | Gorgias’s last activity includes customer replies; the card excludes customer replies because they do not represent team progress on a finding. A ticket where a customer replied 7 days ago but the team has not responded counts as abandoned in this card; Gorgias’s last activity older than 14d filter would not flag it until day 21. |
| Multi-store aggregation | Either | Card aggregates across all integrations; Gorgias’s UI scopes to a single integration filter at a time. |
| Tag drift | Ours stricter | We require literal vortex_iq. Legacy tags from earlier Vortex IQ versions drop out of our population. |
| Webhook delay | Up to 60s stale | A movement event from the last minute may not have reached our index yet; Gorgias’s UI updates in real time. |
| Macro-applied changes | Either | Some Gorgias macros apply tags or status changes server-side; the card sees these via webhook within 60 seconds. |
| API rate-limit lag | Up to 30s stale during peak | Gorgias caps API requests at 40/sec; large accounts see brief lag. |
| Card | Expected relationship | What causes the divergence |
|---|---|---|
shopify.refund_rate / bigcommerce.refund_rate / adobe_commerce.refund_rate | Inverse correlation. Higher abandoned rate predicts a refund rate rise over a 4 to 8 week trailing window. | Abandoned rising on returns-policy findings = refund rate climbs; abandoned rising on cosmetic findings only = no refund correlation. |
shopify.ecommerce_conversion_rate | Inverse correlation; tighter on Gorgias-using merchants because they skew Shopify Plus / high-traffic. | Abandoned >10 for 4+ weeks predicts conversion-rate dip of 0.05 to 0.15 percentage points. |
shopify.customer_service_sentiment | Inverse correlation; 2 to 4 week lag. | Sustained abandoned >10 for a quarter predicts CSAT drop of 3 to 5 points. |
datadog.dd_health_score | Independent peer; correlates only when audit is dominantly technical. | Both green = balanced engineering culture; technical abandoned + Datadog elevated = engineering firefighting. |
Known limitations / merchant FAQs
Gorgias’s view says I have 7 abandoned findings but Vortex IQ says 9. Which is right? Both, almost always. The two-ticket gap is the standard set of reasons listed in the reconcile section: timezone (Gorgias UI uses agent profile, card uses account), last-activity definition (the card excludes customer replies as movement; Gorgias’s filter includes them), multi-store aggregation (the card sums across stores, Gorgias scopes to one integration), and webhook delay (a movement from the last minute may not have reached the card’s index). Open the per-store stack panel to reconcile. A customer replied to one of my Vortex IQ tickets 5 days ago. Why is it abandoned? Because the team has not responded to the customer reply. The card treats only team movement (agent reply, status change, assignee change, internal note) as resetting the abandonment clock. Customer replies pile pressure on the team but do not represent the team’s progress on the finding. If the customer replied 5 days ago and the team has not responded, the ticket is in the “10-day silent” zone today; another 4 days and it tips into abandoned. Triage these before they cross. The 14-day window feels arbitrary. Can we tune it? Yes, in Settings, Connectors, Gorgias, Abandonment threshold (days). We default to 14 days because it sits one full sprint plus a buffer, which empirically separates “in active backlog” from “forgotten”. CX-led merchants on Gorgias often tune this down to 7 days because their daily rhythm catches stagnation faster than engineering-led teams; agency-led teams on Gorgias sometimes tune it up to 21 days because their work cycles are longer. Multi-store: the count looks alarming on a 2-store merchant. Open the per-store stack panel from the connector drawer to see which storefront drives the abandoned count. In our experience, multi-store merchants typically find one store (often the secondary outlet or migrated catalogue) drives most of the abandoned count while the main store stays clean. Velocity dropped, abandoned count rising. What changed? Standard playbook. (1) Open Tickets by Assignee and look for sudden concentration changes; a key person on leave is the single most common cause. (2) Open Avg First-Response Time; if FRT rose sharply, the team is being pulled into live chat / shopper response and away from finding work. (3) Cross-check against any global-incident pattern; a Black Friday weekend or a returns surge pulls the team off audit work for days at a time. (4) Open Shopify Refund Rate; a refund spike drives ticket volume that crowds findings out. The abandoned count appears suddenly higher overnight. Why? Because the 14-day clock keeps ticking even when no one is working. If five findings were last touched on the same day exactly 14 days ago, all five become abandoned at the same time the next day. Normal and self-corrects within 24 hours of the team picking the queue back up. Should I close abandoned findings or fix them? Both, depending on triage. Run a weekly 30-minute “abandoned review” with one ops lead. For each: if no real merchant impact, close (Gorgias’s only terminal state isclosed, which serves as both “done” and “won’t fix”; add an internal note to mark the latter). If real merchant impact, reassign and put in next sprint. We see Gorgias merchants close 30 to 50% of abandoned findings on this triage; the remainder being correctly prioritised is the win.
Why doesn’t Gorgias have a built-in “abandoned” filter natively?
Gorgias does have last activity older than X days as a filter primitive, which is closer to native than most helpdesks. The card’s added value is the cross-store aggregation, the customer-reply exclusion, and the alert thresholds. If your team is comfortable building a Gorgias View with tags:vortex_iq AND status:open AND last activity older than 14 days, that view will track this card closely; the card’s advantage is the historical trend and threshold-based alerting.
Is this card the right primary watch metric for Gorgias-using merchants?
Yes. Findings Open tells you the queue size; this card tells you the queue health. Use Findings Open to size the team’s workload. Use this card to detect execution discipline regressions. Both are hero cards because they answer different questions; if you only watch one on a Gorgias-using merchant, watch this one. The open count can climb for healthy reasons (audit found more this week, promotional push surfaced edge cases) but a rising abandoned count is rarely benign.
My team uses Gorgias’s automation rules to mass-tag tickets. Does that count as movement?
Yes. Any tag change (including by automation rule, by macro, or by manual agent action) updates the ticket’s tags_updated_at timestamp, which the card watches as a movement signal. This is intentional because automation activity reflects active triage even when no human typed a reply.
A finding important enough to fix manually but we never used Gorgias to track it. Do we close the ticket?
Yes. Set the ticket to closed once the work is done. Otherwise it stays in the abandoned bucket and the timer keeps ticking. Vortex IQ does not auto-close findings just because the underlying audit signal cleared; the human acknowledgement (closing the ticket) is the close signal.
Can we automate closing low-impact abandoned findings?
Yes via Gorgias Rules. Build a rule: IF tags CONTAINS 'vortex_iq' AND last_activity > 21 days AND priority NOT IN [high, critical] THEN close ticket AND apply tag 'auto_closed_low_impact'. This auto-closes the bottom-tier abandoned findings on a 21-day timer, leaving the high-impact ones for human triage. Most Gorgias merchants who adopt this see abandoned-bucket size drop 40 to 60% within a month with no manual triage.