Desk phones feel like furniture - wired in, parked on a desk, surely going nowhere. That is exactly why nobody tracks them, and why a single office reshuffle leaves the phone register describing a floor plan that no longer exists. Extensions stop matching desks, handsets get swapped with spares mid-fault, headsets and power supplies wander, and the directory becomes folklore. The fix is to treat handsets like the IT assets they are: identified, labelled, assigned, and moved on record.
What you will learn
- Why desk phones drift
- The record: extension, MAC, serial
- Labelling handsets
- Moves, swaps and hot-desking
- Spares, conference phones and refresh
- Software that keeps the register honest
- FAQ
Why desk phones drift
Phones do not get stolen so much as shuffled. The drift has four usual sources:
- Office moves and reshuffles. Twenty desks move on a Friday; the phones move with them; the register hears about none of it.
- Hot-desking. Once a desk has no fixed occupant, “whose phone is this?” stops having an obvious answer unless the register provides one.
- Silent swaps. A handset fails, a spare comes out of the cupboard, provisioning is re-pointed to the new MAC - and on paper the dead phone still sits on desk 14.
- Borrowed conference units. The meeting-room phone goes to an offsite event and returns weeks later, or never.
None of this is dramatic. It is dozens of small unrecorded events, which is why the cure is a register that captures events.
The record: extension, MAC, serial
A desk phone has three identities - the asset ID you assign, the serial the manufacturer assigns, and the MAC address the phone platform provisions against. A useful record holds all three, plus the human context:
| Field | Why it matters |
|---|---|
| Asset ID | The label number people quote - shorter and friendlier than a MAC |
| Make + model | Determines spares compatibility and firmware support |
| Serial number | The warranty and RMA reference |
| MAC address | The bridge between the physical box and the extension in the phone system |
| Extension / assignee | Personal extension and user, or a generic extension for a shared desk or room |
| Location | Site, floor, desk or room - the field a reshuffle invalidates first |
| Purchase date + price | Feeds refresh budgeting across the estate |
| Status | In use, in storage, in repair, retired - so spares are countable |
Tip: capture the MAC address at provisioning time, straight off the box label. Reading it later means crawling under a desk with a torch, which is why it never happens.
Labelling handsets
Put a QR label with the printed asset ID on the underside of the base unit - not on the handset itself, because handsets get swapped between bases, and not on the face, where it looks untidy and gets picked at. A QR code scanned with any phone camera can open the unit’s record directly, which is genuinely useful mid-reshuffle when IT is nowhere near a desk.
Two refinements specific to phones:
- Keep the extension on a separate, cheap label. Extensions change; asset IDs should not. A taped paper strip for the extension and a durable polyester label for the ID lets each live its own life.
- Label the power supply where one exists. PoE phones need no PSU, but the ones that do lose them constantly. A simple “belongs to PH-0031” label is enough.
Moves, swaps and hot-desking
The discipline that keeps a phone register honest is small: every change of place or holder is an event, not an edit.
- Personal extensions follow people. A desk move is recorded as a transfer; the history of who had the unit survives.
- Shared and hot desks own their phones. Assign the handset to the desk or room as a location, give it a generic extension, and stop pretending a rotating cast of users can be “the owner”.
- Swaps are a return plus an assignment. The failed unit is checked in with a fault note (and a warranty check), the spare is checked out to the desk. Two events, thirty seconds, register intact.
- Borrowed units get due dates. A conference phone lent for an event is a checkout with a return date, which is what gets it back.
The same event-based model covers desktop computers and monitors, so a reshuffle can be handled once, consistently, for everything on the desk.
Spares, conference phones and refresh
Spares deserve their own honesty. Count them, label them, and keep them at “in storage” status - a spares cupboard with an accurate count is the difference between absorbing a reshuffle and a panicked purchase order. Faulty units checked in with notes get warranty-claimed; unrecorded ones rot in drawers.
For planning further out, the purchase dates in the register tell you when the estate hits its refresh cycle - desk phones tend to be bought in one big batch during a platform migration, which means they all age out in one big batch too. Seeing that coming a budget year early is exactly what the register is for. For a fuller baseline of what to record across the office estate, see the IT asset inventory checklist.
Software that keeps the register honest
A spreadsheet can describe the phone estate on the day it is written. Its weakness is everything after that day: reshuffles, swaps and loans are events, and sheets do not record events - someone has to remember to retype a cell, and during a Friday desk move nobody does. The result is a register that is roughly right and precisely useless.
An asset management tool like AMPthilly records the events for you: each handset gets a profile with serial, MAC (as a custom field), supplier, warranty and documents; assignments, transfers and returns are logged with a full history; printable QR labels open the right record from any phone browser, so a unit can be re-assigned from the desk it just landed on; and the audit trail shows exactly when desk 14’s phone became desk 22’s. The free plan covers 3 users and 25 assets, no card required - enough to pilot a floor’s worth of handsets before committing to anything.
FAQ
How do I keep track of desk phones in an office? Unique asset ID and label per handset, serial and MAC on record, assignment to a person, desk or room - and every move logged as an event, especially during reshuffles.
Why record the MAC address of a VoIP phone? It is how the phone platform identifies the physical unit. With MAC, serial and asset ID in one record, you can reconcile the boxes on desks against the extensions in the system.
How should desk moves and hot-desking be handled? Personal extensions transfer with the person; hot-desk and shared phones are assigned to the desk or room. Both cases: record the move when it happens.
Do conference phones need different treatment? Assign them to their room and run check-outs with due dates when they are borrowed. They are the most-borrowed, least-returned phones in any office.
What should I do with spare handsets? Label them, count them, status them “in storage”, and make every swap a return plus a new assignment so the spares count stays true.
The takeaway
Phone registers do not fail at the desk; they fail at the move. Record each handset’s asset ID, serial and MAC once, label the base unit, assign it to a person or a place, and then guard the events - moves, swaps, loans - rather than the spreadsheet. An estate tracked that way survives any reshuffle, and “which extension is on which desk?” stays a lookup rather than a building tour.