1330 results found

1. Historical Reporting for Message-Only Lines

   Add historical/trend reporting for Message-Only Lines within Live Reports (or Analytics Portal). Currently, the Admin Portal only shows a real-time snapshot — total messages in the box and the number still unaddressed — with no way to view this data over time.

   For contact centers using Message-Only Lines as an overflow or after-hold outlet, historical reporting is critical to understanding call access patterns. Without it, we can't accurately distinguish between:

   Patients who proactively chose voicemail instead of holding, and
   Callers who were forced to voicemail after exceeding hold-time thresholds

   This distinction directly affects how we measure and report on call abandonment, hold-time performance, and true patient access to care. Without historical trending, this volume is essentially invisible in our access reporting — understating actual call demand and misrepresenting the patient experience.

   Requested functionality:

   Historical volume of messages received per Message-Only Line (daily/weekly/monthly)
   Ability to filter/report by date range, consistent with other queue reporting
   Ideally, a data point differentiating "opted into voicemail" vs. "system-forced to voicemail due to hold time," if technically feasible
   Exportable data consistent with other Live Reports for integration into existing access dashboards

   Business impact:
   Without this, organizations lack a complete, accurate picture of call volume and access — specifically the portion of demand being deflected to voicemail — which undermines the integrity of access and volume metrics used for staffing, performance accountability, and strategic decision-making.

   Current Account Manager: Jaclyn Nickel, David Chao (Request reported to JN 09.16.2026)

   Add historical/trend reporting for Message-Only Lines within Live Reports (or Analytics Portal). Currently, the Admin Portal only shows a real-time snapshot — total messages in the box and the number still unaddressed — with no way to view this data over time.

   For contact centers using Message-Only Lines as an overflow or after-hold outlet, historical reporting is critical to understanding call access patterns. Without it, we can't accurately distinguish between:

   Patients who proactively chose voicemail instead of holding, and
   Callers who were forced to voicemail after exceeding hold-time thresholds

   This distinction directly affects how we measure and report on call… more

   16 votes

   Vote 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  ·  6 comments  ·  Live Reports  ·  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. Add Explicit "Do Not Disturb (DND)" Agent Status Metric and Breakout to Live Reports Dashboard

   As a Supervisor utilizing RingCentral Live Reports, I want the dashboard to display an explicit "Do Not Disturb (DND)" status label or column for agents, rather than grouping them under the generic "Unavailable" category. This will allow me to immediately distinguish between an agent who is missing/out-of-office versus an agent who has intentionally toggled their application or hardware deskphone to DND to complete offline work, handle an escalation, or manage a brief break.

   Current Pain Points & Behavioral Gaps:
   Currently, when an agent activates "Do Not Disturb" (DND) on their RingCentral app or physical deskphone, Live Reports aggregates this state directly into the generic "Unavailable" bucket.
   To see if an agent is actually in DND, supervisors have to change their dashboard configurations to "Expanded View Mode" or guess based on call routing behavior. Because "Unavailable" conflates multiple backend states (such as being manually logged out, system timeouts, network disconnections, or DND), leadership lacks real-time, actionable visibility into what their staff is doing at any given second.

   Proposed Solutions / Enhanced Capabilities:
   Capability 1: Standalone DND Column/Widget Metric
   Introduce a dedicated DND column to the Agent Details widget and include a unique DND counter block in the Agent Counts overview scorecard.

   Capability 2: Granular Status Breakdown Mapping
   Update the Live Reports backend data engine to parse out the strict DND state from other "Unavailable" triggers. When an agent turns on DND, their individual live status row should explicitly change to a distinct color/label (e.g., a hard red indicator labeled "Do Not Disturb" or "DND").

   Capability 3: Specific Filter Thresholds
   Add a dashboard filter toggle that allows supervisors to selectively view or isolate only agents who are currently on DND, streamlining remote team management and floor coaching.

   As a Supervisor utilizing RingCentral Live Reports, I want the dashboard to display an explicit "Do Not Disturb (DND)" status label or column for agents, rather than grouping them under the generic "Unavailable" category. This will allow me to immediately distinguish between an agent who is missing/out-of-office versus an agent who has intentionally toggled their application or hardware deskphone to DND to complete offline work, handle an escalation, or manage a brief break.

   Current Pain Points & Behavioral Gaps:
   Currently, when an agent activates "Do Not Disturb" (DND) on their RingCentral app or physical deskphone, Live Reports aggregates this state… more

   25 votes

   Vote 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  ·  Live Reports  ·  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. Multi-Select Extensions for Call Log Filtering and Reporting

   Ability to Filter Call Logs by Multiple Extensions and Generate IVR External Routing Reports

   Description:
   Currently, the Admin Portal only allows administrators to select one IVR, Call Queue, User, Group, or AI Receptionist at a time when filtering call logs.

   We would like to request an enhancement that allows administrators to select multiple extensions/entities simultaneously when reviewing call logs.

   Requested Enhancement:

   Allow users to select multiple:
   IVRs
   Call Queues
   User extensions
   Groups
   AI Receptionist extensions
   Allow multiple selections within the same call-log report instead of requiring administrators to run separate reports for each extension.
   Support reporting periods of at least 30 days and 60 days.

   Business Use Case:
   The customer has multiple IVRs configured with Business Hours. In some IVRs, callers can press a key that routes the call to an external phone number.

   The customer needs to review all applicable IVRs at once and determine:

   How many calls entered each IVR.
   How many callers selected the option that routes to an external number.
   Which IVR routed the call externally.
   The destination external number, where available.
   The total number of calls routed externally during the selected reporting period.

   Example:
   Instead of running individual reports for IVR 101, IVR 102, IVR 103, etc., the administrator should be able to select multiple IVRs and generate one consolidated report covering all selected IVRs.

   Requested Reporting Period:
   At minimum, support 30-day and 60-day reporting periods, with the ability to select a custom date range where supported.

   Expected Benefit:
   This enhancement would significantly reduce the time required for administrators to audit IVR call routing and provide a consolidated view of calls that are transferred or routed to external numbers. It would also improve reporting, monitoring, and operational analysis across multiple IVRs, Call Queues, Users, Groups, and AI Receptionist configurations.

   Ability to Filter Call Logs by Multiple Extensions and Generate IVR External Routing Reports

   Description:
   Currently, the Admin Portal only allows administrators to select one IVR, Call Queue, User, Group, or AI Receptionist at a time when filtering call logs.

   We would like to request an enhancement that allows administrators to select multiple extensions/entities simultaneously when reviewing call logs.

   Requested Enhancement:

   Allow users to select multiple:
   IVRs
   Call Queues
   User extensions
   Groups
   AI Receptionist extensions
   Allow multiple selections within the same call-log report instead of requiring administrators to run separate reports for each extension.
   Support reporting periods of at least… more

   9 votes

   Vote 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  ·  Accessibility  ·  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. Add "Average Speed to Answer" (ASA) Metric to the Company Numbers Performance Report

   1. Business Need & Context
      The customer needs to track Average Speed to Answer (ASA) sliced by specific Inbound Company Phone Numbers. They run marketing campaigns, regional DID numbers, or line-of-business numbers and need to evaluate service performance and caller wait times based on the entry phone number dialed.

   2. Current Limitation
      In RingCentral Analytics, Average Speed to Answer (ASA) is only calculated at the Call Queue or User endpoint level. The Company Numbers Report (Analytics > Performance Reports > Company Numbers) provides volume and duration metrics (Inbound Calls, Missed Calls, Total Handle Time, Avg Ring Time), but it lacks an ASA metric.

   3. Proposed Feature / Enhancement

   Add ASA as a KPI: Include Average Speed to Answer (ASA) as a toggleable KPI card and column in the Company Numbers Report within RingCentral Analytics.

   Calculation Rule: Measure the total duration from the moment the call reaches the RingCentral platform via that specific phone number until the call is answered by an agent/user (including queue wait time).

   1. Business Impact & Value

   Customer Retention: Allows managers to evaluate queue efficiency and staffing levels per phone number without having to rebuild 1:1 Call Queue mappings for every single direct line.

   Reporting Parity: Brings phone-number-level reporting in line with call queue performance analytics.

   1. Business Need & Context
      The customer needs to track Average Speed to Answer (ASA) sliced by specific Inbound Company Phone Numbers. They run marketing campaigns, regional DID numbers, or line-of-business numbers and need to evaluate service performance and caller wait times based on the entry phone number dialed.

   2. Current Limitation
      In RingCentral Analytics, Average Speed to Answer (ASA) is only calculated at the Call Queue or User endpoint level. The Company Numbers Report (Analytics > Performance Reports > Company Numbers) provides volume and duration metrics (Inbound Calls, Missed Calls, Total Handle Time, Avg Ring Time), but it lacks an ASA… more

   7 votes

   Vote 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  ·  Subscriptions  ·  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. Yealink T54W/T4U Series: One-Touch Handset Button for Manual Night/After-Hours Mode

   Summary
   Requesting the ability to configure a dedicated line key / DND / BLF button on Yealink T54W (and T4U series) handsets that allows staff to manually toggle the main company phone line between standard business hours mode and the After-Hours IVR menu with a single button press.

   Business Use Case & Value
   Currently, automatic business-hour schedules handle standard open/close times, but they do not accommodate unpredictable operational changes such as staff taking lunch breaks or leaving early. Having a physical "Night Button" on the front desk or main handsets will allow employees to instantly route incoming calls to the After-Hours IVR menu during these temporary or unscheduled gaps, ensuring no customer call goes unanswered.

   Key Requirements & Expected Functionality

   One-Touch Toggle: Pressing the designated key on the handset should immediately shift the primary inbound call flow / main trunk routing to the After-Hours IVR. Pressing it again restores normal daytime routing.

   Visual Status Indicator: The LED light on the handset line key should provide clear visual feedback (e.g., solid red or blinking when active, off/green when in standard daytime mode) so staff can easily confirm which mode is active.

   Handset Compatibility: Must be supportable on standard Yealink T4U/T54W IP desktop phones via standard provisioning (SIP code, Feature Code, or BLF key toggle).

   Summary
   Requesting the ability to configure a dedicated line key / DND / BLF button on Yealink T54W (and T4U series) handsets that allows staff to manually toggle the main company phone line between standard business hours mode and the After-Hours IVR menu with a single button press.

   Business Use Case & Value
   Currently, automatic business-hour schedules handle standard open/close times, but they do not accommodate unpredictable operational changes such as staff taking lunch breaks or leaving early. Having a physical "Night Button" on the front desk or main handsets will allow employees to instantly route incoming calls to the… more

   5 votes

   Vote 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  ·  Rooms & Devices  ·  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. Agent SOA (speed of answer) buckets

   Allow the ability to put Agent SOA into buckets to measure the number of rings an agent answers a call rather than relying on the average. I can create this report, but I need to export and manipulate the data.

   18 votes

   Vote 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  ·  Other  ·  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. Enable Timezone-Based Timestamps for Exported Analytics Reports

   Customers have reported inconsistencies between the timestamps displayed in the RingCentral Analytics dashboard and the timestamps shown in downloaded/exported report files (CSV/Excel format).

   Currently:

   The Analytics dashboard correctly reflects timestamps based on the customer account’s configured local timezone (example: EDT).
   However, exported reports are generated using UTC/universal time format regardless of the account timezone settings.

   Requested Enhancement:
   Provide an option for exported Analytics reports to use the account’s configured timezone instead of UTC. Ideally, this can be implemented through one of the following methods:

   Automatically apply the account timezone to exported reports.
   Add a selectable timezone option during report export.
   Include both UTC and local timezone columns in exported reports.

   Business Impact / Customer Impact:

   Customers experience confusion when comparing dashboard data against exported report timestamps.
   Manual timezone conversion is required after export, increasing operational overhead and risk of reporting inaccuracies.
   Organizations operating across different regions rely heavily on exported reports for audits, staffing analysis, compliance tracking, and business reporting.
   Consistent timestamps between dashboard and exported data would improve usability, reporting accuracy, and customer experience.

   Customer Use Case:
   The customer’s organization operates in the EDT timezone. While timestamps appear correctly on the Analytics dashboard, exported Excel reports display timestamps in UTC, creating discrepancies during operational review and reporting processes.

   Expected Outcome:
   Exported reports should align with the timezone configured on the customer account/dashboard to ensure consistency across all reporting interfaces.

   Additional Notes:
   Current behavior is confirmed to be working as designed because exported files use a universal timestamp format (UTC). The customer is requesting enhancement functionality rather than reporting a product defect.

   Customers have reported inconsistencies between the timestamps displayed in the RingCentral Analytics dashboard and the timestamps shown in downloaded/exported report files (CSV/Excel format).

   Currently:

   The Analytics dashboard correctly reflects timestamps based on the customer account’s configured local timezone (example: EDT).
   However, exported reports are generated using UTC/universal time format regardless of the account timezone settings.

   Requested Enhancement:
   Provide an option for exported Analytics reports to use the account’s configured timezone instead of UTC. Ideally, this can be implemented through one of the following methods:

   Automatically apply the account timezone to exported reports.
   Add a selectable timezone option during report export.… more

   11 votes

   Vote 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  ·  Subscriptions  ·  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. Support Multi-Dimensional Grouping and Outbound Queue-Mask Tracking in Business Analytics Pro

   As a RingCentral Supervisor and Systems Administrator utilizing Business Analytics Pro, I want the ability to perform multi-dimensional grouping (nested "Group Bys") and accurately track outbound performance mapped to specific Call Queues via Outbound Caller ID masks. This will allow me to seamlessly evaluate individual agent contribution directly within the scope of a shared queue across both inbound and outbound traffic streams without managing fragmented dashboards or executing manual data exports.

   Current Pain Points & Behavioral Gaps:
   Lack of Inbound/Outbound Parity for Call Queues: Currently, Call Queues are treated strictly as inbound containers. If a team of agents performs outbound dialing campaigns while utilizing the Queue’s phone number as their Outbound Caller ID mask, Business Analytics Pro logs those metrics exclusively under the individual User dimension. Selecting the Queue or Queue Agents dimension for outbound metrics yields zero results. This prevents leadership from assessing the true total volume (Inbound + Outbound) generated by a dedicated queue's operational footprint.

   No Multi-Dimensional (Nested) Group Bys: The analytics interface currently restricts reporting widgets to a single "Group By" dimension. Users cannot view an overarching Queue dimension nested with a secondary User dimension in the same data grid. While a filtering workaround exists to isolate users by a single queue, it prevents administrators from viewing a master, comparative matrix of all queues alongside their respective handling agents simultaneously.

   Proposed Solutions / Enhanced Capabilities:

   Capability 1: Outbound Caller ID Mapping to Queues (Metadata Routing):
   Introduce a backend metadata tracking option where any outbound call initiated by an extension utilizing a verified Call Queue number as their Outbound Caller ID mask attributes that specific outbound metric to the corresponding Queue container. This will allow the Queues and Queue Agents dimensions to display valid data when toggled to "Outbound" filters.

   Capability 2: Multi-Dimensional Pivot Reporting (Nested Group Bys):
   Enhance the charting engine in Analytics Pro to support a secondary "Group By" sub-dimension. For example, allow users to select Group By: Queues ➔ Then Group By: Users. This will output a structured hierarchical tree or nested data table mapping metrics like Total Calls, Talk Time, and Hold Time comprehensively across both organizational layers.

   As a RingCentral Supervisor and Systems Administrator utilizing Business Analytics Pro, I want the ability to perform multi-dimensional grouping (nested "Group Bys") and accurately track outbound performance mapped to specific Call Queues via Outbound Caller ID masks. This will allow me to seamlessly evaluate individual agent contribution directly within the scope of a shared queue across both inbound and outbound traffic streams without managing fragmented dashboards or executing manual data exports.

   Current Pain Points & Behavioral Gaps:
   Lack of Inbound/Outbound Parity for Call Queues: Currently, Call Queues are treated strictly as inbound containers. If a team of agents performs outbound… more

   9 votes

   Vote 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  ·  Accessibility  ·  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. Access call log of other extension via the RingCentral app

   "We require a configuration that allows selected team members to monitor the call activity/log (made and received) of other account extensions. This visibility must be accessible within the standard RingCentral app interface, bypassing the need for admin portal access."

   6 votes

   Vote 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  ·  Other  ·  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. Add "Average Speed to Answer" (ASA) Metric to Business Analytics Pro Company Numbers

    1. Business Need & Problem StatementThe customer utilizes Business Analytics Pro to manage performance and track service metrics across various business units. They require the ability to measure Average Speed to Answer (ASA) sliced directly by individual Company Phone Numbers.Currently, when marketing campaigns, regional lines, or specific line-of-business DIDs point to shared response targets, stakeholders cannot evaluate wait times or answering performance based on the specific entry phone number the customer dialed.2. Product GapIn Business Analytics Pro > Performance Reports > Company Numbers, users have access to metrics such as Inbound Calls, Missed Calls, Avg Ring Time, and Handle Time, but Average Speed to Answer (ASA) is not available as a selectable KPI.ASA is currently restricted to endpoint-level objects (Queues and Users). When multiple company phone numbers route into a shared Queue or User group, Business Analytics Pro cannot isolate ASA by the inbound DID. 3. Proposed Feature DescriptionInclude ASA in Company Numbers View: Expand the KPI library within Business Analytics Pro > Performance Reports > Company Numbers to include Average Speed to Answer (ASA).Calculation Logic: Measure elapsed time from when an inbound call reaches the RingCentral platform via that specific phone number until a live agent or user answers (including queue wait times and auto-receptionist navigation).Dashboard & Export Support: Allow the new Company Number ASA metric to be added to custom Business Analytics Pro drag-and-drop dashboards, scheduled reports, and BI API streams.4. Business Value & Operational ImpactEnhanced SLA Tracking: Enables enterprise customers to accurately evaluate campaign performance and regional service-level agreements (SLAs) without needing 1:1 call queue workarounds.Pro Feature Alignment: Elevates Business Analytics Pro by closing the reporting gap between high-level company phone numbers and queue-level analytics.

    1. Business Need & Problem StatementThe customer utilizes Business Analytics Pro to manage performance and track service metrics across various business units. They require the ability to measure Average Speed to Answer (ASA) sliced directly by individual Company Phone Numbers.Currently, when marketing campaigns, regional lines, or specific line-of-business DIDs point to shared response targets, stakeholders cannot evaluate wait times or answering performance based on the specific entry phone number the customer dialed.2. Product GapIn Business Analytics Pro > Performance Reports > Company Numbers, users have access to metrics such as Inbound Calls, Missed Calls, Avg Ring Time, and Handle Time, but… more
    5 votes

    Vote 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  ·  Accessibility  ·  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. Ability to Export/Download Call Logs directly within the RingCentral App

    Add a native export button within the RingCentral desktop app's Phone > Calls tab, allowing users to download call logs directly into a CSV or PDF file. Currently, users are forced to leave the desktop application and log into the web-based RingCentral Admin Portal under Analytics/Reports to pull call history data, which creates unnecessary steps for routine admin tasks. Adding a simple export option or multi-select functionality—similar to the app's existing text message and voicemail download features—would streamline daily workflows, make client record-keeping much faster, and eliminate friction for desktop users.

    5 votes

    Vote 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  ·  Accessibility  ·  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. Bulk updating/copying Business Analytics dashboards

    I would like to be able to edit the table for the default dashboard (queues, users, etc.) and be able to apply that as a template to selected "My dashboards."  I have over 200 dashboards and subscriptions, so making a change to this table and applying it to all of my dashboard is very time-consuming. The ability to bulk update is desired.

    •  

    7 votes

    Vote 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  ·  Other  ·  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. custom role can only access selected call queue on analytics

    Wants to have an option to have selected call queues visible to the said custom role. an option to hide specific call queues on that custom role

    4 votes

    Vote 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  ·  Live Reports  ·  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. Live Reports Enhancement: Real-Time Status Update for Call Queue Members

    Description:

    Implement real-time synchronization of call queue member status in Live Reports, ensuring that any changes in agent availability, whether becoming available or unavailable, are reflected instantly and accurately.

    Importance and Benefits;

    -Real-Time Visibility: Enables managers to make faster, more accurate staffing and routing decisions.

    -Quicker Response: Instantly shows who’s available, helping reduce call wait times and improve service.

    -Operational Efficiency: Ensures calls are routed to truly available agents, maximizing productivity.

    -Reliable Data: Provides confidence in Live Reports for real-time decision-making.

    -Better Customer Experience: Faster, more efficient handling of calls leads to higher satisfaction.

    34 votes

    Vote 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  ·  Live Reports  ·  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. Add Analytics Tab to Track Agent App Usage (RC App vs RC Phone)

    Request to enhance Analytics by adding a dedicated tab that displays which specific application agents are using. The view should clearly differentiate between RC App and RC Phone and allow filtering by individual agents or groups of agents.

    16 votes

    Vote 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  ·  Adoption & Usage  ·  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. company call log

    company call log in app currently if you call out from main number you cant see user which called , should say user 101 ..... called
    same with answer and called out should show main number along with user

    •  

    3 votes

    Vote 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  ·  Live Reports  ·  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. Live Report should show amount of time since last call.

    I'd like to look at a report that shows me agent1's last call was 10 seconds ago and agent2's last call was 15 minutes ago. Time between calls would be very helpful!

    6 votes

    Vote 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  ·  Live Reports  ·  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. Access to the call transcript of other extensions

    Configure permissions to allow the Super Admin role to access, review, and download call transcripts by other user extensions

    5 votes

    Vote 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  ·  Other  ·  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. Have The Option to Remove Inbound Calls in the Live report for Call Volume Widget

    When Selecting Call Volume Widget on live reports inbound calls is automatically selected and cannot be removed. We would like to filter it out for the widget as the a customer only needs to filter the outbound calls.

    7 votes

    Vote 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  ·  3 comments  ·  Live Reports  ·  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. RingSense: Reporting Issue

    Currently, when a call hits an extension configured with Simultaneous Ringing (e.g., Ext 101), RingSense attributes the entire call session, AI summary, and metrics strictly to Ext 101. It does not record which user/extension physically answered the call.

    Modify RingSense ingest logic to capture the answered_by SIP endpoint / user extension ID from the call session state rather than the initial target extension (Ext 101).

    3 votes

    Vote 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  ·  Other  ·  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