The WhatsApp channel connects one WhatsApp number to one agent through Meta’s WhatsApp Business Platform (Cloud API). Kylo calls Meta’s Graph API on behalf of your WhatsApp business account, and Meta calls Kylo’s webhook when a customer writes or a message status changes.

Connect

You connect from Channels with the Connect WhatsApp dialog. It has two tabs, Facebook login and Access token. Facebook login runs Meta’s Embedded Signup. Access token stores values you supply. The comparison is in Choose a connection method.

What Kylo stores for a connection

Connection states

The WhatsApp card on Channels shows Manage whenever Kylo holds a connection, including a disconnected one. Read the real state on the Connection tab. See Manage the WhatsApp connection.

Inbound messages

Meta posts each event to Kylo’s webhook. Kylo checks the request signature, drops events that are not WhatsApp business account events, and answers Meta quickly before it does the work. Rapid consecutive messages from one contact are coalesced into one agent turn, so a customer who sends three quick texts gets one considered reply. Replies are split into a few short bubbles. Kylo deduplicates on Meta’s message id, so a redelivered webhook does not produce a second reply. Message bodies are stored encrypted. See Conversation privacy.

Outbound messages

A business can message a customer first only with an approved template, and free-form replies are allowed inside Meta’s 24-hour customer service window. Kylo’s outbound send uses templates. See Templates and How a send works.

Manage the connection

The Connection and Templates tabs, disconnect, and reconnect.

Token lifecycle

What expires, what Kylo refreshes, and what to do when it fails.