Settings and activity
105 results found
-
63 votes
Sofya
supported this idea
·
-
58 votes
Sofya
supported this idea
·
-
25 votes
Sofya
supported this idea
·
-
15 votes
Sofya
supported this idea
·
-
19 votes
Sofya
supported this idea
·
-
134 votes
Sofya
supported this idea
·
-
233 votes
Sofya
supported this idea
·
-
15 votes
Sofya
supported this idea
·
-
3 votes
Sofya
supported this idea
·
-
45 votes
Sofya
supported this idea
·
-
18 votes
Sofya
supported this idea
·
-
23 votes
Sofya
supported this idea
·
-
22 votes
Sofya
supported this idea
·
-
36 votes
I'm pleased to announce that this feature is live! RingSense (RS) now lets you:
- Filter interactions by Queue (REX/RCX) and Disposition in the filter panel.
- See source identifiers on each interaction—including the queue (REX, RCX) and the final Disposition value—for clear traceability.
- Target scorecards using Queue and Disposition so you can tailor evaluations by routing path or final outcome. (Great for customizing scorecards by team/flow or result.)
More details in the attached screenshots.
Why this matters
- Enhanced visibility: Source identifiers in RS make it easy to correlate data across RS ↔ REX/RCX.
- Smarter insights: REX/RCX call-queue metadata is now available for advanced filtering and analysis.
- Customizable targeting: Use Queue and Disposition to build highly relevant, outcome-aware scorecards.
Sofya
supported this idea
·
-
330 votes
Sofya
supported this idea
·
-
70 votes
Sofya
supported this idea
·
-
37 votes
Sofya
supported this idea
·
-
46 votes
Sofya
supported this idea
·
-
17 votes
Sofya
supported this idea
·
-
170 votes
Sofya
supported this idea
·