Confirm the connected state
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Verify the connection card shows the linked device as ready and that recent conversations become available in Inbox.
Where to goAdmin Area → WhatsApp → Connections
Before you start
- Verify the module is active and select the intended WhatsApp account before changing any operational record.
- Use an account with the stated native CRM capability and per-account access.
- Test with controlled customer/contact data before relying on live verification, email or CRM automation.
What this guide helps you do
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
- Go to Admin Area → WhatsApp → Connections.
- Select the relevant record or setting.
- Follow the supported controls described below.
- Save or confirm once.
- Check the result.
Fields and options
Account namerequired, maximum 191 characters
AvailabilityActive or inactive
Live QRgenerated by the private connector
Delete confirmationexact uppercase DELETE
Rules and limits
- 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.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.
