103 results found

1. Case Sensitivity for Audio Search is not friendly

   1. Inconsistent User Expectations Most users are accustomed to search functions (e.g., on Google, file systems, or applications) that are case-insensitive. Forcing them to match the exact case creates unnecessary friction. Users might not remember the exact case used when inputting keywords or metadata, leading to repeated failed searches.
   2. Reduced Efficiency Case-sensitive searches require more precision, which slows down the user experience. For example, searching for "Interview" might fail if the actual data is labeled as "interview," causing users to spend extra time troubleshooting or retrying searches.
   3. Increased Error Rate Capitalization errors are common, especially in fast-paced or high-stress environments. A case-sensitive system punishes these errors, making it harder for users to get results on the first try.
   4. Limited Accessibility Case sensitivity might disproportionately affect users with dyslexia or those unfamiliar with the conventions of the metadata format. It can also be challenging for users working on devices with non-standard keyboards or autocorrect features.
   5. Poor Compatibility with Voice or Automated Inputs In scenarios where audio search is paired with voice commands or automated inputs, ensuring case accuracy can be impractical. Voice-to-text systems may not always apply the correct capitalization, leading to mismatched search results.
   6. Contradicts the "Forgiving Interface" Principle User-friendly interfaces are designed to tolerate minor errors and inconsistencies in input. A case-sensitive search system feels rigid and unaccommodating, alienating users.

   Solution Recommendation:
   Implement a case-insensitive search by default, allowing users to find results regardless of capitalization. If necessary, offer advanced search options where case sensitivity can be toggled on for specific use cases. This balances flexibility with usability.

   1. Inconsistent User Expectations Most users are accustomed to search functions (e.g., on Google, file systems, or applications) that are case-insensitive. Forcing them to match the exact case creates unnecessary friction. Users might not remember the exact case used when inputting keywords or metadata, leading to repeated failed searches.
   2. Reduced Efficiency Case-sensitive searches require more precision, which slows down the user experience. For example, searching for "Interview" might fail if the actual data is labeled as "interview," causing users to spend extra time troubleshooting or retrying searches.
   3. Increased Error Rate Capitalization errors are common, especially in fast-paced or high-stress environments. A… more
   2 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  ·  Admin experience  ·  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. RCX - Admin ability to share the dashboard to Supervisor only

   Admin ability to share the dashboard with the Supervisor only without admin access

   1 vote

   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  ·  Admin experience  ·  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. Allow Super Admins to have a non billable agent account for testing

   Enable Super Admins to access a non-billable agent account specifically designated for testing purposes. This account will allow Super Admins to simulate agent activities, troubleshoot issues, and test system updates or changes without incurring additional charges or affecting billing metrics. By providing a non-billable test account, Super Admins can ensure that workflows, new features, and platform configurations are thoroughly vetted, improving the reliability of the overall system and enhancing the user experience for all agents.

   2 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  ·  Admin experience  ·  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