Recent searches
No recent searches
Centralized log collection for a ticket
Posted Feb 12, 2025
This feature request is about log collection in Zendesk.
The current way of collecting logs is not scalable in a Zendesk ticket. While support engineers request for logs from customers e.g. code files, screenshots, videos, console/browser logs, the files are sent as an attachment. When the ticket history is long, the process is difficult for the engineers to view the logs at one single place. Sometime, the attachment is blocked and not viewable by the support engineer and the engineers have to request for the logs again. The process becomes more complex when the ticket gets passes among different support engineers.
My proposal is to have a single shared space for the logs exchanged between customer and support engineer per ticket. This makes log references easier for all the engineers who work on the ticket.
The log space can be located within the Customer Context App (as shared in the attachment). Looking forward to a solution soon, thanks!

- Preethi Paramasivam.
2
4 comments
Scott Tynan
To get around this challenge we installed the free attachment manager app so that we could open the app to see all attachments for the ticket.
0
Shawna James
Thank you for taking the time to provide us with your feedback. This has been logged for our PM team to review. For others who may be interested in this feature request, please add your support by upvoting this post and/or adding your use case to the comments below. Thank you again!
1
Preethi Paramasivam
Thank you Shawna James Looking forward to the response from Zendesk PM team!
Fyi: My colleagues and friends aren't able to view this post. They have been denied access. Please refer to the screenshot. Could you help me understand why is it happening & how everyone can view so they can upvote? Thanks in advance!
0
Preethi Paramasivam
Shawna James any update from PM on this feature request?
0