Connect your company’s WhatsApp.

1. 01

   Prepare your Meta account

   Ask your Meta administrator to prepare your business portfolio, WhatsApp Business Account and a registered Cloud API phone number. You need the numeric Phone Number ID, Business Account ID and Meta App ID. These are different from the phone number people dial. A regular WhatsApp account alone does not provide the Cloud API.

2. 02

   Create credentials with the right access

   In Meta, create a system-user access token assigned to the relevant business assets, with whatsapp_business_management and whatsapp_business_messaging permissions. Temporary dashboard tokens can expire quickly. Follow your company’s credential rotation policy and Meta’s current requirements. Your Meta administrator must also provide the app secret from App settings → Basic.

3. 03

   Save the connection in Oklyst

   Sign in as your company owner and open Settings → WhatsApp. Select WhatsApp Cloud and enter the IDs, access token, Meta App ID and app secret. You do not need to make up a verification token: Oklyst creates one itself. Oklyst encrypts these credentials for this company and never displays them again. Blank secret fields keep saved values.

4. 04

   Press “Connect Meta for me”

   In step 3 of Settings, press “Connect Meta for me”. Using only the details you saved, Oklyst points your Meta app’s WhatsApp webhook at your company’s own callback address for the messages field and subscribes the app to your WhatsApp Business Account. Meta checks the callback while this happens. Pressing it again is safe. Meta sends each app’s messages to one address, so give each Oklyst company its own Meta app: Oklyst will not move an app that still delivers another company’s messages.

5. 05

   Check the saved connection

   Choose “Check connection” in Oklyst. This performs read-only Meta requests to check token access, the number’s membership in the Business Account, the app’s subscription and whether Meta sends messages to this company’s callback address. It sends no messages and changes nothing. A successful check does not prove webhook delivery, template approval, messaging permission or that a future token will remain valid.

6. 06

   Prepare templates and your team

   In WhatsApp Manager, create and obtain approval for the notification templates that match your Oklyst settings and language. Add every team member’s full international WhatsApp number under People. Set up the company’s agent and the forms it will work with. The agent needs its own authorized connection and running routine; a WhatsApp connection does not create one.

7. 07

   Enable processing and verify a real message

   When ready, press “Go live” on Getting started, or enable WhatsApp processing in Settings. Ask a registered team member to send a harmless test request to your company’s number, then confirm it arrives in Messages and the intended agent work completes. Inspect delivery issues for any reply failures. Meta may charge for messages; Oklyst’s connection check does not send a test message automatically.

Outside Meta’s customer service window, an ordinary chat reply cannot be used. Oklyst uses the notification templates configured for your company. Names and language must exactly match templates approved in your Business Account; saving a template name in Oklyst does not create or approve it in Meta.

• system_not_ready: the company is not ready to process staff messages. No body parameters.
• reply_waiting: a reply is waiting for the recipient. One body parameter: the company name. A Utility template, for example “There is a reply from {{1}} to your message. Reply here to read it.”
• run_alert: an agent run needs the owner’s attention. One body parameter: the Agent settings URL.

Use the template names shown in Settings if you have customized them. Your Meta administrator should confirm the body parameters match the notification before enabling replies.

“Connect Meta for me” fails

If Oklyst says Meta did not accept the app ID and app secret, copy both again from App settings → Basic and save them. If Meta could not confirm Oklyst’s address, wait a minute and press the button again. If the app could not be subscribed to the Business Account, check that the access token can manage that account. A callback URL is not an access token.

The connection check fails

Check whether the token expired or was revoked, whether both permissions are present, and whether the system user has access to this Business Account and number. Verify the numeric IDs in Meta. Wait 30 seconds before repeating the check.

The check passes but no message appears

If the check says Meta sends messages to another address or not at all, press “Connect Meta for me”. Confirm the number is registered and usable with Cloud API. The sender must be active in People with the correct international number: messages from a number on nobody’s profile are kept but not answered, and People lists those numbers so you can add the person. Check Meta’s webhook delivery diagnostics. A Meta test event alone is not proof that a staff message reaches Oklyst.

Messages arrive but no agent work starts

Enable WhatsApp processing only when your company is ready, then check the agent’s authorization, routine schedule and task status. Receipt reading has a separate setup; receiving an attachment does not prove automatic extraction is active.

The number is connected to another company

A WhatsApp number works in one company at a time. The owner of the company that has it must disconnect it in its WhatsApp settings first; then save the connection here. Message history stays with the company that received it.

A reply is failed or uncertain

Read Delivery issues in WhatsApp settings. Check the recipient, approved template and language. An uncertain send may already have arrived; check with the recipient before trying again to avoid duplicate messages.

Credentials are encrypted and scoped to your company. Only its owner can change them in the signed-in web settings. The company callback checks Meta’s signature and refuses messages for another saved account or number. A phone number can belong to only one Oklyst company connection at a time.

To rotate credentials, replace the values in Settings, press “Connect Meta for me” again and check the connection. Use “Disconnect WhatsApp” in Settings to stop new routing and sends without deleting records. Messages already accepted may still be processed. Revoking the access token in Meta stops Oklyst’s token-based requests; removing the callback/subscription stops incoming delivery.

Changing a connection for a company whose processing is already enabled takes effect immediately. Keep the old credentials available in your password manager until the new connection has been verified.