New Reporting Metric: Chat Widget Uptime & Hourly Available Gap Analysis
Summary of Requirement: We require a report that tracks the availability status of the web chat widget (Visible vs. Hidden) relative to business hours. Specifically, we need to report on the percentage and duration of time the chat option was unavailable/hidden on the customer's website, broken down by hour.
Use Case: The client is a Business Process Outsourcing (BPO) provider whose revenue model is strictly tied to engagement volume.
* Revenue Loss - Every minute the chat widget is hidden (due to capacity limits or staffing gaps) equates to unrecoverable missed revenue.
* The "Black Hole" Effect - Currently, RingCX reports on interactions received. It does not report on the time periods where the widget was effectively "down." During peak seasonal periods (e.g., Christmas), the client suspects high unavailability (potentially >50%) but lacks the data to prove it or pinpoint the exact hours it occurs.
Impact on Customer Experience (CX)
* Sentiment Decline - The client’s demographic demands immediate, live support. When the chat option is hidden during business hours, it creates significant friction and damages brand perception.
* Blind Spots - Without visibility into "unavailability duration," the client cannot quantify the negative impact on CX scores during peak traffic.
Operational & Workforce Management Impact
* WFM Inefficiency - Without knowing when the widget is hiding due to lack of agents, the WFM team cannot optimize schedules. They are effectively staffing based on "answered" volume rather than "true demand."
* Forecasting - They cannot accurately forecast for future peaks because the "lost time" data is missing from historical reports.
Specific Functional Requirement We request a standard report or dashboard widget that visualizes:
1. Hourly Availability Rate: (e.g., 09:00–10:00: Chat Widget Active 40 mins / Inactive 20 mins).
2. Unavailability Percentage: A calculation of (Time Widget Hidden / Total Business Hours) * 100.
It would also be helpful to offer threshold alerts and the ability to flag when unavailability exceeds a certain percentage (e.g., >10% downtime) to trigger immediate staffing adjustments.