> ## 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. # Crisp on Vortex IQ > Monitor Crisp pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn. Monitor Crisp pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn. 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. [Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) ยท [How connecting works](/integrations/connector-catalogue) | **24** | **3** | **Build your own** | **Ready to build yours** | **9** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | performance signals | automated checks | automated fixes | workflows | API operations | ## Monitor performance 24 performance signals. Signals with an alert band can raise Nerve Centre alerts; every signal supports a merchant-configured watcher. | Signal | Outcome | Alert behaviour | What it tracks | | ----------------------------------------- | ------------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Abandoned Findings (>14d no movement)** | Protect revenue | Alert band 0 / 5 | Findings with no agent activity in 14 days - quietly losing money while everyone assumes they are in the queue. | | **Finding Resolution Rate (90d)** | Run operations | Alert band 75 / 50 | resolved\_in\_90d / created\_in\_90d x 100. Is the team fixing what Vortex IQ surfaces, or is the audit just noise? | | **VortexIQ Findings Open** | Run operations | Alert band 5 / 20 | Crisp conversations tagged vortexiq:finding in pending/unresolved state - open audit work the team has not closed. | | **Avg Cycle Time (days)** | Run operations | Alert band 3 / 7 | Mean days from first-response (work started) to resolved - how long active work takes. | | **Avg Lead Time (days)** | Run operations | Alert band 5 / 14 | Mean days from created\_at to resolved\_at - total time in the system including queue wait. | | **Avg Time-to-Fix (days)** | Run operations | Alert band 3 / 14 | Mean days from finding created\_at to resolved\_at over the window. | | **Backlog by Priority** | Run operations | Alert band 25 / 50 | Open conversations split by priority segment - is the queue top-heavy with urgent work? | | **Backlog by Status** | Run operations | Merchant rule | Open conversations split by state (pending / unresolved) - the shape of the working inbox. | | **Blocked Tickets** | Run operations | Alert band 0 / 8 | Open conversations tagged blocked/waiting - cannot progress until an external dependency clears. Warn 3 / critical 8. | | **Cycle Time by Priority** | Run operations | Alert band 2 / 5 | Mean cycle time bucketed by priority - are urgent items actually moving faster? | | **First Response Time (min)** | Run operations | Alert band 30 / 240 | Crisp's own 'First Response Time' Analytics metric (POST /website/{website_id}/analytics/generate, confirmed real route per the official Go SDK's route builder) - average | | **In Progress** | Run operations | Merchant rule | Conversations in unresolved state with an operator assigned - being handled right now. | | **Oldest Open (days)** | Run operations | Alert band 14 / 90 | Age in days of the oldest still-open conversation - the maximum-age outlier. | | **Open Tickets** | Run operations | Alert band 50 / 200 | Every unresolved Crisp conversation (customer chat + findings) - the whole open inbox. | | **Overloaded Assignees (>10 open)** | Run operations | Alert band 0 / 1 | Count of operators carrying more than 10 open conversations - redistribution signal. | | **Scope Added Mid-Sprint** | Run operations | Alert band 5 / 15 | % of findings added after the sprint started - work preempting committed audit follow-up. | | **Sprint Progress** | Run operations | Alert band 90 / 70 | % of the current sprint committed findings resolved against time elapsed - burn-down health. | | **Sprint Velocity (avg)** | Run operations | Alert band 0 / 20 | Findings resolved per sprint, averaged over the last 5 sprints - capacity trend. | | **Throughput Trend** | Customer experience | Merchant rule | Daily resolved-count sparkline over 30 days - is the team speeding up or slowing down? | | **Tickets Resolved (7d)** | Run operations | Alert band 0 / 25 | Conversations moved to resolved in the last 7 days vs the prior 7 - weekly outflow. | | **Tickets by Assignee** | Run operations | Alert band 5 / 10 | Open conversations per operator - where the work is concentrated. | | **Unassigned Tickets** | Run operations | Alert band 0 / 20 | Open conversations with no operator assigned - nobody owns these. Warn 5 / critical 20. | | **VortexIQ Findings In Progress** | Run operations | Merchant rule | Findings in unresolved state with an assigned operator - actively being worked. | | **VortexIQ Findings Resolved** | Run operations | Merchant rule | Findings moved to resolved state in the trailing 90 days - the raw outflow count behind resolution rate. | ## 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. | Check | Severity | Outcome | Why it matters | Fix status | | --------------------------------------------------------- | -------- | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | | **CSAT below 70%** | high | Grow revenue | CSAT below 70 percent predicts churn before it shows in revenue; the transcripts behind the score say exactly what to fix. | Report only | | **Median first-response time above 4h** | medium | Protect revenue | 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 b | Report only | | **Open-conversation backlog rising > 20% week-over-week** | medium | Run operations | 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 | Report only | ### Build your own automated fixes 3 checks report findings on Crisp today. Turn any finding into an automated fix with a Vortex IQ workflow: **13,885 read and write operations across 229 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 **4 write** operations across websites, websiteanalyticsgenerates, websiteconversations, websiteconversationmessages, websiteconversationmetas, websiteconversationroutings on Crisp. Combine them with anything from the **13,885 operations across 229 connectors** to automate the work in your own words. Changes follow the merchant's configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. Read-only operations do not modify the connected system. [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=crisp) | Resource | Read operations | Write operations | | --------------------------- | --------------- | ---------------- | | websites | 1 | 0 | | websiteanalyticsgenerates | 0 | 1 | | websiteconversations | 1 | 0 | | websiteconversationmessages | 1 | 0 | | websiteconversationmetas | 1 | 0 | | websiteconversationroutings | 0 | 1 | | websiteconversationsegments | 0 | 1 | | websiteconversationstates | 0 | 1 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected. ### Ready to build your first Crisp 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. *** *Generated from the connector capability graph. Counts reflect the servable registry after alias normalisation and de-duplication, and refresh automatically when the registry changes.*