Mark an unread conversation as read

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Follow this guide to open the conversation and allow Pixie CRM to call WhatsApp sendSeen before setting the CRM unread count to zero.

What this guide helps you do

Open the conversation and allow Pixie CRM to call WhatsApp sendSeen before setting the CRM unread count to zero. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.

Follow these steps

1. Go to Admin Area → WhatsApp → Inbox → Open conversation.
2. Select the correct account, conversation, customer, staff member or session before you mark an unread conversation as read.
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. Check the result in the operational record and, where applicable, in Audit Trail or the linked native CRM record.

Fields and options

Rules and limits

• A send request requires reply permission and either non-empty text or one accepted attachment.
• The server validates MIME type using file content and stores a randomised filename in the protected upload area.
• Opening an unread conversation asks the linked device to send a real read acknowledgement before clearing CRM unread state.
• Open the conversation and allow Pixie CRM to call WhatsApp sendSeen before setting the CRM unread count to zero.

Check 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.

Related guides