> ## Documentation Index
> Fetch the complete documentation index at: https://fliqr.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Measure Conversation Performance Metrics in Fliqr AI

> Track conversation volume, flow completion rates, drop-off points, and channel breakdown to understand how your automations perform over time.

The Conversations analytics panel gives you a quantitative view of how your automations are running. Raw message counts tell you activity; completion rates and drop-off data tell you whether your flows are actually working. Reviewing these metrics regularly helps you identify which flows need revision and where contacts lose interest or get stuck.

## Overview

Every conversation that passes through Fliqr AI — whether handled by a flow, an AI Agent, or a live agent — is recorded and aggregated here. The panel breaks performance down by time period, channel, and individual flow, so you can compare across dimensions without exporting data manually.

## Metrics Explained

| Metric                   | What it measures                                             |
| ------------------------ | ------------------------------------------------------------ |
| Total Conversations      | Number of unique conversation threads in the selected period |
| New Contacts             | Contacts who had their first interaction in this period      |
| Messages Sent            | Outbound messages delivered by Fliqr AI                      |
| Messages Received        | Inbound messages from contacts                               |
| Flow Completion Rate     | Percentage of flow starts that reached the final block       |
| Average Response Time    | Mean time between an inbound message and Fliqr AI's reply    |
| Conversations by Channel | Breakdown of threads by WhatsApp, Instagram, Messenger, etc. |
| Conversations Over Time  | Daily, weekly, or monthly trend line                         |

## Viewing the Dashboard

<Steps>
  <Step title="Navigate to Analytics">
    From the left navigation, click **Analytics → Conversations**.
  </Step>

  <Step title="Set your date range">
    Use the date picker at the top of the panel to select the period you want to analyze. You can choose preset ranges (Last 7 days, Last 30 days, Last quarter) or enter custom start and end dates.
  </Step>

  <Step title="Apply filters">
    Use the filter dropdowns to narrow the data by channel (e.g., WhatsApp only) or by a specific flow. This is useful when you want to compare how the same flow performs across different channels.

    \[SCREENSHOT: Conversation analytics dashboard showing a line chart of daily conversations and a channel breakdown pie chart]
  </Step>

  <Step title="Inspect individual data points">
    Hover over any point on the line chart to see the exact count and date. Click a channel segment in the pie chart to filter the rest of the dashboard to that channel.
  </Step>

  <Step title="Review the flow funnel">
    Scroll down to the **Flow Funnel** section. Select a flow from the dropdown to see impression counts for each block. The widest gap between two consecutive blocks is your primary drop-off point.
  </Step>
</Steps>

## Reading the Flow Funnel

Each block in a flow records how many contacts passed through it. As contacts drop off at any point — by not responding, closing the chat, or hitting an error — the count decreases. The funnel makes this visible as a series of bars narrowing from top (flow entry) to bottom (flow exit).

Drop-off is significant when the gap between two blocks is larger than expected. Common causes:

* **A question with no quick-reply options** — contacts who have to type a free-form response often don't.
* **A long delay block** — contacts may re-engage elsewhere before the next message arrives.
* **A confusing or ambiguous message** — especially in languages where the phrasing doesn't translate well.

<Tip>
  A low completion rate on a specific flow often means one block is too complex or the next step isn't clear. Check the flow funnel for the exact drop-off point, then A/B test a revised message for that block.
</Tip>

## What's Next

<CardGroup cols={2}>
  <Card title="Unanswered Messages" href="/docs/analytics/unanswered-messages">
    Find inbound messages that no automation handled and build rules to cover them.
  </Card>

  <Card title="Sales Analytics" href="/docs/analytics/sales-analytics">
    Track revenue, conversion rates, and order volume tied to your automations.
  </Card>
</CardGroup>
