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

# Batteries

> What a battery is, the six batteries OMNI offers, and which channels each one works with.

A **battery** is an optional add-on to FireFlo OMNI. The channels — SMS, WhatsApp, RCS and
Voice — work on their own. A battery adds to them: AI agents that answer customers, a
shared calendar, a product catalogue, and so on.

A battery is turned on by your **plan**. When your plan includes it, its screens appear in
the panel and its features join the channels you already have. When your plan does not
include it, OMNI behaves exactly as if the battery were not there — nothing half-works,
and nothing changes in how your channels behave.

<Note>
  To see what your plan includes, open **Settings → Plan**. To add a battery, ask your
  account owner, your reseller or FireFlo at [support@fireflo.au](mailto:support@fireflo.au). See
  [Plan and modules](/using/plan-and-modules).
</Note>

## The six batteries

<CardGroup cols={2}>
  <Card title="AI Agents" icon="robot" href="/batteries/ai-agents">
    Sales and support agents on your own AI key. They plan, ask for approval where you
    say so, reply on WhatsApp and SMS, and step back when a person takes over. Includes
    [Knowledge](/batteries/knowledge).
  </Card>

  <Card title="Calendar" icon="calendar" href="/batteries/calendar">
    A shared calendar, booking types, team hours and time off, reminders on WhatsApp and
    SMS, and an online booking page.
  </Card>

  <Card title="Catalogue" icon="box" href="/batteries/catalogue">
    Products with prices, stock and pictures, sets, sync to your WhatsApp catalogue,
    product messages and orders.
  </Card>

  <Card title="Customer data" icon="users" href="/batteries/customer-data">
    Audiences, traits, duplicates and merging, consent per channel, the preference page and
    events from your website and server.
  </Card>

  <Card title="Pipelines" icon="chart-kanban" href="/batteries/pipelines">
    Pipelines and deals on a board or a list, a page for each deal, stages and a record of
    every change.
  </Card>

  <Card title="Tickets" icon="ticket" href="/batteries/tickets">
    Each Inbox conversation split into tickets — one per problem — with status, priority,
    categories and settings.
  </Card>
</CardGroup>

On the plan, some batteries carry a different name:

| Battery | Shown in the plan as |
| - | - |
| AI Agents | AI agents |
| Calendar | Appointments |
| Catalogue | Catalogue |
| Customer data | Customer data |
| Pipelines | CRM |
| Tickets | Tickets |

## Which channels each battery works with

A battery uses only the channels your account has set up. This table shows what each
battery adds on each channel today.

| Battery | SMS | WhatsApp | RCS | Voice |
| - | - | - | - | - |
| **AI Agents** | Agents reply by SMS using your DLT templates; ask for a new template when none fits; workflows; reminder stories; questions about a broadcast | Agents reply in free text inside the 24-hour window and with approved templates outside it; ask for new templates; workflows with reply buttons; reminder stories; questions about a broadcast | Questions about a broadcast. Agents do not reply on RCS, because RCS carries approved templates rather than typed text | — |
| **Calendar** | Reminders and confirmations; the online booking code | Reminders and confirmations with Confirm, Reschedule and Cancel buttons; a list of free times to tap; the online booking code | — | — |
| **Catalogue** | Products as names and prices with a link to your public catalogue page; a catalogue link in broadcasts | Products pushed to your WhatsApp catalogue; product cards and lists customers can order from; carts become orders | Products as names and prices with a link to your public catalogue page | — |
| **Customer data** | Consent per channel; opt-in for marketing; your own stop and start words; the preference page; audiences; traits | Consent per channel; opt-in for marketing; your own stop and start words; the preference page; audiences; traits | Consent per channel; opt-in for marketing; your own stop and start words; the preference page; audiences; traits | Voice appears in consent and on the preference page, so someone can stop calls without stopping messages |
| **Pipelines** | Messages on a deal's timeline; a contact's deals beside their thread | Messages on a deal's timeline; a contact's deals beside their thread | Messages on a deal's timeline; a contact's deals beside their thread | — |
| **Tickets** | A conversation becomes tickets | A conversation becomes tickets | A conversation becomes tickets | — |

<Tip>
  Without Customer data, a STOP reply stops every channel at once. With it, someone can stop
  marketing on one channel and keep the rest. See [Customer data](/batteries/customer-data).
</Tip>

## Batteries work together

Each battery stands on its own, and adds a little more when others are on too:

* With **AI Agents**, Calendar, Catalogue and Tickets each give agents new actions and new
  workflow blocks — booking appointments, pitching products, setting a ticket's status.
* With **Pipelines**, an order from a WhatsApp cart can open a deal.
* With **Tickets**, an agent's hand-over leaves a summary on the ticket, and solved tickets
  suggest new FAQs for [Knowledge](/batteries/knowledge).
* With **Customer data**, an audience can be the recipients of a broadcast or start an
  agent's workflow.

## Who may use a battery

Each battery has its own permissions, given to roles on the **Roles** screen under
**Settings → Team**. The roles
OMNI starts with get sensible defaults, described on each battery's page; an Owner or
Admin can change them. See [Team and roles](/using/team-and-roles).


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