v2026.8.14
Release date: August 26, 2026
New Features
Filter conversations by customer custom fields
The chat list, attendance report, and quick filters now accept the same customer custom fields you already use in Customers: select, multi-select, date, and date/time.
The queue shows only conversations that match the profile you care about — plan, source, due date — without opening each record.
Full guide: Chat — Conversation filters
What is it for?
- Find conversations by a value on the customer (e.g. plan, source)
- See who still has no value on a field
- Narrow the queue by a date or date/time range
- Reuse the same cut in the report and in team quick filters
How to use?
- In Chats, open the filters panel
- In Custom fields, choose the mode: all, blank, or specific values/period
- Apply — the list and counts follow
- In the report, use the same criteria before exporting
- Admins: Configure quick filters → add the criteria to the team shortcut
What is included
The filter looks at the customer record linked to the conversation. Groups and chats without a customer are left out. Text, number, and yes/no fields do not filter the list yet — but they are available as columns in the report.
Custom field columns in the report
In the attendance report export, the Columns to export list includes all customer custom fields. Check the ones that should appear in the file.
How to use?
- In Chats, open Export report
- On the right, scroll to Custom fields
- Check the fields you want in the file
- Export — each field becomes a column, with the customer value from the conversation
Groups and chats without a customer get an empty cell. Fields start unchecked, so the current report does not change until you pick them.
Bug Fixes
WhatsApp funnel conversion without a registered ad
Moving a customer to a stage with a Meta conversion event used to require a registered ad or pixel in UTM when the origin was WhatsApp (click-to-WhatsApp / CTWA). That is not needed: only the connected official WhatsApp channel and the customer's click identifier (ctwa_clid) are required.
The event now reaches Meta in that case even without a registered ad. Other origins (website, form, account pixel) still need an ad or pixel as before.
Benefits
- Same filter logic already familiar from Customers
- Queue and report stay on the same cut
- Report includes the unique fields of each operation, in the file
- Team shortcuts can store the criteria, without rebuilding the panel every shift
- WhatsApp funnel conversions no longer depend on a registered ad in UTM