> ## 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. # Freshsales on Vortex IQ > Monitor Freshsales pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn. Monitor Freshsales 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=freshsales) 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. Monitor orders, fulfilment, delivery and settlement. Improve discovery, conversion, campaigns and repeat purchase. Find storefront, speed, accessibility and journey problems. Keep tracking, access and change under governed control. 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 30 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 | | -------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | **CRM Data Hygiene Score** | Alert band 95 / 80 | Composite of two confirmed real Freshsales Contact fields (via GET /contacts/view/\[view\_id]): share with email populated and share with mobile\_number | | **Click-to-Open Rate** | Alert band 10 / 3 | Clicks / opens - message relevance. Gauge bands: good ≥10%, warn ≤3%. | | **Email Click Rate** | Alert band 2 / 0.5 | Clicks / delivered. Gauge bands: good ≥2%, warn ≤0.5%. | | **Email Open Rate** | Alert band 20 / 10 | Opens / delivered. Gauge bands: good ≥20%, warn ≤10%. | | **Flow Count Summary** | Merchant rule | Total sequences (flows) and how many are active. | | **Flow Trigger Types** | Merchant rule | Sequences grouped by trigger type (manual/list-join/segment/deal-stage/property). | | **Flows List** | Merchant rule | Tabular list of sequences with status, trigger and 30d enrollment. | | **Lists Overview** | Merchant rule | Per-list table: name, type, member count, active members. | | **Placed Orders Total** | Merchant rule | Orders attributed to email sends in the window (Placed Order metric). | | **Segments Overview** | Merchant rule | Dynamic segments with member counts and last refresh. | | **Top Lists by Name** | Merchant rule | Largest lists ranked by member count. | | Signal | Alert behaviour | What it tracks | | ----------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------ | | **Campaign Status Breakdown** | Merchant rule | Count of sales campaigns by status (draft/scheduled/sending/sent/paused/archived). | | **Checkout-to-Order Rate** | Merchant rule | Of email-driven checkouts started, the share that became orders; reconciled with the ecom sibling's order events. | | **Conversion Rate** | Merchant rule | Orders / delivered emails - overall email conversion. | | **Engagement Funnel** | Merchant rule | Sent → delivered → opened → clicked → converted funnel for outbound email. | | **List Health Summary** | Merchant rule | Active-member share across lists - low = stale/decaying audience. | | **Revenue per Recipient** | Merchant rule | Attributed revenue divided by unique recipients. | | **Revenue per Send** | Merchant rule | Attributed revenue divided by total sends. | | **Total Revenue** | Merchant rule | Email-attributed revenue from Freshsales sales campaigns; cross-checked against the ecom sibling's actual order revenue. | | **Total Sends** | Merchant rule | Total emails sent across sales campaigns in the window. | | Signal | Alert behaviour | What it tracks | | ----------------------------- | -------------------- | -------------------------------------------------------------------------------------------------------------------- | | **Active Subscribers (Est.)** | Merchant rule | Estimated subscribed/deliverable contacts (subscription\_status = subscribed). | | **Bounce Rate** | Alert band 2 / 5 | Bounces / sent (inverse gauge). Bands: good ≤2%, warn ≥5%. Sustained high = list-hygiene or auth (SPF/DKIM) problem. | | **Delivery Rate** | Alert band 98 / 95 | Delivered / sent. Gauge bands: good ≥98%, warn ≤95%. | | **Email Health KPIs** | Merchant rule | Composite email-health roll-up (delivery, open, click, bounce) in one card. | | **Flow Status Breakdown** | Merchant rule | Sequences grouped by status (active/paused/draft/archived) - paused-heavy = abandoned automation. | | **Refund Rate** | Alert band 1 / 5 | Refunded share of email-attributed revenue - high = post-purchase dissatisfaction or returns leakage. | | **Spam Complaint Rate** | Alert band 0.1 / 0.3 | Spam reports / delivered (inverse gauge). Bands: good ≤0.1%, warn ≥0.3%. Above 0.3% risks sender-reputation damage. | | **Unsubscribe Rate** | Alert band 0.5 / 2 | Unsubscribes / delivered (inverse gauge). Bands: good ≤0.5%, warn ≥2%. | | Signal | Alert behaviour | What it tracks | | --------------------- | --------------- | ------------------------------------------------------------- | | **Checkouts Started** | Merchant rule | Checkouts started attributed to email activity in the window. | | Signal | Alert behaviour | What it tracks | | -------------- | --------------- | ---------------------------------------------- | | **List Count** | Merchant rule | Total contact lists configured in the account. | ### 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** 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 **8 read** and **1 write** operations across contacts, contactfilters, contactviews, deals, lists, salecampaigns on Freshsales. 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=freshsales) #### Ready to build your first Freshsales 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 | | -------------- | --------------- | ---------------- | | contacts | 1 | 0 | | contactfilters | 1 | 0 | | contactviews | 1 | 0 | | deals | 1 | 0 | | lists | 1 | 0 | | salecampaigns | 1 | 0 | | sequences | 1 | 0 | | sequencepauses | 0 | 1 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.