Skip to main content
OMNI is built from modules:
  • Channels carry messages and calls: SMS, WhatsApp, RCS and Voice.
  • Batteries add what the panel can do beyond messaging: AI Agents, Calendar, Catalogue, Customer data, Pipelines and Tickets.
  • Pluggable modules sit in front of everything else. The OMNI API is one. They are optional: without them, every channel and battery works as before.
Platform → Modules shows which of these your deployment carries, at what version, and how many accounts use each. It is the page to open when something seems to be missing.
The Modules page, with version and health figures at the top and sections for channels, batteries and modules.

Platform → Modules: what this deployment carries, at what version, and who uses it.

​
How a module reaches a customer

Three things must all be true:
  1. The deployment carries it. A module this deployment doesn’t load has no pages and no menu entries for anyone, whatever their plan says.
  2. It isn’t switched off for everyone on this page (or, for a channel, under Channels).
  3. The customer’s product includes it, or you’ve given it to them with an override. A channel also needs a connection, shared or their own.
A module with no plan feature is on for everyone it reaches.

​
Turning a module on for customers

This page doesn’t decide who has a module. That is set in two places:
  • For a product: Products. Every customer on it gets the module.
  • For one customer: the Modules tab on their page.

​
Reading the page

The figures at the top show the core and panel versions, how many modules are loaded out of those installed, and Health: Clear, or the number of issues to look at. Each issue is spelled out above the list: Each module’s row shows its badges (Not loaded, Version mismatch, Off for everyone), what it depends on, its version, and how many accounts use it. For a channel, that’s accounts that have it configured. For anything else, it’s accounts whose plan includes it.

​
Switching a module off for everyone

1

Open the module

Select Manage on its row.
2

Switch it off

Under For every account, select Switch off for everyone. The page tells you how many accounts have it.
Switching off is immediate and reversible. The module disappears from every account’s menus and pages, and nothing is deleted. Select Switch back on to restore it. For a channel, this is the same switch as under Channels, and its open broadcasts are cancelled.
Switching off stops a module reaching anyone, but the deployment still loads it. To stop carrying a module altogether, contact support@fireflo.au.

​
Backing up and deleting a module’s data

The Its data section of Manage shows how many rows the module holds, and in how many tables. Back up downloads all of it to you as one file. The page checks that what you received matches what was sent, and says so. Nothing is kept on the server. The file you download is the only copy. Deleting a module’s data is permanent. The page refuses until every reason not to has been dealt with, and lists them all:
  • the module is still switched on;
  • some accounts still have it;
  • another module still depends on its data, and has to be emptied first;
  • no backup has been taken, the last one was never confirmed as received in full, or the last one has already been used for a delete.
When nothing stands in the way, type the module’s key to confirm and select Delete this data.
This empties every table the module holds and can’t be undone. Keep your backup somewhere you trust before you delete.