Choose a professional account name
Use a name that identifies the team, brand, location or purpose because staff see it in account selectors, access control, audit and history.
Exact navigationAdmin Area → WhatsApp → Connections
Before you begin
- Confirm 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 covers
Use a name that identifies the team, brand, location or purpose because staff see it in account selectors, access control, audit and history. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.
Exact step-by-step process
- Open Admin Area → WhatsApp → Connections.
- Locate the control used to choose a professional account name.
- Select or enter only the supported value described below.
- Select the page’s Save, Save settings, Save access control or Save controls action.
- Reload or open the affected Inbox/account and verify the new behaviour.
Fields, choices and supported possibilities
Account namerequired, maximum 191 characters
AvailabilityActive or inactive
Live QRgenerated by the private connector
Delete confirmationexact uppercase DELETE
Code-backed validations and workflow rules
- 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.
- Use a name that identifies the team, brand, location or purpose because staff see it in account selectors, access control, audit and history.
Expected result and verification
- 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.