150 results found

1. Quality of Service (QoS) Portal for RingCX Calls

   Implementing a Quality of Service (QoS) Portal in RingCX would allow visibility into whether call quality issues originate from the agent’s side or the caller’s side.

   67 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  11 comments  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. View Ring CX Realtime dashboards in minutes and seconds.

   Some supervisors have requested that the Realtime inbound display dashboard shows queue times in minutes and seconds (MM:SS) rather than just seconds to make viewing these at a glance simpler.

   Max Q, Avg Q etc.

   •  

   95 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Implemented  ·  7 comments  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. transfer

   Include Agent Name on Transfer Segment in Interaction Details Report

   Request Summary:
   When an agent initiates a transfer (especially a warm transfer) during an active call, the Interaction Details Report splits the call into two segments under the same UII. However, the second segment (the transfer attempt) does not display the agent name, resulting in incomplete data when filtering by agent in the report. The customer requests that the agent name be captured for all segments of a call—including transfer attempts—to ensure accurate reporting.

   ---

   Current Behavior:
   • The agent's name is shown for the initial (inbound) segment.
   • During a transfer attempt, the second segment is created but shows Agent Name = N/A.
   • As a result, when filtered by agent, the report omits the transfer segment—causing data discrepancies.

   ---

   Expected Behavior:
   • Both the original and the transfer segments of the interaction should capture and display the initiating agent's name.
   • Filtering the Interaction Details Report by agent should include all call segments initiated by that agent, including canceled or completed transfer attempts.

   ---

   Business Impact:
   • The customer relies heavily on the Interaction Details Report to track individual agent activity.
   • Missing agent data on transfer segments leads to inaccurate call metrics, causing confusion and a lack of confidence in reporting.
   • For instance, OB calls made during active IB calls are not tracked properly, resulting in agent performance being under- or over-represented.

   ---

   Use Case Reproduction (as demonstrated by customer):
   1. Agent places outbound call (OB) to their own cell.
   2. While on call, agent clicks Transfer, dials another number, connects, then cancels the transfer.
   3. Interaction Details shows:
   o 2 call segments (same UII),
   o 1st segment: agent name populated,
   o 2nd segment: agent name = N/A.
   4. Filtering by agent omits the 2nd segment entirely.

   ---

   Supporting Evidence:
   • Multiple test scenarios (UIIs included in case notes).
   • Screenshots, spreadsheets, and logs attached to Case 27382978.
   • Customer provided 4-page Excel document showing discrepancies between reports.
   • Customer's updated report (“Updated Agent Activity Report: Daily”) does not fix the issue due to missing agent name in core data.

   ---

   Requested Solution:
   Modify the data model or reporting logic so that agent information is retained and displayed in all segments of an interaction, especially during transfer attempts (warm or cold), regardless of whether the transfer is completed or canceled.

   Include Agent Name on Transfer Segment in Interaction Details Report

   Request Summary:
   When an agent initiates a transfer (especially a warm transfer) during an active call, the Interaction Details Report splits the call into two segments under the same UII. However, the second segment (the transfer attempt) does not display the agent name, resulting in incomplete data when filtering by agent in the report. The customer requests that the agent name be captured for all segments of a call—including transfer attempts—to ensure accurate reporting.

   ---

   Current Behavior:
   • The agent's name is shown for the initial (inbound) segment.
   • During a… more

   • 

   65 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Review  ·  2 comments  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Feature Request: Add Reporting for Abandoned Chats in RingCX

   Feature Request: Add Reporting for Abandoned Chats in RingCX

   Summary:
   Request to introduce a reporting feature in RingCX that captures and displays metrics for abandoned chats — similar to how abandoned calls are tracked in voice queues.

   Details / Description:
   Currently, RingCX does not provide any native reporting or metrics that log abandoned chat interactions, such as when a customer initiates a chat but disconnects before an agent accepts or responds.
   This limits visibility for contact center managers who need to measure missed engagement opportunities and optimize staffing and response strategies.

   Use Case:
   Supervisors and analysts need the ability to identify how many customers abandon chat sessions before they are handled, along with timestamps and queue information.
   This data would help:

   Improve response times by identifying high abandonment periods.

   Enhance customer experience by ensuring sufficient agent coverage.

   Provide parity with existing voice reporting (e.g., abandoned call metrics).

   Requested Enhancement:

   Add “Abandoned Chats” as a metric in chat queue reports and real-time dashboards.

   Include fields such as:

   Queue name

   Timestamp of chat initiation and abandonment

   Time waited before abandonment

   Agent availability at time of event

   Optionally, include in Interaction Detail Reports (IDR) or Queue Summary Reports.

   Business Impact:
   Without this feature, supervisors lack visibility into missed chat interactions, making it difficult to track customer engagement effectiveness or staffing needs.

   Feature Request: Add Reporting for Abandoned Chats in RingCX

   Summary:
   Request to introduce a reporting feature in RingCX that captures and displays metrics for abandoned chats — similar to how abandoned calls are tracked in voice queues.

   Details / Description:
   Currently, RingCX does not provide any native reporting or metrics that log abandoned chat interactions, such as when a customer initiates a chat but disconnects before an agent accepts or responds.
   This limits visibility for contact center managers who need to measure missed engagement opportunities and optimize staffing and response strategies.

   Use Case:
   Supervisors and analysts need the ability to… more

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  2 comments  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. 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.

   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… more

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Ability to see Logged out agents in RingCX Real time Dashboard

   Ability to see Logged out agents in RingCX Real time Dashboard

   Currently in the Real Time Agent Widget, it only shows logged in agents. It would also help if it would show agents who are logged out

   15 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Future Consideration  ·  0 comments  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Wants to see Requeued Calls and Transferred Calls in RingCX Analytics

   Wants to see Requeued Calls and Transferred Calls in RingCX Analytics
   Wants to view the RingCX Analytics page to see the number of requeued or transferred calls when agents use the Requeue or Transfer options. There should be a report available that shows which calls were handled using these options.

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  1 comment  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. RingCX Analytics: Additional Metrics and Elements to Simplify Use and Provide Enhanced Functionality

   There is a significant need for the ability to drill down into historical data and filter digital queue KPIs by channel name and ID. This functionality serves multiple purposes and use cases, with a common scenario being the grouping of channels by site, language, or brand. Without the ability to create a more granular channel breakdown of KPIs, RingCX data analysts and supervisors have limited capabilities when it comes to determining and understanding potential customer service performance issues or identifying areas for improvement across different sites, languages, or brands today. Additionally, providing the associated digital thread ID within Historical Reporting would enable them to review conversations linked to specific interactions where NPS is flagged as poor or interaction handling time is unusually high. Furthermore, including a digital interaction URL would provide valuable functionality for data analysts and supervisors, allowing them to easily access digital conversations directly with minimal effort from the Analytics application.

   To improve existing analytics capabilities and to simplify data analysts and supervisors work, I would like to suggest implementing the following metrics and elements for Historical Reporting and Realtime Dashboards within RingCX Analytics:

   Digital Channel Name - Example: ACME Incorporated WebChat (Channel)

   Digital Channel ID - Example: 66718bdc30e2670007a938fa

   Digital Interaction Thread ID - Example: 6671b7063d443400075b2681

   Digital Interaction URL - Example: https://brgzmzwqdj.digital.ringcentral.com/identities/6671b7063d443400075b267d?thread_id=6671b7063d443400075b2681&view=no-header

   Digital Category Name - Example: WebChat

   Digital Category ID - Example: 66718b8b94c18e000727c35c

   There is a significant need for the ability to drill down into historical data and filter digital queue KPIs by channel name and ID. This functionality serves multiple purposes and use cases, with a common scenario being the grouping of channels by site, language, or brand. Without the ability to create a more granular channel breakdown of KPIs, RingCX data analysts and supervisors have limited capabilities when it comes to determining and understanding potential customer service performance issues or identifying areas for improvement across different sites, languages, or brands today. Additionally, providing the associated digital thread ID within Historical Reporting… more

   •  

   •  

   •  

   31 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Future Consideration  ·  0 comments  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. RCX - Realtime Dashboard Access

   RingCX agents should have the option to view the dashboard to see the other agent's status in the RingCX Agent platform, not in Analytics, regardless if they are just an Agent or an Admin.

   12 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  1 comment  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Ability for Any Admin to Modify, Disable, or Delete RCX Historical Report Schedule Regardless of Ownership

    Currently, a RingCX admin can only modify and delete Historical Report Schedules that they own.

    I would like to suggest a feature enhancement to allow an admin to delete any Historical Report Schedule, regardless of ownership. This is particularly useful for Historical Report Schedules no longer owned by off-boarded admins or users whose admin access has been revoked.

    This capability can also be important if a situation arises where an employee is absent from the business due to unforeseen circumstances and the schedule needs to be modified, disabled, or deleted. Furthermore, if an admin is deleted, the schedule will show as not having an owner.

    There is currently no way to delete this or reports not owned without engaging RingCentral's support team.

    Currently, a RingCX admin can only modify and delete Historical Report Schedules that they own.

    I would like to suggest a feature enhancement to allow an admin to delete any Historical Report Schedule, regardless of ownership. This is particularly useful for Historical Report Schedules no longer owned by off-boarded admins or users whose admin access has been revoked.

    This capability can also be important if a situation arises where an employee is absent from the business due to unforeseen circumstances and the schedule needs to be modified, disabled, or deleted. Furthermore, if an admin is deleted, the schedule will show… more

    •  

    •  

    •  

    25 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Feature Request – Distinct “Invalid Number” Result for Manual Outbound Calls

    Description:

    Currently, in RingCX historical reports, manual outbound calls to invalid numbers are recorded as “No Answer” in the Call Results column. This makes it impossible to differentiate between genuine no-answer calls and invalid-number attempts in reporting.

    Business Impact:

    Agents and managers cannot accurately track list quality or outbound performance.

    Invalid numbers are not flagged for clean-up, reducing operational efficiency.

    Reporting and analytics on manual outbound campaigns are incomplete.

    Requested Feature:

    Introduce a distinct call result/disposition such as “Invalid Number” for manual outbound calls.

    Ensure this result is visible in historical reports, dashboards, and exported data.

    (Optional) Include this disposition in APIs and automated reporting tools for better integration.

    Priority: Medium–High (impacts reporting accuracy and outbound efficiency)

    Accurate invalid-number tracking is critical for list hygiene and performance measurement.

    Description:

    Currently, in RingCX historical reports, manual outbound calls to invalid numbers are recorded as “No Answer” in the Call Results column. This makes it impossible to differentiate between genuine no-answer calls and invalid-number attempts in reporting.

    Business Impact:

    Agents and managers cannot accurately track list quality or outbound performance.

    Invalid numbers are not flagged for clean-up, reducing operational efficiency.

    Reporting and analytics on manual outbound campaigns are incomplete.

    Requested Feature:

    Introduce a distinct call result/disposition such as “Invalid Number” for manual outbound calls.

    Ensure this result is visible in historical reports, dashboards, and exported data.

    (Optional) Include this disposition… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  1 comment  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Allow Hiding Metrics on a Historical Report

    Ability to hide a metric on a report. For example, I use 2 metrics to calculate a custom metric, but I don't want those visible on the finished report.

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  1 comment  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Improve Historical Reporting: Exclude Deleted Agents and Queues past their deletion date

    When an agent or queue is deleted, the historical data associated with them should ideally no longer be displayed or should be clearly marked as inactive past their deletion date.

    If multiple agents are leaving and are removed from RingCX, manually filtering them out from historical dashboards is indeed very difficult and inefficient.

    Hence, the agent and queue details should be cleared off after the date they are deleted from the portal

    12 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Interaction Search

    Interaction Search feature like on CXOne. Instead of pulling up a report and manually look for the interaction.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Omnidirectional Allow RingCentral App Channels

    We would like the "Allow RingCentral App Channels" setting to sync both ways. It has been described as Unidirectional. Currently on a RCX Call, we could still get a direct call to our office line. We would like presence to sync both ways so that our agents don't get another call while on a CC call.

    15 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  1 comment  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. RingCX - Option not to count outbound queue calls within inbound reporting stats

    Currently, if an agent has an inbound queue assigned to them in the 'manual outbound default queue assignment' field, then manual outbound calls made by that agent are counted in analytics as inbound calls against that inbound call queue.

    This causes some confusion in reporting and skews stats related to inbound calls to the given call queue.

    Customers would like an option to differentiate between inbound and outbound calls associated with an inbound queue, or at least manual outbound calls associated with an inbound queue should not be counted on inbound reports & dashboards.

    30 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Implemented  ·  3 comments  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. View RingCX Dashboards in Softphone-Client

    It should be possible to display the created dashboards from Analytics directly in the client, preferably via an additional selection, so that the website does not have to be open in parallel for the display.

    •  

    10 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Forced logout or manual logout reporting

    To have a report on whether an agent was forced to log out by a supervisor or system log out due to a network issue, or manually log out on their own.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Identify percentage of RingCX calls that are recorded

    Need a way to query data to identify what % of calls are recorded.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Dashboard Sharing

    Please add the option to edit a real-time dashboard for all users it's shared with, and a way to view whom a dashboard has been shared with. This would greatly improve the experience for admins and make it easier for them to create and share dashboards with supervisors.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating