Contact Center · UCCX

UCCX Wrap-up Codes Designer

Pick a vertical or CSQ type, set whether codes are mandatory, and get a clean 2-level wrap-up tree ready to paste into UCCX Admin + matching report filters.

By Faz Karim · 30 yrs Cisco UCLast updated 2026-04-20
What this tool does

Wrap-up codes are where call center insight starts (or dies)

When agents enter wrap-up codes inconsistently — or worse, skip them — your CSQ reports show activity but no outcome. This tool builds a 2-level wrap-up code tree for each vertical (sales, support, billing, healthcare, appointments) with 8–15 codes total. Too few and reports are meaningless; too many and agents guess or click the first option.

Design your wrap-up tree

Inputs

Your code tree

Pick a vertical, click Generate Codes.

How to read your result

Code tree → report filters → coaching

1

Categories

Top-level grouping. 3–5 categories max.

2

Codes

2–5 codes per category. Total 8–15.

3

Outcomes

Each code maps to "resolved" / "escalated" / "abandoned" for reporting.

Deep dive

Mandatory vs optional: the dropdown that kills data

Make wrap-up codes mandatory. The "let agents skip if in a rush" compromise means 60% of calls get coded "Other" or don't get coded at all, making First-Call Resolution reporting useless. If you're worried about forcing it on agents, limit the tree to 8 codes — short lists get coded accurately.

Design mistake to avoid: creating a code for every possible thing a caller says. Wrap-up codes describe why the agent handled the call, not what the caller said. "Password reset", "Account unlocked", "Service outage investigated" are good. "Customer asked about pricing" is too granular — use "Sales inquiry" instead.

Pair wrap-up codes with Not Ready reason codes for a complete picture. Not Ready reasons explain why an agent went offline; wrap-up codes explain what they resolved. Together they tell you both capacity (Not Ready) and productivity (wrap-up).

FK
Faz Karim30 years Cisco Network · UC · Data Center · LinkedIn
FAQ

Common questions

How many wrap-up codes are too many?

Above 15 and agents stop coding accurately. Target 8–12.

Can codes be CSQ-specific?

Yes — UCCX supports assigning wrap-up code lists per CSQ. Use this if Sales and Support have different outcomes.

Where do I import these?

UCCX Admin → Subsystems → RmCm → Wrap-up Data → Add New. One entry per code.

How do codes show in reports?

CUIC "Contact Service Queue Activity Report" shows code distribution. Custom reports can group by code.

Worked examples

Three vertical wrap-up trees

IT helpdesk

Support CSQ, mandatory codes.

10 codes in 4 categories: Password/access, Account, Device, Escalated to L2.
FCR metric derived from "Resolved on first call" subcode.

Healthcare scheduling

Appointment booking, mandatory.

9 codes: Appt booked, Appt changed, Info requested, Transferred to clinical, Patient refused.
"Transferred to clinical" flags calls needing nurse triage; HIPAA requires.

Sales inbound

Warm lead intake, optional codes.

8 codes: Qualified lead, Unqualified, Existing customer upsell, Callback scheduled, Competitor research, Wrong number.
"Qualified lead" feeds CRM pipeline; optional acceptable since Sales CSQ is small.
Sources verified against current Cisco guidance

Citations

Related tools

You might also need

No one codes their calls?

Our UC Modernization Sprint includes wrap-up rollout + agent training + QA coaching playbook.

$25K–$75Kturnkey
Book a 30-min call →Or email info@famoustec.com