Designing Screen Recording Quality Assurance Workflows with Evaluator Annotation Tools

How-To-Articles
1

Designing Screen Recording Quality Assurance Workflows with Evaluator Annotation Tools

What This Guide Covers

This article details the architectural design and configuration of a robust Quality Assurance (QA) workflow within Genesys Cloud CX that leverages Screen Recording capabilities. You will learn how to configure the recording infrastructure, build an evaluation form that supports synchronized screen annotations, and manage the data lifecycle for compliance and training purposes. The end result is a QA process where evaluators can timestamp specific visual interactions on the agent desktop, linking those visual cues directly to performance scores and coaching notes.

Prerequisites, Roles & Licensing

To implement this solution, the following technical and licensing prerequisites must be met:

  • Licensing Tiers:
    • CX 3 License: Required for the full suite of QA capabilities, including custom evaluation forms and advanced reporting.
    • Screen Recording Add-on: Specifically required for capturing agent desktop activity. This is not included in the base CX license.
    • WEM (Workforce Engagement Management) Add-on: Optional but recommended if you intend to use the unified WEM dashboard for managing QA and Screen Recording data side-by-side.
  • Permissions & Roles:
    • Administrator: Requires Telephony > Screen Recording > Edit and QA > Evaluation Form > Edit.
    • Evaluator: Requires QA > Evaluation > Evaluate and QA > Screen Recording > View.
    • Supervisor/Manager: Requires QA > Evaluation > View and QA > Screen Recording > View.
  • External Dependencies:
    • Genesys Cloud Desktop App: Must be installed on all agent machines with the Screen Recording feature enabled in the client settings.
    • Agent Consent Configuration: Legal review of the Screen Recording consent banner text, as this is displayed to the agent upon launch.

The Implementation Deep-Dive

1. Configuring the Screen Recording Infrastructure

Before designing the QA workflow, the underlying recording capability must be provisioned. Screen Recording in Genesys Cloud operates by capturing the screen content of the Genesys Cloud Desktop application. It does not capture the entire OS desktop unless specific configurations are applied, but it captures all windows managed by the Genesys client, including integrated CRM views if they are embedded within the app or if the app is running in a mode that allows screen capture.

Configuration Steps:

  1. Navigate to Admin > Telephony > Screen Recording.
  2. Enable the global toggle for Screen Recording.
  3. Define the Recording Policy. You must select which user groups are subject to recording.
    • Critical Decision: Do not enable recording for all users globally unless mandated. Create a specific User Group (e.g., QA-Targeted-Agents) and assign agents to this group. This allows you to test the workflow with a small cohort before enterprise-wide rollout.
  4. Configure the Consent Banner. This text appears to the agent when they log in.
    • The Trap: Leaving the default consent text vague. In many jurisdictions (GDPR, CCPA), “screen recording” is considered biometric or sensitive data processing depending on what is captured. Ensure the text explicitly states that the desktop activity is being recorded for quality assurance and training purposes. Failure to provide clear consent can lead to legal invalidation of the QA data.

Architectural Reasoning:
We isolate the recording policy to specific user groups to manage storage costs and performance overhead. Screen recording generates significantly more data than audio-only calls. By restricting the scope, you reduce the load on the Genesys Cloud storage backend and ensure that only relevant interactions are captured for QA.

2. Building the Evaluation Form with Screen Annotation Support

The core of this workflow is the Evaluation Form. Unlike standard audio QA, screen QA requires the evaluator to correlate visual actions with score criteria. Genesys Cloud QA forms support the integration of Screen Recording playback directly within the evaluation interface.

Configuration Steps:

  1. Navigate to Admin > QA > Evaluation Forms.
  2. Create a new form or clone an existing one (e.g., Standard QA Form).
  3. Add a Screen Recording Widget to the form.
    • This widget is not a standard question type. It is a media component that loads the associated screen recording for the selected interaction.
    • Ensure the Interaction Type for the form is set to Screen Recording. If you mix Interaction Types (e.g., Audio and Screen) in one form, the system may struggle to load the correct media stream, leading to playback failures.
  4. Design the Annotation-Driven Questions.
    • Instead of generic questions like “Did the agent follow the script?”, create questions that require visual verification.
    • Example Question: Agent correctly entered the customer ID in the CRM within 10 seconds.
    • Type: Boolean or Score (1-5).
    • The Trap: Relying on the evaluator to remember visual events. Human memory for visual tasks is poor. The form design must force the evaluator to scrub the timeline. Use Section Breaks to group questions by the phase of the interaction (e.g., “Login Phase”, “Data Entry Phase”, “Resolution Phase”). This guides the evaluator to scrub to the relevant timestamp.

Architectural Reasoning:
We use Section Breaks to map the evaluation form to the temporal structure of the screen recording. This reduces cognitive load on the evaluator. Without this structure, evaluators often watch the entire recording passively, leading to inconsistent scoring. By structuring the form chronologically, you enforce active evaluation.

3. Implementing the Annotation and Feedback Loop

The value of screen recording QA lies in the ability to provide specific, timestamped feedback. Genesys Cloud allows evaluators to add comments that are linked to specific timestamps in the recording.

Configuration Steps:

  1. In the Evaluation Form, enable Comments for each question.
  2. Configure the Feedback Visibility settings.
    • Set Agent Visibility to Visible after review.
    • Set Manager Visibility to Always Visible.
  3. Train evaluators on the Annotation Tool.
    • When viewing the screen recording in the QA interface, the evaluator can pause the video and click the Add Comment icon.
    • This action creates a bookmark in the recording timeline.
    • The Trap: Evaluators adding generic comments like “Good job” or “Bad entry”. Enforce a standard operating procedure (SOP) that requires comments to include: (1) What was observed, (2) Why it was scored poorly/well, and (3) The exact timestamp.

Architectural Reasoning:
We link comments to timestamps to create an auditable trail. This is critical for dispute resolution. If an agent challenges a score, the manager can jump directly to the timestamp cited by the evaluator. This removes ambiguity from the coaching conversation.

4. Automating the QA Assignment Workflow

Manual assignment of screen recordings for QA is inefficient. You should leverage Genesys Cloud’s QA Campaigns to automate the selection and assignment of recordings.

Configuration Steps:

  1. Navigate to Admin > QA > Campaigns.
  2. Create a new Campaign named Screen QA - Weekly Review.
  3. Set the Interaction Type to Screen Recording.
  4. Define Selection Criteria:
    • Date Range: Last 7 days.
    • User Group: QA-Targeted-Agents.
    • Status: Completed.
    • Optional: Use Speech Analytics data to filter. If you have Speech Analytics enabled, you can filter for recordings where the agent used specific keywords (e.g., “refund”, “cancel”). This allows for targeted QA on high-risk interactions.
  5. Set Assignment Rules:
    • Assign to: QA Team (User Group).
    • Method: Round Robin or Random.
    • The Trap: Assigning all recordings to a single evaluator. This leads to evaluator fatigue and bias. Use Round Robin to distribute the load evenly.

Architectural Reasoning:
We use automated campaigns to ensure statistical validity. Manual selection introduces bias (e.g., supervisors only listening to calls they know were bad). Automated random sampling ensures that the QA scores represent the true performance of the agent population.

Validation, Edge Cases & Troubleshooting

Edge Case 1: Screen Recording Playback Failure in QA Interface

The Failure Condition:
The evaluator opens the evaluation form, but the screen recording widget shows a “Failed to Load” error or remains blank.

The Root Cause:
This is often caused by a mismatch in the Interaction ID between the QA system and the Screen Recording backend. This can happen if the recording was started but not properly stopped due to an abrupt client crash or network dropout. Another common cause is that the recording file was not fully uploaded to the Genesys Cloud storage before the QA evaluation was triggered.

The Solution:

  1. Check the Screen Recording Status in Admin > Telephony > Screen Recording > Recordings.
  2. If the status is Uploading or Processing, wait for it to change to Available.
  3. If the status is Failed, check the Genesys Cloud Desktop App logs on the agent machine. Look for errors related to screen_capture or network_timeout.
  4. Ensure the agent’s firewall allows outbound traffic to the Genesys Cloud media endpoints on ports 443 and 50000-50100 (UDP/TCP).

Edge Case 2: Agent Privacy and Data Masking

The Failure Condition:
The screen recording captures sensitive customer data (PII, PCI) that should not be visible to QA evaluators, violating compliance policies (e.g., PCI-DSS).

The Root Cause:
Screen recording captures everything visible on the screen. If the agent has a CRM window open with credit card numbers, those numbers are recorded.

The Solution:

  1. Training: Implement strict agent training on Data Masking. Agents must blur or hide sensitive fields before performing actions that are likely to be reviewed.
  2. Technical Mitigation: Use Genesys Cloud Desktop App Settings to restrict which applications are captured. If possible, configure the app to only capture the Genesys interface and exclude external CRM windows, or use a virtual desktop infrastructure (VDI) that allows for pixel-level masking.
  3. Policy Update: Update the QA Evaluation Form to include a mandatory question: Was any PII/PCI visible during the interaction? If the answer is Yes, the evaluation must be flagged for Compliance Review by a specialized team, and the score may be voided to prevent penalizing the agent for a systemic privacy issue.

Edge Case 3: Desynchronization Between Audio and Screen Video

The Failure Condition:
The evaluator hears the agent speak, but the screen actions (e.g., clicking a button) appear to happen several seconds before or after the corresponding audio cue.

The Root Cause:
This is a known issue in some versions of the Genesys Cloud Desktop App where the audio stream and the screen capture stream are encoded separately and may experience slight latency differences during upload. The QA player attempts to synchronize them, but if the network conditions were poor during the call, the synchronization offset may be significant.

The Solution:

  1. Check the Genesys Cloud Desktop App version. Ensure all agents are on the latest version, as synchronization algorithms are improved in each release.
  2. If the offset is minor (< 2 seconds), train evaluators to account for this latency.
  3. If the offset is major (> 5 seconds), submit a Support Ticket to Genesys Cloud with the Interaction ID and Recording ID. This is likely a backend encoding error.
  4. As a workaround, encourage evaluators to rely primarily on the Screen Video for visual tasks and the Audio for verbal tasks, rather than expecting perfect lip-sync between the two.

Official References