Search conversations
Enter part of the display name, telephone number or latest-message preview to find matching conversations.
Exact navigationAdmin Area → WhatsApp → Inbox
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
Enter part of the display name, telephone number or latest-message preview to find matching conversations. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.
Exact step-by-step process
- Open Admin Area → WhatsApp → Inbox.
- Select the relevant record or setting.
- Follow the supported controls described below.
- Save or confirm once.
- Verify the result.
Fields, choices and supported possibilities
Account selectorAccount selector
Conversation searchConversation search
StatusAll, Open, Pending, Closed
Unread onlyUnread only
Synchronise nowSynchronise now
Code-backed validations and workflow rules
- The browser retains the last accessible selected account in staff-scoped storage and in the Inbox URL.
- Late responses from a previously selected account cannot overwrite the current account view.
- Bootstrap returns a bounded conversation set and the model enforces an upper limit.
- Enter part of the display name, telephone number or latest-message preview to find matching conversations.
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.