Implementing Badge and Achievement Systems Tied to Quality Management Evaluation Scores

How-To-Articles
1

Implementing Badge and Achievement Systems Tied to Quality Management Evaluation Scores

What This Guide Covers

This guide details the configuration of Genesys Cloud Achievements driven by Quality Management (QM) evaluation scores. You will configure achievement rules that trigger upon specific score thresholds being met within defined time windows. The end result is a gamified performance system where agents receive real-time badges and notifications directly within the platform interface based on validated QM data.

Prerequisites, Roles & Licensing

Before initiating configuration, verify the following environment requirements to ensure successful deployment of achievement logic tied to evaluation data.

Licensing Tiers

  • Genesys Cloud CX Platform: Full license required for all agents involved in the program.
  • Quality Management Add-on: Essential for the evaluation scoring engine. The achievement trigger relies on the existence of a valid evaluation record.
  • Workforce Engagement Management (WEM): Required for the “Achievements” feature to be active. This is often included in the CX 3 or higher tier but must be verified under License Administration.

Granular Permissions
Users configuring this system require specific permissions within the Admin Console. Do not grant full Administrator rights; adhere to the principle of least privilege.

  • Quality > Evaluations > Edit: Required to modify evaluation forms and ensure score fields are available for triggering.
  • Quality > Achievements > Edit: Required to create and edit achievement definitions.
  • Reporting > Reports > All: Required if you intend to build custom dashboards to track achievement distribution across the organization.
  • System > Admin > View Licenses: To verify WEM entitlement availability.

OAuth Scopes (For API Integration)
If you extend this system via API to push custom badges or integrate with external HR systems, the following scopes are mandatory:

  • quality.read
  • achievement.read
  • achievement.write
  • profile.view

External Dependencies

  • Evaluation Forms: Must exist and contain numeric fields capable of aggregation (e.g., “Average Score” or “Specific Competency Rating”).
  • Notification Channels: Teams, Email, or In-App notifications must be configured in the Contact Center routing plan to handle achievement events.

The Implementation Deep-Dive

1. Configure Quality Evaluation Form Structure for Triggering

The foundation of any achievement system is the data source. You cannot trigger an achievement on a text field or a boolean that lacks a numeric value. The QM evaluation form must be structured to expose numeric scores that map directly to achievement thresholds.

Configuration Steps:

  1. Navigate to Admin > Quality > Evaluation Forms.
  2. Select the form associated with your primary quality program (e.g., “Standard Customer Service Evaluation”).
  3. Open the Question Editor and identify the fields you wish to use as triggers (e.g., “Customer Satisfaction”, “Adherence to Protocol”).
  4. Ensure these questions utilize a numeric scale (typically 1-5 or 1-10). Avoid dropdowns unless they map strictly to integers in the backend logic.
  5. If you require composite scores, create a calculated field within the form configuration that sums specific competency areas.

The Trap: The most common failure occurs when administrators use qualitative text fields for scoring. The achievement engine expects numeric input for threshold comparison (e.g., score > 4.0). If a form contains unstructured text or mixed data types, the trigger will fail silently during evaluation submission.

  • Catastrophic Downstream Effect: Agents submit evaluations that meet performance standards but receive no badges because the scoring engine cannot parse the value. This erodes trust in the gamification system and leads to complaints about unfairness.
  • Architectural Reasoning: We enforce numeric fields because they allow for deterministic logic evaluation. Text-based triggers require Natural Language Processing which introduces latency and variance unsuitable for real-time achievement triggering.

2. Define Achievement Rules and Thresholds

With the data source validated, you must define the rules that convert a score into an achievement event. Genesys Cloud allows for two primary types of achievements: Instant (triggered on submission) and Rolling (triggered over a time window).

Configuration Steps:

  1. Navigate to Admin > Workforce Engagement Management > Achievements.
  2. Click Create Achievement.
  3. Select the Trigger Type. Choose “Quality Evaluation Score” as the source event.
  4. Define the Condition Logic. You will configure operators such as Greater Than, Less Than, or Equal To.
    • Example: Average Score >= 4.5 over a 7-Day Rolling Window.
  5. Set the Badge Configuration. Upload an image asset (PNG/SVG, max 1024x1024) and define the display title (e.g., “Gold Star Performer”).
  6. Configure Notification Rules. Select whether this triggers a system notification to the agent or a broadcast message to their team lead.

The Trap: Misconfiguring the time window for rolling achievements. Many architects configure a 7-Day window but do not account for evaluation processing latency. If an evaluation is submitted at 11:59 PM on Day 1, it may not be scored and available in the achievement engine until 2:00 AM the next day due to batch processing cycles.

  • Catastrophic Downstream Effect: Agents perceive the system as laggy or broken because they achieve a score but do not receive the badge immediately. This creates a disconnect between performance and recognition, reducing the motivational impact of the achievement system.
  • Architectural Reasoning: We recommend setting rolling windows to 7 days or 14 days rather than 24 hours. Evaluation data ingestion into the analytics engine is asynchronous. A longer window absorbs processing latency without breaking the user experience logic.

API Payload Example for Custom Achievement Logic:
If you require custom validation outside the UI (e.g., checking agent tenure alongside score), use the Achievements API to verify conditions programmatically.

POST /api/v2/achievements/rules
{
  "name": "TenureAndScoreAchievement",
  "description": "Achievement for agents with 6 months tenure and QM score > 90",
  "triggerType": "QUALITY_EVALUATION",
  "condition": {
    "operator": "AND",
    "conditions": [
      {
        "field": "evaluationScore",
        "operator": "GT",
        "value": 90
      },
      {
        "field": "agentTenureDays",
        "operator": "GTE",
        "value": 180
      }
    ]
  },
  "badgeImageId": "img_12345abcde"
}

3. Map Achievement Events to Notification Channels

An achievement without visibility provides no value. You must ensure that the trigger event propagates through the notification fabric of the platform. This involves linking the achievement definition to the Notification configuration within WEM.

Configuration Steps:

  1. Navigate to Admin > Workforce Engagement Management > Notifications.
  2. Locate the Achievement Triggered category.
  3. Create a new Notification Rule. Link it to the Achievement ID created in the previous step.
  4. Select the Channel. Options include In-App Banner, Email, or Third-party Integration (e.g., Microsoft Teams).
  5. Define the Audience Scope. You can restrict notifications to the specific agent (Individual) or their Supervisor (Manager View).

The Trap: Over-notification fatigue. Configuring a rule that sends an email and a Teams message and an in-app banner for every minor achievement creates noise.

  • Catastrophic Downstream Effect: Agents begin to ignore notifications entirely because the signal-to-noise ratio is too low. They stop looking at their badge inventory, rendering the gamification useless.
  • Architectural Reasoning: We use a tiered notification strategy. High-value achievements (e.g., “Perfect Score”) trigger all channels. Minor achievements (e.g., “10th Evaluation Completed”) trigger only the in-app banner. This prioritizes cognitive load and ensures important milestones are seen.

Configuration Snippet for Notification Logic:
When configuring the notification rule, ensure you utilize conditional logic to prevent duplicate sends.

{
  "notificationRule": {
    "name": "QM_Achievement_Alert",
    "targetType": "AGENT",
    "channels": [
      "IN_APP_BANNER",
      "EMAIL"
    ],
    "frequencyCap": "PER_DAY",
    "maxFrequency": 2
  }
}

Validation, Edge Cases & Troubleshooting

Edge Case 1: Evaluation Score Correction and Badge Revocation

The Failure Condition: An agent receives a badge based on an evaluation score. Later, a supervisor reviews the call recording and changes the score downward, dropping it below the achievement threshold. The badge remains on the agent’s profile despite the corrected data.

The Root Cause: Achievement triggers are often event-driven (fire-and-forget). Once the badge is awarded, the system does not automatically revoke it unless configured to do so. This creates a discrepancy between current performance standing and historical recognition.

The Solution: Implement a “Re-evaluation” logic within your WEM settings.

  1. Enable Achievement Validation Cycles. Set this to run nightly or hourly depending on the criticality of score accuracy.
  2. Configure the Achievement Rule to include a Revocation Condition. If CurrentScore < Threshold, remove badge and log a revocation event.
  3. Note that revocation events trigger a different notification (Badge Removed) which must be configured carefully to avoid discouraging agents.

Edge Case 2: Batch Processing Latency in High-Volume Centers

The Failure Condition: During peak call volume, evaluations are submitted rapidly. Agents do not see badges appear until several hours after the evaluation is completed.

The Root Cause: Achievement processing occurs in a batch job queue separate from the real-time ingestion of QM scores. In high-volume environments, this queue can experience backlogs.

The Solution:

  1. Monitor System > Admin > System Logs for AchievementProcessing jobs.
  2. If latency exceeds 30 minutes, increase the processing priority of the achievement job in the background worker configuration (requires Genesys Support intervention or specific WEM tuning parameters).
  3. Alternatively, adjust the threshold window to be slightly more forgiving (e.g., 4.5 instead of 4.6) to account for potential score rounding variances during high-load periods where calculation precision might fluctuate due to load balancing.

Edge Case 3: Permission Drift and Audit Trails

The Failure Condition: An agent claims they are not receiving badges that other agents in their team receive, despite identical scores.

The Root Cause: Role-based access control (RBAC) changes over time. A supervisor might have inadvertently removed the Achievement > View permission from a specific group of agents during a permissions audit.

The Solution:

  1. Run a standard report to compare Agent Permissions against Achievement Status.
  2. Verify that the agent has Quality > Evaluations > Read access. Without this, they cannot see their own scores in the portal, which is required to view associated achievements.
  3. Check the Audit Log for any recent modifications to the Achievement Rule definition itself. If a rule was edited and the scope changed from All Agents to Specific Groups, agents outside that group will be excluded automatically.

Official References