UCaaS Renewal: Stop Pricing Every Shared Phone Like a User

Your UCaaS proposal has 620 user licenses. Your HR file has 547 employees. The vendor says the difference covers conference rooms, reception phones, break rooms, warehouse devices, and analog adapters.

Okay, cool. Which of those endpoints needs a full user license?

Do not accept “that is how it was configured” as the renewal answer. A shared phone, a named employee, a call queue, a meeting room, and an analog device do different work. They may need different license types, features, calling rights, and support. Sometimes they should not be licensed at all.

Before you reprice the renewal, separate every person, endpoint, number, and workflow. Make the license follow the requirement instead of letting the current license become the requirement.

Start with roles, not the vendor quote

Export the current users, licenses, phone numbers, devices, extensions, calling plans, add-ons, and assigned locations from the administration portal. Add the renewal proposal, current agreement, invoices, HR roster, site list, endpoint inventory, call-flow records, and support history.

Build one row for every licensed person or shared endpoint.

Field	What to record
Identity or resource account	The named user, room, workspace, common area, or device account
Person or device	Whether the license serves an employee, shared endpoint, system workflow, or analog connection
Site and physical location	Building, floor, room, desk, reception area, warehouse, or other location
Endpoint	Model, MAC address, serial number, analog adapter port, application, or no physical device
Number and extension	Direct number, extension, emergency location, or no external number
Business role	Named user, receptionist, common area, conference room, hot desk, paging, fax, door phone, or another defined use
Required calling behavior	Internal calling, external calling, voicemail, queue membership, transfer, shared line, recording, meetings, or emergency calling
Current license and add-ons	Base license, calling plan, device license, room license, contact center seat, recording, or other entitlement
Evidence	Sign-in, call, registration, configuration, or business-owner confirmation
Renewal decision	Keep, convert, reassign, remove, replace, or investigate
Owner and date	The person responsible for closing the decision

The proposal total tells you how many licenses the provider wants to renew. This file tells you why each one exists.

A phone on a desk is not automatically a user seat

Start by separating named-user phones from shared endpoints.

A named employee may need a personal identity, desktop and mobile apps, voicemail, direct number, meetings, messaging, and calling features that follow the person across devices. That is a user requirement.

A lobby phone may need one device, one extension, limited outbound calling, an emergency location, and no personal mailbox or application access. That is a shared-space requirement.

A reception phone can look shared but behave like a power-user workstation. The receptionist may need multiple lines, queue controls, presence, transfer tools, directory access, voicemail handling, reporting, or a desktop client. Calling it a common-area phone just because several people sit there can strip out needed features.

The label does not decide the license. The workflow does.

Current vendor documentation makes this distinction clear, even though each platform uses different names and boundaries. Microsoft documents its Teams Shared Space license for devices such as Teams phones in common areas and says each license enables one device when used that way. Zoom documents Common Area Licenses for non-user-specific endpoints including common-area phones, hoteling phones, Zoom Rooms, fax devices, paging devices, door-release devices, and analog telephone adapter ports. Webex describes a Workspace license for shared-use and common-area locations and limits that tier to a single device, while its professional workspace treatment supports different capabilities.

That does not mean one vendor model is better. It means “one phone equals one user” is not a safe renewal assumption.

Put every shared endpoint into a real use case

Walk the sites and administration records. Give each shared endpoint one role.

Common roles include:

Lobby or hallway phone
Reception position
Conference-room phone
Break-room or warehouse phone
Hot-desk device
Security desk or guard station
Paging endpoint
Fax or analog adapter port
Door, gate, elevator, alarm, or other operational device
Temporary project or training-room phone
Retired device that still has an account

Do not combine these into a line called “common areas.” A warehouse phone used for emergency calls has a different requirement from a receptionist handling several queues. A retired phone with a live license has no requirement at all.

For each row, confirm the physical endpoint, registration state, assigned number, emergency location, business owner, and recent evidence. Then test the functions the business still needs.

If nobody can locate the device, nobody owns the workflow, and the portal shows no useful activity, move it to an exception queue. Do not renew it through inertia.

Separate device licensing from calling rights

This is where quote reviews get messy.

The base treatment for a shared device may not include every calling or workflow capability you need. External calling, voicemail, queues, recording, paging, SMS, analytics, or contact center features may sit in separate licenses or add-ons.

Microsoft’s common-area phone setup documentation, for example, separates the shared-device treatment from the PSTN connection choice and notes that additional calling-plan licensing may be needed depending on how the organization connects to the telephone network. Zoom’s common-area support documentation distinguishes minimal common-area capability from higher licensing needed for features such as auto receptionists, call queues, voicemail, and IVR. Webex publishes a feature table that separates its user and workspace license types.

Ask the provider to map each proposed charge to the exact required behavior. “Voice license” is not enough.

For every shared endpoint, require written answers to these questions:

What base license is assigned, and why?
What calling service or usage plan sits behind it?
Which features does this role require that the shared tier does not include?
Does the endpoint need a direct number, or will an extension work?
Does it need voicemail, queue membership, recording, texting, meetings, or an application login?
Is a room, workspace, analog, or common-area license available for this use?
What changes if several people sign in rather than one resource account staying signed in?
Which emergency-calling configuration and location record applies?
What hardware, firmware, or certification limits affect the license choice?
What happens to the number, configuration, and device if the license changes?

A cheaper license that breaks the workflow is not savings. A full user seat assigned to a phone that only calls the front desk is not control.

Reconcile licenses, devices, accounts, and numbers separately

Run four counts:

Licensed identities and resource accounts
Physical and soft endpoints
Assigned phone numbers and extensions
Required business roles and workflows

This catches renewal errors such as:

A conference room has both a user seat and a room or workspace treatment.
An analog port was disconnected while its license and number stayed active.
A receptionist needs advanced controls but was placed on a limited common-area tier.
A device moved sites without updating its emergency location.
A number is preserved for business reasons but attached to the wrong license.

Test before you convert at scale

Do not change 80 shared phones on a spreadsheet and hope the call flow survives.

Choose a small sample: one lobby phone, one conference room, one receptionist or shared desk, one warehouse device, and one analog endpoint if you have them.

For each sample, record the current state, proposed license, required functions, test owner, and rollback step. Test inbound and outbound calls, transfers, emergency calling configuration, caller ID, queue behavior, voicemail, shared lines, directory access, sign-in, device management, failover, and any feature the role depends on.

Use the provider’s current documentation for the exact platform and contract. Product names and entitlements change. Microsoft renamed its Teams Shared Devices license to Teams Shared Space in April 2026. A renewal workbook built around an old SKU name can create confusion even when the operational need has not changed.

Get the provider to confirm the proposed mapping in writing. Compare that answer with the order form and product terms. Sales slides are weak approval evidence.

Rebuild the renewal proposal from the approved rows

Give every row one disposition:

Keep: The current treatment fits the role, features, usage, and contract.
Convert: The endpoint stays, but another license or calling treatment fits better.
Reassign: The license is needed elsewhere or belongs to another owner, site, or device.
Remove: The person, endpoint, number, or workflow no longer needs the entitlement.
Replace: Another device, platform, service design, or provider fits the requirement better.
Investigate: The location, ownership, usage, feature need, or contract treatment is still unclear.

Send the approved schedule to the incumbent and any competing provider. Ask each one to price the same requirements. If vendors quote different quantities, make them explain the mapping.

Show the approver:

Current and proposed counts by license type
Count and recurring charge by disposition
Shared endpoints that still carry user licenses
Required features that need a higher tier or add-on
Unlocated, inactive, retired, or unowned devices
Numbers and analog ports that need a separate keep-or-remove decision
Contract term, minimum commitment, notice rules, and true-down rights
Open exceptions with owners and dates

Pair this work with the UCaaS renewal roadmap test so promised features do not hide current licensing waste. If you are comparing platforms, use the broader UCaaS buyer’s guide to check implementation, integrations, support, resilience, security, and contract fit.

Renew as proposed only when the quantities trace to current roles, the license types fit those roles, add-ons map to required features, and the contract allows the changes you expect over the next term.

Renew with corrections when the platform still fits but the user, shared-device, room, analog, number, or calling-plan treatment needs to change.

Run a competitive review when the provider cannot produce a clean mapping, the contract blocks reasonable true-downs, or the proposed architecture forces expensive licenses onto simple requirements.

Your renewal should answer one basic question for every charge: who or what uses this, and what breaks if we remove it?

If the answer is vague, the line is not ready for another term.

If your UCaaS agreement is approaching renewal, request a Contract and Spend Risk Review. Bring the agreement, proposal, invoices, license export, endpoint inventory, number inventory, site list, and call-flow requirements. Catch Advisors will help you decide what to keep, convert, reassign, remove, or compare before you sign.