Feature Request: Built-in Comprehensive Debugging Functionality for Zendesk Products

Problem Statement: Our agents are experiencing intermittent issues with accepting calls in Zendesk Talk, where the call interface hangs on the "accepting" state and eventually fails, marking the call as missed. This sporadic issue is challenging to diagnose as it requires agents to generate HAR files and perform extensive troubleshooting steps, which is impractical given their primary responsibilities. The current process places the burden of investigation on our agents, which is not customer-centric and leads to inefficiencies and frustration.

Description: We request the development of a built-in comprehensive debugging functionality within Zendesk products (Support, Talk, Guide, etc.) that allows for enhanced logging and diagnostics for specific users, products, modules, and services. This feature should enable administrators to activate a debugging mode that captures detailed logs and diagnostic information without requiring agents to perform manual troubleshooting steps.

Requested Features:

1. Enhanced Logging and Diagnostics:
   • Enable a debugging mode that administrators can activate for specific users, products, modules, and services.
   • Capture detailed logs, including network requests, browser console errors, and system performance metrics.
2. Automated Data Collection:
   • Automatically collect and store diagnostic data when issues occur, reducing the need for agents to manually generate HAR files or perform other troubleshooting steps.
   • Provide a centralised location within the Zendesk Admin UI to access and review collected diagnostic data.
3. Real-time Monitoring and Alerts:
   • Implement real-time monitoring of system performance and user interactions.
   • Send alerts to administrators when anomalies or errors are detected, allowing for proactive issue resolution.
4. Integration with Existing Tools:
   • Integrate with existing Zendesk tools and third-party monitoring solutions to provide a seamless debugging experience.
   • Allow for easy export of diagnostic data for further analysis by technical teams.

What We Have Tried So Far:

• Manual Troubleshooting: Agents have been instructed to generate HAR files and perform ping tests when issues occur. However, this approach is impractical due to the sporadic nature of the issue and the additional burden it places on agents.
• Shared Documentation: We have attempted to use shared documents to track and diagnose issues, but this method is inefficient and does not provide the necessary level of detail for effective troubleshooting.

Benefits:

• Improved efficiency and reduced burden on agents by automating the collection of diagnostic data.
• Enhanced visibility into system performance and user interactions, allowing for quicker identification and resolution of issues.
• A more customer-centric approach to troubleshooting, reducing frustration and improving overall satisfaction.