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

# FireFlo OMNI

> What FireFlo OMNI is: one inbox, one set of contacts and one API for SMS, WhatsApp, RCS and Voice.

FireFlo OMNI is where a business talks to its customers. Every message, on every
channel, lands in **one Inbox**. Every person is **one contact**, whichever channel
they wrote on. And everything the panel does, your own systems can do through **one
API**.

<Frame caption="The dashboard: what was sent, what is waiting, and what needs attention.">
  <img src="https://mintcdn.com/fire-flo-omno/qMiP0VYTVwEeCAoo/images/using/dashboard.png?fit=max&auto=format&n=qMiP0VYTVwEeCAoo&q=85&s=eda03ade4e72e16e8576ea5df4fe6842" alt="The OMNI dashboard with message totals, replies waiting and channel cards" width="1440" height="900" data-path="images/using/dashboard.png" />
</Frame>

## What OMNI is made of

OMNI is built from modules. Your plan decides which ones your account has.

<CardGroup cols={3}>
  <Card title="Channels" icon="tower-broadcast" href="/channels/overview">
    How messages leave and arrive: **SMS**, **WhatsApp**, **RCS** and **Voice**. Use
    FireFlo's connection, or connect your own.
  </Card>

  <Card title="Batteries" icon="battery-full" href="/batteries/overview">
    What else the panel can do: **AI Agents**, **Calendar**, **Catalogue**,
    **Customer data**, **Pipelines** and **Tickets**.
  </Card>

  <Card title="OMNI API" icon="code" href="/developers/overview">
    One API for every channel: send with failover between channels, manage contacts,
    answer conversations and receive signed webhooks.
  </Card>
</CardGroup>

Whatever modules you have, a few things are always there: the **Inbox**,
**Contacts**, **Broadcasts**, the **Delivery report**, **Downloads**, **Billing** and
your **Team**.

## Where to go next

<CardGroup cols={2}>
  <Card title="Get started" icon="flag" href="/get-started/concepts">
    The ideas behind OMNI — accounts, plans, roles, modules and consent — and a
    first hour with the panel.
  </Card>

  <Card title="Using OMNI" icon="window-maximize" href="/using/finding-your-way">
    Every everyday screen: the Inbox, Contacts, Broadcasts, the Delivery report,
    Billing, Team and more.
  </Card>

  <Card title="Channels" icon="message" href="/channels/overview">
    Setting up SMS, WhatsApp, RCS and Voice, and the templates and sender IDs each
    one needs.
  </Card>

  <Card title="Batteries" icon="plug" href="/batteries/overview">
    AI Agents, Calendar, Catalogue, Customer data, Pipelines and Tickets.
  </Card>

  <Card title="Developers" icon="terminal" href="/developers/overview">
    Keys and scopes, errors, webhooks, and guides for messages, contacts,
    conversations and calls.
  </Card>

  <Card title="API reference" icon="book" href="/api-reference/overview">
    Every endpoint, with a request you can try.
  </Card>

  <Card title="For operators" icon="building" href="/operators/overview">
    For those running OMNI for their customers: plans, pricing, channel connections
    and resellers.
  </Card>
</CardGroup>

<Note>
  Questions about your account or the product: write to
  [support@fireflo.au](mailto:support@fireflo.au).
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.