good point. I'll check definitely, what are the options we have, ;)
I'm still open to see other ideas. when I checked the data action still not correct since it's returning all the calls where the agent was involved and the conversation recorded, but not everytime that specific agent picked up... so it will need some tidy-up.
Original Message:
Sent: 05-14-2026 05:24
From: Phaneendra Avatapalli
Subject: Agent-Level Call Recording Percentage
Hi Adorjan,
One possible recommendation might be to try using a Cloud Function alongside the Data Actions approach, as it could help reduce some of the overall complexity.
The idea itself sounds technically possible, but handling multiple analytics queries, Architect expressions, percentage calculations, and branching logic directly in Architect may become difficult to maintain over time.
A Function could potentially centralize the logic and simply return a lightweight decision such as whether the interaction should be recorded or not.
Hope this helps.
------------------------------
Phaneendra
Technical Solutions Consultant
Original Message:
Sent: 05-14-2026 04:59
From: Adorjan Racz
Subject: Agent-Level Call Recording Percentage
Hi Kaio, and thank you all for the replies.
This idea is so close to our needs and worth to consider, (easy to manage, not accurate but fairly optimal)
My other idea is to set 2 data actions to count the agent's interactions 1 total and 1 with recording(i'm not sure is there a possibility to narrow it to recording segments)
and before sending the call to the agent we set a screen pop to check the percentage and agentID against the rules controlled by a datatable.
I know it sounds overcomplicated but it's not my idea :D
The data action I tried hitting
/api/v2/analytics/conversations/details/query
with a simple payload(agentID,IN/OUTBOUND,Voice,today)
the recorded
with a simple payload(agentID,IN/OUTBOUND,Voice,today,dimension:recorded:true)
and do a simple % calculation if below 70% release a secure pause.
Any overcomplicated ideas?
#WorkaroundAsAService
------------------------------
Adorjan Racz
Customer Solutions Design Practioner
Original Message:
Sent: 05-13-2026 16:12
From: Kaio Oliveira
Subject: Agent-Level Call Recording Percentage
Hi
Adorjan
-
In Brazil, 100% of calls must be recorded, so I haven't encountered that scenario yet.
-
The idea I can give you is this:
Since you need to recording by percentage, you could use the selective method based on "Time sets".
-
For example, assuming your operation runs from 7 AM to 7 PM, that's 12 hours a day.
12 * 0.7 = 8.4, meaning 8.4 hours per day need to be recorded and 3h26m do not need record.
-
My idea is to spread those 3 hours and 30 minutes throughout the weekdays.
This ensures that you get all the times, all the agents, all the call volumes...etc.
-
for exemple:
Monday
Not recording: 3:24 PM → 7:00 PM
Recording: 7:00 AM → 3:24 PM
-Tuesday
Does not record: 07:00 → 10:36
Records: 10:36 → 19:00
-
Wednesday
Does not record: 11:00 → 14:36
Records: 07:00 → 11:00 / 14:36 → 19:00
-
Thursday
Does not record: 08:48 → 12:24
Records: 07:00 → 08:48 / 12:24 → 19:00 /
.
.
etc
-
-
Just a reminder that 70% of the TIME doesn't exactly mean 70% of the CALLS.
The most accurate way would be to analyze the history and distribute the "gaps" proportionally to the hourly volume.
It's not perfect, but I believe it's close to what you need.
-
I hope this help you.
------------------------------
Kaio Oliveira
GCP - GCQM - GCS - GCA - GCD - GCO - GPE & GPR - GCWM
PS.: I apologize if there are any mistakes in my English; my primary language is Portuguese-Br.
Original Message:
Sent: 05-13-2026 09:27
From: Adorjan Racz
Subject: Agent-Level Call Recording Percentage
Hi everyone,
I'm looking into flexible call recording strategies within Genesys Cloud and had a specific use case in mind.
Ideally, I'd like to configure recording in a way that behaves similarly to a percentage-based model at the agent level (not queue level that is already in use). For example, if we set recording to 70%, then roughly 70% of each agent's interactions would be recorded, rather than applying the percentage globally across the entire queue or org.
This would help ensure a more balanced and consistent distribution of recordings across agents for QA and compliance purposes.
My questions:
- Are there any native options in Genesys Cloud that support per-agent recording percentages?
- If not directly supported, what are the recommended design patterns or workarounds (e.g., using policies, rules, scripts, or API-driven approaches)?
- Has anyone implemented a similar solution (e.g., using randomization, external automation, or QA assignment logic)?
- Any best practices or pitfalls to be aware of when trying to achieve this kind of recording distribution?
I'd really appreciate hearing about real-world implementations or creative approaches others have used.
Thanks in advance!
#Reporting/Analytics
------------------------------
Adorjan Racz
Customer Solutions Designer
------------------------------