Confirm the connected state

Verify the connection card shows the linked device as ready and that recent conversations become available in Inbox. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

What you’ll accomplish

Verify the connection card shows the linked device as ready and that recent conversations become available in Inbox. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.

Follow these steps

1. Go to Admin Area → WhatsApp → Connections.
2. Select the relevant record or setting.
3. Follow the supported controls described below.
4. Save or confirm once.
5. Check the result.

Fields and options to review

Rules the system enforces

• Each account receives a unique account key, encrypted connector token, loopback connector endpoint and isolated session directory.
• The account creator is granted View, Reply, Convert and Manage for the new account.
• Account deletion is a soft operational deletion after successful isolated runtime removal; messages, verification evidence, portal history and audit remain.
• Verify the connection card shows the linked device as ready and that recent conversations become available in Inbox.

How to confirm it worked

• The requested action completes without a permission, validation, connector or native CRM error.
• The selected account or conversation shows the expected state without changing another account’s data.
• Where the action creates evidence, confirm the message, native record, verification event, portal history or audit entry is present.

Security, privacy and troubleshooting checks

• Never expose connector tokens, loopback ports, authentication directories or raw customer verification replies.
• Use the supported Connections, Access Control, Settings and Audit Trail pages rather than editing runtime or database records directly.
• If the expected control is missing, verify both native capability and per-account permission before treating it as an installation fault.

Continue with related guidance