> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Gorgias on Vortex IQ > Monitor Gorgias pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn. Monitor Gorgias pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn. [Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=gorgias) performance signals automated checks automated fixes workflows API operations ### What you can achieve Capabilities are grouped around merchant outcomes, not API terminology. Find failures, leaks and risks before they cost sales. Monitor orders, fulfilment, delivery and settlement. Improve discovery, conversion, campaigns and repeat purchase. ### From connection to verified outcome The controlled sequence every capability follows. Nothing changes a connected system without the approval step. Authorise the source. Scopes are shown before access is granted. Watch the signals against your own baselines, not universal defaults. Run checks and gather evidence specific to your store. Explain what happened, why it matters and the proposed action. You review scope, risk and reversibility before anything changes. Apply through governed connector operations. Confirm the intended result and keep the receipt. No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls. ### Monitor performance 23 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system. | Signal | Alert behaviour | What it tracks | | ----------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | **Avg Cycle Time (days)** | Alert band 3 / 7 | Description pending editorial review; the signal is live. | | **Avg Lead Time (days)** | Alert band 7 / 14 | Description pending editorial review; the signal is live. | | **Avg Time-to-Fix (days)** | Alert band 7 / 14 | Description pending editorial review; the signal is live. | | **Backlog by Priority** | Merchant rule | Backlog by Priority. | | **Backlog by Status** | Merchant rule | Backlog by Status. | | **Blocked Tickets** | Alert band 3 / 8 | Open tickets tagged blocked / waiting-on-customer - the operational queue's stuck list. | | **Cycle Time by Priority** | Alert band 3 / 5 | Cycle Time by Priority. | | **Finding Resolution Rate (90d)** | Alert band 75 / 50 | What share of audit findings filed in the last 90d actually got fixed via Gorgias. Healthy band on Gorgias is higher (>75%) thanks to inline order | | **In Progress** | Merchant rule | Open tickets with an assignee and recent activity - work actively being handled. | | **Oldest Open (days)** | Alert band 30 / 90 | Age in days of the oldest still-open ticket - backlog-rot signal. | | **Open Tickets** | Alert band 0 / 100 | Total open tickets across the connected storefronts - top-of-funnel backlog volume. | | **Overloaded Assignees (>10 open)** | Alert band 0 / 1 | Agents with >10 open tickets - capacity bottleneck candidates. | | **Scope Added Mid-Sprint** | Alert band 5 / 15 | Description pending editorial review; the signal is live. | | **Sprint Progress** | Alert band 90 / 70 | Description pending editorial review; the signal is live. | | **Sprint Velocity (avg)** | Alert band 0 / 20 | Sprint Velocity (avg) over time. | | **Throughput Trend** | Merchant rule | Description pending editorial review; the signal is live. | | **Tickets Resolved (7d)** | Alert band 0 / 25 | Description pending editorial review; the signal is live. | | **Tickets by Assignee** | Alert band 5 / 10 | Tickets by Assignee. | | **Unassigned Tickets** | Alert band 5 / 20 | Description pending editorial review; the signal is live. | | **VortexIQ Findings In Progress** | Merchant rule | Description pending editorial review; the signal is live. | | **VortexIQ Findings Open** | Alert band 5 / 20 | Tickets we filed from audit findings that haven't been resolved yet - the live backlog of things VortexIQ surfaced, in the same inbox as live shopper | | **VortexIQ Findings Resolved** | Merchant rule | Description pending editorial review; the signal is live. | | Signal | Alert behaviour | What it tracks | | ----------------------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Findings sat in the backlog with no team movement for two weeks - these are the ones losing money silently while the team works live shopper queries. | ### Audit risks and opportunities A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. Open a check for the detail. **Severity** high · **Outcome** Grow revenue · **Fix status** Report only CSAT below 70 percent predicts churn before it shows in revenue; the transcripts behind the score say exactly what to fix. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `SUPPORT-CSAT-001` **Severity** high · **Outcome** Run operations · **Fix status** Report only Breached first-response SLAs compound: late answers create chase messages, which create more queue, which creates later answers. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `SUPPORT-SLA-001` **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only Customers are waiting a median of over 4 hours just to hear back for the first time, before their actual issue is even addressed. Slow first response is one of the most common drivers of a bad support experience and of customers escalating, cancelling an order, or leaving a negative review while the Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `SUPPORT-FRT-001` **Severity** medium · **Outcome** Run operations · **Fix status** Report only The open-conversation backlog grew more than 20% in a week. A growing backlog means response and resolution times for everyone in the queue are about to get worse, not just the customers who are waiting today; the problem compounds until incoming volume and resolution capacity come back into balance Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `SUPPORT-BACKLOG-001` #### Build your own automated fixes Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change. ### Automate approved work Vortex IQ is integrated with **5 read** and **3 write** operations across tickets, accounts, integrations, ticketmessages, users on Gorgias. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words. Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=gorgias) #### Ready to build your first Gorgias workflow Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build. | Resource | Read operations | Write operations | | -------------- | --------------- | ---------------- | | tickets | 2 | 2 | | accounts | 1 | 0 | | integrations | 1 | 0 | | ticketmessages | 0 | 1 | | users | 1 | 0 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.