RingCX SPOG: contact search during transfer caps at 10 results — raise the cap and add scroll
Description
In the RingCX SPOG App, when users initiate a call transfer and search for a contact, the system currently returns only 10 results.
This limitation makes it difficult for agents to locate the correct contact, particularly in environments with large directories or when contacts have similar names.
Steps to Reproduce
1. Initiate or receive a call
2. Attempt to transfer the call
3. Use the contact search function
4. Observe that only 10 contacts are returned, even when more matches exist
Actual Result
Search results are limited to 10 contacts.
Expected Result
Search should return more results (e.g., 50–100) or support pagination / infinite scrolling to allow access to all relevant contacts.
Proposed Solution
- Increase the result limit to a higher threshold (configurable if possible)
- Implement pagination or infinite scroll
- Improve search relevance (e.g., fuzzy search, ranking)
- (Optional) Add filters such as department or team
Business Impact
- Increases Average Handle Time (AHT)
- Reduces agent efficiency
- Increases likelihood of incorrect call transfers
- Negatively impacts user experience
=====
Today, when a RingCX SPOG agent initiates a call transfer and types into the contact search field, the dropdown returns at most 10 matches with no way to see more. In tenants with large corporate directories or common names (e.g. multiple "John" or "Smith"), agents often can't find the intended transfer target and either guess, hang up, or escalate. The desired behavior is a larger result set (target ~50–100), with pagination or infinite scroll so the agent can keep looking, and ideally fuzzy/relevance ranking so the right contact surfaces near the top. Impact: lower AHT on transfers, fewer misrouted calls, less agent friction in directories of any meaningful size.