Create a WhatsApp account
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Enter a clear account name, choose whether it is active, save it and allow Pixie CRM to prepare its private linked-device runtime.
- 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
Enter a clear account name, choose whether it is active, save it and allow Pixie CRM to prepare its private linked-device runtime. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.
Follow these steps
- Go to Admin Area → WhatsApp → Connections.
- In Add WhatsApp account, enter a name such as Customer Support WhatsApp.
- Keep Active selected if the account should be available immediately.
- Select Create WhatsApp account.
- Wait for Automatic connection preparation to reach the QR stage.
Fields and options
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.
- Enter a clear account name, choose whether it is active, save it and allow Pixie CRM to prepare its private linked-device runtime.
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.
