Webex WFO Custom Metrics: Turning Performance Management into a Business-Outcome Scorecard

Three Webex updates landed within two days of each other at the end of October, and read together they point in one direction: Webex WFO is becoming a place where contact center operations data and business outcome data sit side by side, and where the workforce plans built on top of that data are easier to adjust. The headline change is custom metrics in Performance Management. The supporting changes — editable forecasts, multi-week shift bidding, and a tighter desktop session policy — are what determine whether the headline actually works in practice. This post walks through what changed, then focuses on the part that matters most: how to architect around it.

What changed

On October 30, Webex WFO Performance Management gained custom metrics: organizations can load their own business data — CSAT, NPS, resolution time, first contact resolution, sales conversions and similar measures — alongside the built-in measures, either by CSV upload or through an automated API. It requires at least the Webex WFO Bundle SKU plus the Enterprise Analytics 100 Interactions Add-on SKU, and users sign in through the tenant-specific URL.

The same day, the web Forecasts module became editable: users can adjust, edit and override forecast data, including copy and paste, in the workload and skill grids. Separately, administrators can now create, publish and award shift-bidding patterns spanning 2 to 24 weeks as a single bid; leaving the pattern at 1 week (or blank) keeps the previous single-week process.

And on October 29, the maximum Desktop inactivity sign-out in desktop profiles dropped from 10,000 minutes to 12 hours. Activity resets the timer, and organizations set above 12 hours — or with the timeout switched off — are moved to 12 hours automatically.

Full record for each change: custom metrics, forecast editing and multi-week shift bidding, and the desktop inactivity sign-out cap. The wider feed is on our Webex Contact Center release intelligence page, and Cisco's administrator source is What's new for administrators in Webex Contact Center (opens in a new tab).

Pattern 1: Build a business-outcome scorecard pipeline, not a one-off upload

The obvious use of custom metrics is a scorecard that stops forcing supervisors to reconcile three tools in a spreadsheet. A practical architecture looks like this: your survey platform — Qualtrics or Medallia, for example — is the system of record for CSAT and NPS; your CRM, such as Salesforce, is the system of record for conversion and revenue outcomes; resolution and first-contact-resolution figures are derived from your case or interaction records. Each source publishes a small, dated extract on an agreed cadence, and that extract — not a live query — is what loads into Performance Management through the automated API.

The integration work is less about the API call than about definitions. Before automating anything, settle three questions per metric: who owns the definition, at what grain it lands (agent, team, queue, site), and how late-arriving corrections are handled. CSAT that is re-scored when a survey response is edited, or conversions that settle days after the interaction, will quietly corrupt a scorecard if the load simply overwrites. A dated, repeatable extract with a clear restatement rule is what makes the numbers defensible in a coaching conversation.

Start with the CSV route as a pilot. Pick one team, three or four metrics, and load manually for a few cycles. That sounds unambitious, but it surfaces the real problems — mismatched agent identifiers between your CRM and WFO, survey samples too small to be fair at agent level, metrics nobody can define the same way twice — while the cost of fixing them is still low. Automate only the metrics that survive the pilot with stable definitions and a named owner.

Pattern 2: Govern forecast overrides and multi-week bids like workforce processes

Editable forecasts are genuinely useful the first time a marketing campaign, a product recall or a regional outage makes the statistical forecast wrong in a way everyone can see coming. The pattern that works: planners adjust the workload and skill grids for the known event, and the override carries a reason and an expiry — the event's end date — rather than becoming a silent permanent edit. Review overridden intervals after the fact against actuals; that comparison is how you learn whether your planners' judgment beats the model, and it is the evidence base for trusting overrides next time. Copy and paste makes it easy to propagate an assumption across days, which is exactly why the assumption should be written down where the team can challenge it.

Multi-week shift bidding, up to 24 weeks as a single bid, changes a different workflow. A single multi-week bid suits rotating schedules and seasonal patterns far better than repeating a one-week bid two dozen times, and it reduces the administrative churn of publishing and awarding pattern after pattern. Think through the downstream sync before you use it, though: an award that commits an agent's pattern for months ahead needs to reach the systems that depend on it — HRIS and payroll platforms such as Workday or UKG are the usual examples to check — and your absence and holiday processes need to know which weeks are already committed. None of that is a reason to avoid multi-week bids; it is a reason to treat the first one as a process change, not just a longer form.

Rollout notes and cautions

Sequence this in the order above: pilot custom metrics with CSV on one team, then automate the API feed once definitions are stable, because an automated feed of a badly defined metric just produces wrong numbers faster. Confirm the licensing position before promising the scorecard to stakeholders — custom metrics need the Webex WFO Bundle SKU and the Enterprise Analytics 100 Interactions Add-on SKU — and make sure users know to sign in via the tenant-specific URL, since that detail generates avoidable "it doesn't work" tickets.

The 12-hour sign-out cap deserves a communication pass of its own. Organizations that had desktop profiles set above 12 hours, or the timeout disabled, have already been moved to 12 hours. That is a sensible session-hygiene change, but it will surprise teams that leave desktops signed in across shifts — shared workstations and wallboard-style setups are the places to check first. Activity resets the timer, so genuinely active desktops are unaffected; the impact lands on idle sessions, which is precisely the point, but supervisors should hear it from you before they hear it from agents locked out mid-shift change.

None of these three changes forces a redesign. Together, though, they reward teams that treat WFO as an integration surface — survey, CRM, HRIS and payroll data flowing in with clear ownership — rather than as a reporting island. That is where the scorecard stops being a prettier report and starts changing coaching, forecasting and scheduling decisions.

Track future changes on our Webex Contact Center release intelligence page, and verify details against Cisco's source: What's new for administrators in Webex Contact Center (opens in a new tab).