Voicemail · Unity Connection

Class of Service Designer

Pick the user roles you support — Standard, Executive, Department, Restricted — and get ready-to-build COS templates with feature flags, message length, retention, and fax/transcription settings.

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

Three COS profiles beat thirty

Unity Class of Service controls every feature a subscriber can touch — max message length, retention, fax access, transcription, outcall notifications, web inbox. Most deployments end up with 15+ COS profiles because one-off exceptions get their own. This tool emits three to five clean COS templates (Standard, Executive, Department, Restricted, Kiosk) that cover 95% of real subscribers. Build these first, migrate users to them, delete the rest.

Pick the profiles you want

Inputs

Your Unity COS templates

Pick your roles, click Generate COS templates.

How to read your result

One COS per role, assigned via user template

1

Create COS

Class of Service → Class of Service → Add New, fill in per template.

2

Link to user template

User Templates → Edit → Class of Service → pick the right one.

3

Reassign existing users

Bulk Administration → Import/Update Users → change COS in batch.

Deep dive

Why COS sprawl happens and how to stop it

Start with five COS objects — more is almost always worse. The usual failure mode is creating a one-off "COS_John_Smith" for an exec who needs extended retention, then "COS_Sales_Exec" when it happens to sales, then "COS_Board" when the board asks. Five becomes fifty in two years. Each exception should instead live on the subscriber directly (via Per-Subscriber overrides) or in an existing COS that's broad enough.

Executive COS should allow: long message retention (90 days), transcription, outcall notifications (important callers only), longer max message length (600 seconds — they get long messages). Executives rarely touch the web inbox but often rely on SMS notification of urgent voicemails. Standard COS should be: 30-day retention, 300-second max, transcription off by default (it's a per-mailbox cost on some Unity editions), outcall for their own devices only.

Restricted COS is for contractors, kiosk phones, and shared-desk users who should have minimal capability. 7-day retention, 120-second max, no transcription, no outcall. Don't skip this — giving contractors the same COS as employees creates audit friction.

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

Common questions

How many COS should I have?

3–5. More is harder to maintain; fewer leaves no room for role-based restrictions.

Do COS changes apply immediately?

Yes — new calls use the new COS. In-progress messages retain their original retention.

Can I assign COS in bulk?

Yes. Bulk Administration → Users → Update Users CSV import.

Does COS affect the end-user web inbox?

Yes. Web Inbox access, IMAP access, single-inbox (Exchange sync) are all COS-controlled.

Worked examples

Three realistic COS maps

Corporate HQ, 500 users

Standard for 450, Executive for 35, Department for 12, Restricted for 3.

4 profiles. Average user touches 1, IT manages 4 total.
Less is more. Resist the temptation to create per-team.

Medical clinic, 60 providers

Provider COS (HIPAA retention = 90 days), Staff COS (30 days), Department COS.

3 profiles. HIPAA-driven retention separation.
Compliance drives retention delta; no need for exec/staff split here.

Call center, 200 agents

Agent COS (no outcall, no transcription, 7-day retention), Supervisor COS, Admin COS.

3 profiles. Agent retention tight to stay inside storage budget.
Call centers blow up Unity storage faster than any other vertical.
Sources verified against current Cisco guidance

Citations

Related tools

You might also need

COS audit + consolidation?

Our UC Modernization Sprint audits your existing Class of Service sprawl, consolidates to 3–5 profiles, and migrates users turn-key.

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