Load older customer-profile messages
Use the before-message parameter to page backwards.
Exact navigationClient Area → WhatsApp History
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 the before-message parameter to page backwards. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.
Exact step-by-step process
- Open Client Area → WhatsApp History.
- Select the correct account, conversation, customer, staff member or session before you load older customer-profile messages.
- Complete the visible fields and confirmation prompts exactly as described below.
- Select the available action once and wait for its success or validation response.
- Verify the result in the operational record and, where applicable, in Audit Trail or the linked native CRM record.
Fields, choices and supported possibilities
Portal conversation listPortal conversation list
Selected conversation IDSelected conversation ID
Before-message ID for older messagesBefore-message ID for older messages
Protected media downloadProtected media download
Code-backed validations and workflow rules
- Portal history is contact-owned and includes only conversations verified to the signed-in contact.
- The administrator customer tab appears only when the customer has verified conversations visible through the staff member’s accessible accounts.
- Media downloads are routed through authorised controllers and recorded in the session/audit evidence.
- Use the before-message parameter to page backwards.
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.