Pick a Cisco phone model and the user role — get a complete button-by-button Phone Button Template with Line, Speed Dial, BLF, Intercom, and Service URL assignments ready for CUCM Admin.
Phone Button Templates in CUCM are often created per user — "BobSmith_Phone_Template" — which produces hundreds of templates nobody can audit. The right pattern is one template per phone model + role combination: SEP_8841_Executive, SEP_8841_Reception, SEP_7841_CommonArea. This tool takes a model and role, applies the Cisco-aligned button convention for that role, and emits the full template — ready to paste into Device → Device Settings → Phone Button Template → Add New.
Pick a model + role, click Generate template.
Top-to-bottom on the hardware. Button 1 is always closest to the screen on 7800/8800 series.
Line, Speed Dial, Speed Dial BLF, Intercom, Privacy, Service URL, or Null.
Each KEM has 14 buttons × 2 pages = 28. Users tap the page shift key to flip.
Whenever an engineer creates per-user Phone Button Templates, the cluster accumulates 200+ templates inside a year, and Jane-leaving-for-maternity-leave becomes a 3-hour exercise of figuring out which template she had and whether it was fine to delete. The cost of that waste is real — new-hire provisioning gets slower because "which template should I copy" has no good answer.
The fix is role-based templating. You define 4–6 templates per phone model: Standard, Executive, Reception, Common Area, Call Center, Shared Workspace. Every user phone is assigned to exactly one of these. Per-user customization (a specific BLF to monitor the specific manager's line) goes on the phone, not the template. When the user leaves, you disassociate the phone from their user record and it's immediately reusable.
The role patterns this tool emits are the Cisco-field-standard assignments I've seen work for 10+ years:
Yes, changes propagate to every phone using that template at the next TFTP config reload. No phone reboot needed for most changes; Line changes do require a reset.
No — just pad unused line buttons with Null (or Speed Dial if you want them usable). Users with fewer lines can share the template.
Fixed button for executives and their assistants (one-press answer). Softkey is fine for general users who rarely use Intercom.
Service URL hits an XML service (directory, weather, tool) and displays the response on the phone screen. Speed Dial just dials a number.
Don't. BLF discloses call state to anyone near the phone. Common-area phones should have Null buttons beyond line 1.
1 line, 2 speed dials, 1 service URL (directory), Intercom disabled
5 phone buttons + 28 KEM buttons; personal line + team line + assistant BLF + Intercom to assistant + Privacy; KEM = BLF to direct reports + key customers
1 line + 4 buttons for transfer destinations; 84 KEM buttons as BLF to every office user + conference rooms + key vendors
The Network & UC Health Assessment audits every Phone Button Template, flags per-user templates that should be consolidated, and gives you a consolidation plan your ops team can execute.