Naming labels across countries

The name is the only thing colleagues read out in the number overview. The capability is not shown there — only the name. In an estate spanning several countries and several platforms, the name is therefore what carries the entire structure.

A convention that works

Build the name from two or three parts, with the broadest part first.

• Country · Purpose — Example: DK · Users
  SE · Queues & attendants · Why: Searching for DK · gathers the whole country. Sorting by label name groups them on its own.
• Country · Platform — Example: DE · Legacy PBX
  DK · Contact centre · Why: Makes it visible which numbers do not belong in Teams Phone.
• Country · State — date — Example: DK · Quarantine — release 2027-01
  DE · Migration wave 2 · Why: Temporary states get an expiry date built into the name, so they do not become permanent by accident.

Principles

• Country code first — Good: SE · Users · Less good: User numbers Sweden
• Say what the numbers are for — Good: DK · Queues & attendants · Less good: Group 2
• Name the platform, not "other" — Good: DE · Legacy PBX · Less good: Other system
• Date on temporary labels — Good: DK · Quarantine — release 2027-01 · Less good: Wait a bit
• Leave out personal names — Good: DK · Reserved — Aarhus branch · Less good: Ask Peter

Rule of thumb. The name is good enough if a colleague in another country can read it in the number overview and understand whether they may use the number — without asking anyone.

Agree on ownership

Agree within the team who may create labels, and stick to the convention. Twenty labels with overlapping meanings are worse than none. At the same time, set a fixed review — quarterly, for instance — where quarantine labels, migration waves and reservations are released again.