Kylo connects one WhatsApp number to one agent. The Connect WhatsApp dialog offers two methods on two tabs, Facebook login and Access token. They store the same connection, but they differ in who does the Meta setup, what Kylo does for you afterwards, and what you maintain.

​
Compare the methods

Choose Facebook login unless you have a specific reason not to. It is the only method where Kylo registers the number, subscribes the webhook, and keeps the token alive.

​
Decide in three questions

  1. Is the number already registered for the Cloud API under another app or provider? Meta reports a number that another API client uses as unavailable (errors 131051 and 131060). Release it there before you connect, or use the Access token method with the token of the app that already holds it. See Connect errors.
  2. Do you hold a System User token that does not expire? Meta documents System User tokens as the long-lived choice for a direct developer. A user token from the App Dashboard API setup panel expires within hours, so do not use one. See Meta: access tokens.
  3. Do you need inbound replies? Inbound messages reach Kylo through Meta’s webhook. Facebook login subscribes it for you. With an access token the connection can send, but inbound events reach Kylo only if your WhatsApp account is already subscribed to Kylo’s Meta app, which Kylo does not do for you.

Connect with Facebook login

Run Meta Embedded Signup from Kylo.

Connect with an access token

Paste a token, a phone number id, and an account id.