Settings, operating limits and Inbox behaviour

Disable reopening on inbound messages

Clear the toggle to keep closed conversations closed until staff changes them.

Audience: CRM administratorsPermission: AdministratorModule v1.0.0 · 2026.07.30-r20.5

Exact navigationAdmin Area → WhatsApp → Settings

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

Clear the toggle to keep closed conversations closed until staff changes them. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.

Exact step-by-step process

Open Admin Area → WhatsApp → Settings.
Locate the control used to disable reopening on inbound messages.
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

Maximum attachment size1–32 MB

Inbox refresh interval4–60 seconds

Default history chats1–500

Messages per chat1–200

Verification attempts1–10

Six general toggles and eight automation togglesSix general toggles and eight automation toggles

Code-backed validations and workflow rules

Numeric settings are clamped to the displayed minimum and maximum ranges.
Changes take effect immediately; connection limits are applied during preparation or repair without removing the linked session.
Message templates are limited to 4,000 characters.
Clear the toggle to keep closed conversations closed until staff changes them.

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.