Genesys Cloud workforce engagement management: the WEM handbook

Workforce engagement management (WEM) is Genesys's workforce optimisation suite inside Genesys Cloud. Genesys describes it as a comprehensive solution that simplifies the agent experience and helps organisations drive results and employee satisfaction, with call recording, screen recording, quality management, performance management, speech and text analytics and workforce management.

WEM is not a separate product to install. It is a set of features in the same Genesys Cloud organisation as your queues, routing and reporting, so the queues, skills, languages and users it works on are the ones the rest of the platform uses. That is why WEM results depend so heavily on routing design and data quality upstream: a quality score, a leaderboard and a forecast all inherit whatever the routing and the activity codes say.

WEM is included in the higher Genesys Cloud CX tiers and sold as an add-on for the lower ones. The table summarises Genesys's plan comparison as published on its pricing page on 13 November 2026.

Genesys frames workforce management as four activities: forecasting requirements (how many people, with which skills), planning work schedules (getting people in place at the right times), managing employee time and adherence (making sure they are there when planned), and monitoring and analysing (adjusting in real time and improving the next cycle).

Everything else in WEM touches workforce management because everything else uses agent time. An evaluation, a coaching session, a module or a calibration meeting is time away from customers, and unless it is scheduled and coded it shows up as unexplained non-adherence and unplanned shrinkage.

• Get the hierarchy right: business units for agents who share queues, management units for rules and permissions, planning groups for workload, staffing groups for allowances and capacity plans.
• Build the activity code list first and govern it; the codes decide pay, adherence and shrinkage for every part of WEM.
• Default to Automatic Best Method forecasts, import history on day one, and modify sparingly.
• Encode contracts and law in work plans; triage generation messages; publish to a fixed calendar with a rolling horizon.
• Run the day from an agreed recovery plan; reforecast before you reschedule.
• Reconcile scheduled against actual shrinkage monthly, without double-counting what shifts already contain.

Genesys Cloud records calls and digital interactions using policies that decide which ACD interactions to record and how long to keep them, with encryption keys unique to each organisation. Screen recording captures the agent's screen during ACD interactions for quality purposes; it supports multiple monitors, is switched on through policies, and set-up can involve deploying the Genesys Cloud Background Assistant or configuring ChromeOS devices. Administrators can set limits on simultaneous screen recordings, end recordings in progress, and change archive and deletion dates.

Recording is where WEM meets the law. Every recording policy should have a stated purpose, a retention period matched to it, and access limited to the people who need it. In the UK, call and screen recording of employees must be lawful, proportionate and transparent, and agents must be told about it in advance.

Quality management lets managers record and evaluate agents and interactions to improve the contact centre experience, and coach agents to improve performance. It includes customisable evaluation forms with weighted questions, evaluations of recorded and in-progress interactions, annotations, disputes, scoring policies and AI scoring, plus an evaluator dashboard.

Calibration is how you make scores fair. In Genesys's definition, quality administrators select recorded interactions for calibration and assign evaluators; the evaluators score the same interactions, and the results are compiled so the variation between them is visible. The Calibration Evaluations dashboard tracks each session, including an Unfinished column for evaluators who have not completed their part, and average scores so you can see drift.

• Appoint one owner of quality standards who makes the final call on what is assessed and how.
• Write down the scoring principles you agree in calibration, with examples, so new evaluators score the same way.
• Have evaluators score independently first and compare afterwards; scoring together by discussion lets the loudest voice set the standard.
• Rotate interaction types and channels through calibration: voice, chat, email and messaging, service and sales.
• Judge evaluator consistency on a reasonable sample, not a handful of interactions, comparing each evaluator's scoring with the team's question by question.
• Invite agents to calibration sessions, or to score an interaction themselves first, so they see the standard they are measured against.
• Schedule calibration and evaluation time as coded activities, so it is visible in the schedule and in shrinkage.

Coaching and training are where quality findings turn into better conversations. Both use agent time, so both belong in the schedule.

Gamification turns performance objectives into points and metrics shown on scorecards and leaderboards in the agent's Home view. Performance administrators create objectives from Genesys Cloud metrics, define performance zones, and group agents into profiles, each with its own metrics and members; there is one default profile, with optional automatic assignment. The employee performance use case shows the intended shape: a single scorecard that brings metrics together, objectives with points, and agents seeing their schedule, coaching appointments, modules, scorecard and leaderboards in one place.

Comparing performance with peers changes behaviour, which is the point and the risk. Industry experience is consistent: static leaderboards topped by the same people demotivate everyone else, and schemes that reward only routine activity lose meaning quickly.

• Choose objectives agents can influence, and avoid rewarding speed at the expense of resolution or quality.
• Reward improvement as well as rank, and set challenges against each person's own previous best.
• Use team goals alongside individual ones.
• Segment leaderboards so people compete with peers in similar roles, and never use one to shame the people at the bottom.
• Explain how points are calculated before launch, and let agents see their own data first.
• Review objectives and rewards regularly; gamification is not set and forget.

Speech and text analytics analyses customer conversations: voice transcription, dictionaries to improve accuracy with your own terms, topics and interaction categories, sentiment, agent empathy analysis, content search, and reprocessing so topic changes can be applied to past interactions. Transcripts and sentiment feed quality evaluation, so evaluators can find the interactions worth reviewing rather than sampling at random.

Surveys capture the customer's view after an interaction, by voice or on the web. For a planner, the reason to care about both is handle time: a new script, a compliance prompt or a survey invitation changes how long interactions take, and therefore how many people you need. Feed known changes into forecast modifications before they land.

Every part of WEM spends the same currency: scheduled, coded agent time. When that time is planned and coded, the numbers stay honest across workforce management, quality and performance. When it is not, quality work looks like non-adherence, training looks like unplanned shrinkage, and nobody trusts the reports.

On desktop and mobile, agents can view their schedules by week, month or year; see out-of-adherence notifications and their own adherence in the Activity view's adherence widget; submit and track time-off requests; create, accept and post shift trades, browse alternative shifts and pick up extra shifts; take part in work plan bids; and see their scorecard, leaderboards, coaching appointments and modules. Genesys Tempo is the mobile app; late explanations can currently be submitted only through it.

Genesys describes these self-service tools, on desktop and mobile, as there to allow schedule flexibility and work-life balance, and in practice they are what make rigorous scheduling and adherence acceptable to agents. Every request a planner approves by hand is a request the rules could have decided.

WEM access is controlled by roles and permissions, not a single user type. Workforce management permissions are documented in the workforce management permissions overview; quality, performance and recording each have their own. Two points catch people out: permission changes can take a few minutes to take effect, and planners need Routing > Queue > Search and Routing > Skill > Manage or queue, skill and language names show as placeholders.

Access to schedules is governed by Workforce Management > Schedule and Published Schedule permissions, refined by conditions: a user whose schedule permission is limited to selected work teams can choose only those teams in the schedule editor, and users without work team permissions cannot select work teams at all. Divisions partition WFM data as they do the rest of the platform. Agents need Workforce Management > Agent Schedule Notification > View to be notified of schedule changes.

• Create named, scoped roles such as Workforce Planner, Quality Evaluator and Team Leader rather than handing out Master Admin.
• Remember the billing effect: on CX 1 and CX 2, some WEM administrator roles start add-on charges as soon as they are assigned.
• Use the audit log viewer, under Admin > Troubleshooting or linked from WFM views, to see who created, changed, deleted or published activity codes, business units, forecasts, management units, schedules, trades, time-off requests and work plans. It needs the audits > audit > view permission.
• Review roles and audit activity every quarter, and whenever someone changes job.

Genesys documents the tasks; it does not prescribe a cadence. This is the rhythm QVCCS sets up with clients across the whole suite. The workforce planning routines are covered in more detail in Part 8 of the planner's handbook.

Most WEM programmes that struggle do so for reasons the technology cannot fix. Genesys says it plainly in its planning guidance: gaining buy-in at all levels is critical, and the WFM team needs real authority over scheduling and agents' time.

1. Design for the routing you have: consolidate queues where you can, and settle the queue and skill design before building planning groups.
2. Treat every WEM action on CX 1 or CX 2 as a licence decision, and check roles before go-live.
3. Give every kind of work a coded place in the schedule, including quality, coaching and learning time.
4. Calibrate before you rank: do not put quality scores on a scorecard until evaluators score consistently.
5. Use one set of definitions for service level, shrinkage and work time across planning, quality and operations, agreed in writing.
6. Tell agents what the tools show them, and repeat it whenever the rules change. Explain why auto-approval declined something, and change the rule if it is wrong.
7. Protect team leaders' time for coaching and adherence conversations; a number shouted across the floor changes nothing.
8. Use monitoring, analytics and gamification under clear policies that agents know about, within UK and European rules.
9. Check capability and limit questions against Genesys's own documentation before you rely on them; it changes with every release.