Conversation status, assignment, priority and tags

Close a conversation

Choose Closed and save controls after the operational issue is complete.

Audience: Inbox supervisors and authorised staffPermission: Per-account ManageModule v1.0.0 · 2026.07.30-r20.5

Exact navigationAdmin Area → WhatsApp → Inbox → Open conversation

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

Choose Closed and save controls after the operational issue is complete. 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 → Open conversation.
Select the correct account, conversation, customer, staff member or session before you close a conversation.
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

StatusOpen, Pending, Closed

Assigned staffUnassigned or staff with account View access

PriorityLow, Normal, High, Urgent

Tagscomma-separated, unique, maximum 20; each maximum 40 characters

Code-backed validations and workflow rules

Conversation controls are saved only for an account the user can manage.
A new live inbound message can reopen a closed conversation only when Reopen on inbound is enabled; history import never reopens it.
Assigned staff choices are restricted to users who can view the account.
Choose Closed and save controls after the operational issue is complete.

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.