Restart a connected account

Use Restart to recycle the private connector process while keeping the account configuration and linked-device authentication directory.

What this guide covers

Use Restart to recycle the private connector process while keeping the account configuration and linked-device authentication directory. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.

Exact step-by-step process

1. Open Admin Area → WhatsApp → Connections.
2. Select the correct account, conversation, customer, staff member or session before you restart a connected account.
3. Complete the visible fields and confirmation prompts exactly as described below.
4. Select the available action once and wait for its success or validation response.
5. Verify the result in the operational record and, where applicable, in Audit Trail or the linked native CRM record.

Fields, choices and supported possibilities

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 Restart to recycle the private connector process while keeping the account configuration and linked-device authentication directory.

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.

Related WhatsApp Web Messaging and CRM guides