Verify settings after an upgrade
Follow this guide to open Settings after activation and confirm new r20.5 options have defaults without overwriting deliberate existing values. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → WhatsApp → Settings
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 you’ll accomplish
Open Settings after activation and confirm new r20.5 options have defaults without overwriting deliberate existing values. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.
Follow these steps
- Go to Admin Area → WhatsApp → Settings.
- Select the correct account, conversation, customer, staff member or session before you verify settings after an upgrade.
- Complete the visible fields and confirmation prompts exactly as described below.
- Select the available action once and wait for its success or validation response.
- Check the result in the operational record and, where applicable, in Audit Trail or the linked native CRM record.
Fields and options to review
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
Rules the system enforces
- 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.
- Open Settings after activation and confirm new r20.5 options have defaults without overwriting deliberate existing values.
How to confirm 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.