Skip to main content

​
Available today

WhatsApp

Meta Cloud API. Text, images, documents, reply buttons, lists, CTA links, location, contacts, templates.

Website widget

An embeddable panel. Renders structured blocks — cards, lists, options, checklists — rather than plain text.
Phone (voice) exists for outbound campaigns. Instagram is not implemented: it appears in configuration but has no inbound or outbound path.

​
What this means for your tools

Your tools are channel-agnostic — the same tool is called on every channel and returns the same result. The platform decides how the reply is rendered.
Do not return channel-specific formatting. WhatsApp has no Markdown links, a strict 1,024-character interactive body, and at most one interactive element per message. Return facts; let the platform compose.

​
Delivery rules you inherit

Outside it, WhatsApp permits only approved templates. The platform checks before generating a reply — so a tool may be called in a conversation whose answer is then delivered late, or as a template.
Three quick messages become one turn, not three. Your tool sees the combined intent.
A person replying from the WhatsApp Business app switches the session to human control and the assistant stops. Tools are not called while a human holds the thread.

​
Media

Voice notes are transcribed before the turn. Images are not interpreted — there is no vision path, so a photo arrives as a note asking the customer to describe what they need.
If your product can identify something from a photo, that is a strong case for a tool. Talk to us: it needs a media path on the platform side as well.