
The dashboard: what was sent, what is waiting, and what needs attention.
What OMNI is made of
OMNI is built from modules. Your plan decides which ones your account has.Channels
How messages leave and arrive: SMS, WhatsApp, RCS and Voice. Use
FireFlo’s connection, or connect your own.
Batteries
What else the panel can do: AI Agents, Calendar, Catalogue,
Customer data, Pipelines and Tickets.
OMNI API
One API for every channel: send with failover between channels, manage contacts,
answer conversations and receive signed webhooks.
Where to go next
Get started
The ideas behind OMNI — accounts, plans, roles, modules and consent — and a
first hour with the panel.
Using OMNI
Every everyday screen: the Inbox, Contacts, Broadcasts, the Delivery report,
Billing, Team and more.
Channels
Setting up SMS, WhatsApp, RCS and Voice, and the templates and sender IDs each
one needs.
Batteries
AI Agents, Calendar, Catalogue, Customer data, Pipelines and Tickets.
Developers
Keys and scopes, errors, webhooks, and guides for messages, contacts,
conversations and calls.
API reference
Every endpoint, with a request you can try.
For operators
For those running OMNI for their customers: plans, pricing, channel connections
and resellers.
Questions about your account or the product: write to
support@fireflo.au.