Use when the user asks to prepare a coaching session, 1:1, or performance review for a contact-centre agent — e.g. 'prep coaching for Anthony for the last 4 weeks', 'do a coaching brief on Amelia', 'run a 1:1 prep for Agent X', 'coaching report for Jane'. Produces a self-contained HTML brief covering performance vs targets, peer comparison, QA scores, sentiment, adherence, wrap-up discipline, top flagged calls, and a recommended top-3 coaching focus. Reads tenant-specific knobs (AHT targets, specialist roles, flagged-call thresholds, output filename) from ~/.config/genesys-mcp/tenant.yaml. Requires the genesys MCP to be connected; run the genesys-tenant-setup skill first if the tenant config doesn't exist yet.
Use when the user asks for a contact-centre daily brief, morning brief, daily standup data, or 'what happened yesterday' — e.g. 'daily brief', 'morning brief for yesterday', 'what happened in the CC yesterday', 'how did we go yesterday', 'daily CC report'. Produces a one-page HTML brief covering yesterday's KPIs vs the rolling 7-day median, top flagged agents, worst routes (queues with SL drops), repeat-caller hotlist, and adherence flags. Reads tenant-specific knobs (flag thresholds, comparison window, output filename) from ~/.config/genesys-mcp/tenant.yaml. Requires the genesys MCP to be connected; run the genesys-tenant-setup skill first if the tenant config doesn't exist yet.
Use when the user asks to generate a contact-centre report for a period — e.g. 'do the monthly CC report for May', 'run the contact centre deep dive for last week', 'CC report for April 2026', 'pull a Genesys workforce report for this week'. Produces an HTML report with funnel, themes, repeat callers, workforce, and recommended actions. Reads tenant-specific knobs (brands, AHT targets, WFM unit, pre-break presence, output filename) from ~/.config/genesys-mcp/tenant.yaml. Requires the genesys MCP to be connected; run the genesys-tenant-setup skill first if the tenant config doesn't exist yet.
Use when the user asks for a contact-centre workforce history, headcount trend, joiners and leavers, tenure trend, or 'who was on the floor in [past quarter]' — e.g. 'workforce history report', 'headcount per quarter for the last 3 years', 'who joined and left each quarter', 'average tenure trend', 'first and last active date per agent'. Produces an HTML report with three sections: (1) active-agent headcount + joiners + leavers per quarter, (2) average and median tenure trend per quarter, (3) per-person first/last active table flagging joiners and leavers. Backed by the v1.12 user_activity_history tool which reconstructs each user's first/last handled-interaction date from Genesys analytics across active + inactive + deleted users. Reads tenant timezone + output knobs from ~/.config/genesys-mcp/tenant.yaml. Requires the genesys MCP to be connected.
Use when the user wants to verify the MCP's numbers still match the Genesys 'Performance' UI — e.g. 'reconcile the MCP', 'validate the numbers for last week', 'is the MCP still matching the UI', 'check the MCP is correct', 'run a reconciliation', 'verify monthly report against Genesys UI'. Pulls the MCP tool stack for a chosen period (default: last completed week) and writes a Markdown checklist of side-by-side comparisons (MCP value vs Genesys UI navigation path), so a human can click through and tick each row off. Run before each release and after any material refactor — belt-and-braces over the pytest suite.
Use when the user wants to set up the tenant config for the genesys-mcp skills (cc-monthly-report and any future tenant-aware skills) — e.g. 'set up genesys mcp for my tenant', 'configure cc-monthly-report', 'I cloned the genesys-mcp repo, what now', 'create the tenant.yaml'. Auto-discovers what it can from the read-only MCP (queue naming pattern, brand list, WFM management units, pre-break presence, specialist roles), conducts a guided interview for the rest (tenant display name, AHT targets, output filename), and writes ~/.config/genesys-mcp/tenant.yaml. Requires the read-only OAuth credentials (GENESYS_CLIENT_ID/SECRET) to be set; the genesys MCP itself doesn't need to be connected.