> ## 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.

# Navigating the Fliqr AI Dashboard: A Section-by-Section Tour

> A section-by-section guide to the Fliqr AI dashboard covering Inbox, Flows, AI Agents, Contacts, Pipelines, Broadcasts, Analytics, and Settings.

When you first open Fliqr AI, the dashboard can look like a lot at once. This page walks through every major section in the order you're likely to encounter it: starting with the real-time Inbox and moving through the tools you use to build, manage, and measure your automations. Understanding where things live up front saves you time when you're trying to move fast later.

\[SCREENSHOT: Fliqr AI dashboard overview with labeled sections showing the left navigation sidebar and main content area]

## Getting oriented on first login

When you log in for the first time, follow these steps to locate the key areas covered in the sections below:

<Steps>
  <Step title="Identify the left navigation sidebar">
    The sidebar is the primary navigation element. It contains links to Inbox, Flows, AI Agents, Contacts, Pipelines, Broadcasts, Analytics, and Settings. All major platform sections are one click away from here.
  </Step>

  <Step title="Open the Inbox">
    Click **Inbox** in the sidebar to see all active and recent conversations across every connected channel. This is the first place to check when you want to monitor live bot activity or step in manually.
  </Step>

  <Step title="Visit Flows">
    Click **Flows** to see your list of conversation scripts. If this is a new workspace, the list is empty. After the quickstart, your first published flow appears here.
  </Step>

  <Step title="Explore Settings">
    Click **Settings** to find channel connections, team management, integrations, and billing. Most initial workspace setup happens here before building any automation.
  </Step>
</Steps>

## Dashboard sections

<Accordion title="Inbox">
  **What it is:** A unified view of all active and recent conversations across every connected channel—WhatsApp, Instagram, Messenger, Telegram, SMS, Email, Voice, and website chat—in a single feed.

  **What you'll find here:**

  * All incoming messages, organized by channel and recency
  * Conversation thread view with full history
  * Contact profile panel showing tags, custom fields, and pipeline stage
  * Assignment controls to route conversations to specific team members
  * Manual reply composer for human takeover moments

  **When to use it:** Monitor conversations in real time, step in when the bot needs a human touch, or review how automated flows are performing from a live-conversation perspective. The Inbox is also where you handle any escalations flagged by your AI Agents.

  <Note>
    You can filter the Inbox by channel, assignment status, or tag so your team only sees the conversations relevant to them.
  </Note>
</Accordion>

<Accordion title="Flows">
  **What it is:** The visual Flow Builder—the canvas where you design the conversation logic that runs on your connected channels.

  **What you'll find here:**

  * A library of all flows you've created, with draft and published status indicators
  * The canvas editor, where you connect message blocks, condition branches, user input steps, delay timers, and API call blocks
  * A block menu covering every interaction type: text, buttons, carousels, images, audio, video, forms, and more
  * Flow-level analytics showing message delivery rates and drop-off points per block

  **When to use it:** Build every automated conversation here—onboarding sequences, FAQ bots, lead capture forms, appointment booking flows, and anything else you want the platform to handle without a human in the loop.

  <Tip>
    Duplicate an existing flow before making large changes. You can iterate on the copy, preview it, and then swap it in when ready—without touching the live version.
  </Tip>
</Accordion>

<Accordion title="AI Agents">
  **What it is:** The configuration interface for Fliqr AI's generative AI layer. AI Agents handle open-ended questions that fall outside scripted flow logic.

  **What you'll find here:**

  * Agent creation and naming
  * Knowledge base management: upload documents, paste URLs, or add FAQ entries that the agent draws on when answering questions
  * Model and tone settings (how formal or casual the agent should sound)
  * Handoff rules that define when the agent should escalate to a human or trigger a specific flow
  * Conversation logs showing exactly what the agent said and why

  **When to use it:** Deploy an AI Agent when your users ask questions you can't fully anticipate in advance—product details, policy questions, troubleshooting steps. The agent reads your uploaded knowledge base and formulates answers rather than matching keywords against a decision tree.

  <Note>
    AI Agents and Flows work together. A flow can hand off to an AI Agent mid-conversation, and an AI Agent can trigger a flow when it detects a specific intent (for example, a purchase request).
  </Note>
</Accordion>

<Accordion title="Contacts">
  **What it is:** The built-in CRM that stores every person who has interacted with your bots across any channel.

  **What you'll find here:**

  * A searchable, filterable contact list
  * Individual contact profiles with channel identifiers (phone number, email, social IDs), tags, custom field values, and full conversation history
  * Segment builder for creating dynamic lists based on any combination of fields, tags, or activity
  * Import and export tools for syncing with external systems

  **When to use it:** Review contact data when debugging a flow, build segments for targeted broadcasts, or look up a specific user's history before a human agent takes over a conversation. Contacts accumulate automatically as people interact with your bots—you don't need to import them manually.
</Accordion>

<Accordion title="Pipelines">
  **What it is:** A Kanban-style board for tracking contacts and deals through defined stages—sales funnels, support queues, onboarding checklists, or any other sequential process.

  **What you'll find here:**

  * Customizable pipeline stages (columns on the board)
  * Contact cards that move between stages manually or automatically via flow actions
  * Deal values and notes attached to each card
  * Pipeline-level reporting showing conversion rates between stages

  **When to use it:** Use Pipelines when a conversation needs human follow-up that happens over multiple touchpoints. For example, a lead captured by a flow can be automatically added to a "New Leads" pipeline stage, and a sales rep moves it to "Contacted" and "Qualified" as they work the deal.

  <Tip>
    You can trigger a pipeline stage change directly from a flow block. When a user completes a qualification form, move them to the next stage automatically—no manual work required.
  </Tip>
</Accordion>

<Accordion title="Broadcasts">
  **What it is:** The tool for sending outbound messages to a defined segment of your contact list, either immediately or on a schedule.

  **What you'll find here:**

  * Broadcast composer with channel selector and message editor
  * Audience picker using your saved contact segments or real-time filter criteria
  * Scheduling controls for one-time or recurring sends
  * Per-broadcast delivery and engagement stats (sent, delivered, opened, clicked)

  **When to use it:** Announce a new product, re-engage contacts who haven't started a conversation recently, send appointment reminders, or run promotional campaigns. Each channel has its own message format rules—the composer adapts to show you only the fields available for the selected channel.

  <Warning>
    WhatsApp and SMS broadcasts require pre-approved message templates for users who haven't messaged you in the past 24 hours. See the [Broadcasts documentation](/docs/core-concepts/automation-rules) for channel-specific rules to avoid messages being blocked.
  </Warning>
</Accordion>

<Accordion title="Analytics">
  **What it is:** The reporting layer for all bot activity, flow performance, and channel-level engagement metrics.

  **What you'll find here:**

  * Dashboard overview showing total conversations, active users, and message volume over time
  * Per-flow breakdown: message delivery rate, button click rates, and block-level drop-off
  * Channel comparison view so you can see which channels drive the most engagement
  * AI Agent performance metrics: questions answered, escalation rate, and knowledge base gaps
  * Contact growth over time and segment composition

  **When to use it:** Review Analytics after publishing a new flow to confirm it's performing as expected. Use block-level drop-off data to identify where users abandon a conversation and redesign those steps. Revisit regularly to spot trends—such as a channel that's growing faster than expected—and adjust your strategy accordingly.
</Accordion>

<Accordion title="Settings">
  **What it is:** Workspace-wide configuration for channels, team members, integrations, billing, and account security.

  **What you'll find here:**

  * **Channels:** Connect and configure WhatsApp, Instagram, Messenger, Telegram, SMS, Email, Voice, and website chat
  * **Team:** Invite team members, assign roles (Admin, Agent, Viewer), and manage permissions
  * **Integrations:** Connect third-party tools—Zapier, Make, Google Sheets, Stripe, PayPal, and others
  * **Billing:** View your current plan, usage, and payment history
  * **Security:** Enable two-factor authentication, manage API keys, and review login activity

  **When to use it:** Start here when onboarding a new channel or adding a team member. Return to Integrations when you need to connect Fliqr AI to an external tool as part of a flow.

  <Note>
    Only users with the **Admin** role can access Billing and make changes to channel connections. Agents can manage conversations and flows but cannot change account-level settings.
  </Note>
</Accordion>

## What's next

<CardGroup cols={2}>
  <Card title="Quickstart" icon="bolt" href="/docs/get-started/quickstart">
    Follow the step-by-step guide to build and publish your first flow in under 10 minutes.
  </Card>

  <Card title="Flows" icon="diagram-project" href="/docs/core-concepts/flows">
    Learn how the Flow Builder works in depth—conditions, variables, API calls, and advanced block types.
  </Card>
</CardGroup>
