The platform
Connect a channel once. Four capabilities read the same workspace.
The inbox, the AI, the workflow engine and the Ad Runner are not four products sharing a login. They run against one tenant, one connection layer and one permission check, which is why a conversation can trigger a workflow and a campaign can be read next to what it produced.
The loop the product is organised around. Every capability belongs to one of these four stages.
- 01
Connect
Channels and platforms
Instagram, Facebook Pages, Messenger and WhatsApp connect through OAuth and start delivering into one inbox. Ad accounts connect the same way.
- 02
Automate
Rules and workflows
Triggers, conditions and actions run off the webhook path. A workflow that fails can never delay or drop the message that fired it.
- 03
Operate
Teams and conversations
Assign a thread, tag it, filter by branch, hand it to a colleague. Every conversation has an owner and a history the whole team can see.
- 04
Grow
Campaigns and insight
Build one campaign for three ad networks, publish it paused, and read what it produced next to the conversations it generated.
Capabilities
The four capabilities
What each one does, and the state it is genuinely in today.
Underneath
One connection layer, not four integrations
A connected channel is a row in your workspace, not a setting inside a feature. Nothing is authorised twice, and revoking it revokes it everywhere.
Outbound webhooks
AvailableAny workflow can POST to a URL you own — Slack, Zapier, or your own ERP. HTTP and HTTPS only; internal addresses are refused.
Google Sign-In and passkeys
AvailableSign in with Google, a one-time email code, or a passkey. No password is stored for new accounts.
Cloudinary
AvailableMedia uploads go from the browser straight to your own Cloudinary account, never through our servers.
Public REST API
In developmentThe same API the product runs on, documented and opened to your own systems.