Skip to content
Browse templates Get Maxbot
Channels

One conversation, published where it belongs.

Maxbot Core owns the conversation. A channel decides where that conversation runs. The website widget ships with Core; WhatsApp is a separate add-on. More channels are planned, and we will only list one as available when its add-on genuinely is.

Available today

Two channels, one set of flows.

Website widget

Included in Maxbot Core

A floating chat trigger on the pages you choose, carrying your greeting, your agent, your colours and your layout. Controlled by a project, so you can switch it off without losing anything you built.

  • Greeting, colours and layout options
  • Page-level targeting
  • Desktop and mobile
How it works Try a live preview

WhatsApp

Separate add-on · Available

Incoming WhatsApp messages are delivered by Meta's webhook, resolved to a linked WhatsApp project, passed into the assigned Maxbot flow, and answered through the official Cloud API.

  • Official Meta Cloud API, your own credentials
  • Keyword triggers with exact, contains or starts-with matching
  • Approved templates, carousels, delivery logs
Explore the add-on Setup guide
Roadmap

Planned, and not pretending otherwise.

The architecture is built so a new channel can be added without changing what Maxbot Core is. These add-ons are not released yet, so nothing here is on sale and nothing here is included with a current purchase.

Coming soon

Instagram Direct

Bringing the same guided flows to Instagram direct messages, through Meta's messaging platform.

Status: planned · Not available
Coming soon

Messenger

Page conversations answered by a Maxbot flow, using the same projects and captured fields.

Status: planned · Not available
Under consideration

Telegram

Being evaluated as a future add-on for businesses whose audience lives on Telegram.

Status: exploring · Not available
What "coming soon" means here. A channel is listed as available only once its add-on, documentation and supported workflows are finished. Until then it stays on this page as a plan, not a promise attached to a purchase.
Why this structure

The flow outlives the channel.

Because the conversation lives in Core and the channel is only a delivery surface, a support flow you build today keeps working when a new channel arrives. The same captured fields, the same branches, the same project model.

See what Core provides
One flow, two published projects
Topic · Support
What do you need help with?
Order statusQuick reply
ReturnsQuick reply
Something elseQuick reply
Project A
Website widget, all pages except checkout.
Project B
WhatsApp, trigger on support.