Plan requirement
| Subscription | Suite Professional or higher |
| Access | Admin |
Yes, with the condition Ticket > Channel | Is | Side conversation. That matches tickets created from a side conversation, which is not the same as tickets that have one open, and the difference decides what you can build.
How do I see all my side conversations in one list?
A list of side conversation child tickets, which you can narrow like any other view: unassigned, open, on-hold, not updated for several days. Because they are ordinary tickets, everything you already know about views and reporting applies to them.
That is the practical route to "who have we asked something and heard nothing back from". Use child tickets for the work you need to track, and the view builds itself out of conditions you already use.
What you cannot build
A view of tickets carrying an open or unanswered side conversation. Zendesk documents no condition for the state of a side conversation inside a ticket, so a plain side conversation with no reply leaves no trace a view can filter on.
Two things cover that gap instead. A trigger that sets the ticket back to open when a side conversation is replied to handles the case where somebody does answer. And Explore reports on tickets with side conversations, which tells you how long they typically take and which suppliers or departments are slow.
Neither catches silence on the day it starts, which is the honest limit. If a request has to be chased, make it a child ticket rather than a side conversation, and it becomes visible to every tool you already have.
Comments
0 comments
Article is closed for comments.