What views can filter
Views can filter tickets by:- status
- assignee
- AI Agent (current assignment, history, and last handler)
- channel
- tags
- priority
- sentiment
- custom ticket fields
- created or updated time
- combined AND/OR filter groups
Watch AI Agents in production
The AI Agent filter uses one field and changes meaning with the condition:
When an AI Agent finishes a run, Chatarmin CX usually clears the live assignment. Use
was assigned or is last to find tickets after the slot was released. Use is only for tickets the agent is actively working or paused on.
Create a view such as “Returns agent — last handled, still open” to review production behavior without waiting for live assignment.
See also Activate an AI Agent and Run on existing tickets.
Inbox structure
Pick a base pattern that matches how your team works, then keep status somewhere in every operational view.
Always keep status in the mix. A topic split without status usually becomes unreadable.
Do not build inbox structure for analytics alone. Use tags and the dashboard for reporting. Keep the inbox lean so tickets do not hide in unused folders.
Build reliable views
1
Start with the owner
Decide who should use the view: a team, brand, language, channel, or process.
2
Choose the most stable filters
Prefer filters that stay true for the life of the ticket, such as channel, tag, team, or ticket field.
3
Keep the status explicit
Most operational views should include
Open and On hold, then exclude Resolved and Closed.4
Save and test
Open a few known tickets and confirm they appear or disappear as expected.
Missing ticket checklist
If a ticket is missing from a view, check:- whether the ticket status matches the view
- whether the channel is included
- whether the required tag or ticket field is set
- whether an AND filter group is too restrictive
- whether a subview overwrote the parent filters