> ## 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. # Agile CRM on Vortex IQ > Monitor Agile CRM pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn. Monitor Agile CRM 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=agile-crm) performance signals automated checks prepared fixes proven 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. Keep tracking, access and change under governed control. Improve discovery, conversion, campaigns and repeat purchase. Monitor orders, fulfilment, delivery and settlement. Find storefront, speed, accessibility and journey problems. Identify missing, inconsistent or outdated product data. ### 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 34 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 | | ----------------------------------- | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | **Active Subscribers (Est.)** | Merchant rule | Estimated subscribed (non-unsubscribed, non-bounced) contacts - the marketable audience size. | | **Bounce Rate** | Alert band 2 / 5 | Bounces ÷ sent (lower is better). Sentiment band good ≤2% / warn ≥5%. | | **Campaign Revenue vs Ecom Orders** | Merchant rule | Ties Agile CRM email sends to real ecom orders - exposes campaigns that look engaged but drive no revenue. | | **Checkout-to-Order Rate** | Merchant rule | Placed orders ÷ checkouts started - where the tail of the funnel leaks. | | **Delivery Rate** | Alert band 98 / 95 | Delivered ÷ sent. Sentiment band good ≥98% / warn ≤95%. | | **Email Health KPIs** | Merchant rule | Composite email-health roll-up (deliverability + engagement) for an at-a-glance read. | | **Engagement Funnel** | Merchant rule | Sent → delivered → opened → clicked → converted funnel. Drop-offs expose where engagement leaks. | | **List Health Summary** | Merchant rule | Roll-up of list-decay signals (bounced / unsubscribed / inactive share) across lists. | | **Refund Rate** | Alert band 2 / 8 | Refunded ÷ placed orders (lower is better) - quality/expectation gap signal. | | **Spam Complaint Rate** | Alert band 0.1 / 0.3 | Spam complaints ÷ delivered (lower is better). Good ≤0.1% / warn ≥0.3% - sustained breach risks send throttling. | | **Subscriber vs Customer Drift** | Merchant rule | Marketable-audience vs buyer-base gap. Customers off-list = missed lifecycle email; clicking subscribers who never buy = nurture target. | | **Unsubscribe Rate** | Alert band 0.5 / 2 | Unsubscribes ÷ delivered (lower is better). Good ≤0.5% / warn ≥2%. | | Signal | Alert behaviour | What it tracks | | -------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **CRM Data Hygiene Score** | Alert band 95 / 80 | Composite of two confirmed real Agile CRM Contact properties: share with an email property populated and share with a phone property populated (both u | | **Email Click Rate** | Alert band 2 / 0.5 | Clicks ÷ delivered. Sentiment band good ≥2% / warn ≤0.5%. | | **Email Open Rate** | Alert band 20 / 10 | Opens ÷ delivered. Sentiment band good ≥20% / warn ≤10%. | | **Flow Status Breakdown** | Merchant rule | Flows grouped by status (active / paused / draft) - quick automation-health glance. | | **Flow Trigger Types** | Merchant rule | Flows grouped by trigger type - shows how automations are being entered. | | **Flows List** | Merchant rule | Tabular list of automation flows with status + enrolment counts. | | **List Count** | Merchant rule | Number of contact lists in the account. | | **Lists Overview** | Merchant rule | Per-list table with name, type and contact count. | | **Placed Orders Total** | Merchant rule | Tracked placed orders attributed through Agile CRM in the window. | | **Segments Overview** | Merchant rule | Per-segment (saved filter) table with name and contact count. | | **Top Lists by Name** | Merchant rule | Largest lists ranked by contact count. | | Signal | Alert behaviour | What it tracks | | ----------------------------- | --------------- | -------------------------------------------------------------------------------------------------------- | | **Campaign Status Breakdown** | Merchant rule | Count of campaigns by status (draft / scheduled / sent / paused / archived). | | **Conversion Rate** | Merchant rule | Placed orders ÷ recipients - email-to-purchase conversion. | | **Flow Count Summary** | Merchant rule | Total automation flows / campaigns configured in the account. | | **Revenue per Recipient** | Merchant rule | Attributed revenue ÷ unique recipients - value extracted per person reached. | | **Revenue per Send** | Merchant rule | Attributed revenue ÷ emails sent - the cleanest send-efficiency signal. | | **Total Revenue** | Merchant rule | Total email-attributed revenue across campaigns in the window - top-line health for the whole connector. | | **Total Sends** | Merchant rule | Sum of emails sent across campaigns - denominator for the rate cards below. | | Signal | Alert behaviour | What it tracks | | ---------------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Lead Response Time** | Alert band 60 / 480 | Median minutes from Contact.created\_time to the start\_time of the first logged Event linked to that contact (GET /dev/api/events, contact\_ids\[]). Agil | | **Stalled Deal %** | Alert band 10 / 30 | Open Deals (archived = false) with no note logged in 14 days, as a share of all open Deals. GET /dev/api/opportunity/{deal-id}/notes is Agile CRM's co | | Signal | Alert behaviour | What it tracks | | --------------------- | --------------- | ------------------------------------------------------------------ | | **Checkouts Started** | Merchant rule | Tracked checkout-started events from Agile CRM ecommerce tracking. | | Signal | Alert behaviour | What it tracks | | ---------------------- | ----------------- | ---------------------------------------------------------------------- | | **Click-to-Open Rate** | Alert band 10 / 3 | Clicks ÷ opens - creative/content effectiveness. Good ≥10% / warn ≤3%. | ### 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** critical · **Outcome** Catalogue quality · **Fix status** Report only Once this credential fails, VortexIQ stops seeing deals, contacts and pipeline activity from this CRM entirely, and every pipeline and data-quality finding here goes stale from that moment, silently, until someone notices the numbers stopped updating. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `CRM-AUTH-001` **Severity** high · **Outcome** Grow revenue · **Fix status** Report only Leads answered after 8 hours convert at a fraction of the rate of leads answered in minutes; speed-to-lead is the cheapest conversion lever in the pipeline. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `CRM-LEAD-001` **Severity** high · **Outcome** Run operations · **Fix status** Report only Deals with no activity for two weeks are quietly dying; a nudge list ordered by value recovers some before they close-lose themselves. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `CRM-PIPE-001` **Severity** medium · **Outcome** Run operations · **Fix status** Report only More than 1 in 5 records is missing a required field. Incomplete records make segmentation, reporting and any automation keyed off those fields (routing, scoring, follow-up sequences) unreliable, so the gap compounds into every process built on top of this data, not just the records themselves. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `CRM-DATA-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 **11 read** and **2 write** operations across devcampaignlogs, devcontacts, devcontactcounts, devcontactedittags, devevents, devfilters on Agile CRM. 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=agile-crm) #### Ready to build your first Agile CRM 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 | | ------------------ | --------------- | ---------------- | | devcampaignlogs | 1 | 0 | | devcontacts | 1 | 0 | | devcontactcounts | 1 | 0 | | devcontactedittags | 0 | 1 | | devevents | 1 | 0 | | devfilters | 1 | 0 | | devlists | 1 | 0 | | devopportunitys | 1 | 0 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.