Button Templates
Button templates are reusable layouts for a phone's programmable keys. Build a layout once — speed dials, call parking, shared voicemail, do-not-disturb — then bind it to any compatible deskphone or DECT handset instead of configuring each phone by hand.
Viewing templates
Open an account's Settings view. The Button templates card lists every template on the account by name; click a row to edit its buttons.
Creating a template
- From the Button templates card, click Add template.
- Give it a name (for example, "Reception" or "Executive") and an optional description.
- Save. You're taken to the template's detail page to add buttons.
Adding buttons
On the template detail page, click Add button and pick a purpose:
- Speed dial — one-touch dial to a number, extension, or feature code. When the destination is an extension, phones that support it also light up to show whether that person is available, ringing, or busy.
- Call parking — park a call to a numbered spot and watch that spot's occupancy from this key.
- Shared voicemail — light up when a shared mailbox has new messages, and press to listen or transfer the active call into it. Pick which shared voicemail box the key watches. On-device behavior depends on the phone model's support.
- Do not disturb — toggle do-not-disturb for the assigned user.
Each purpose has its own fields:
- Label — the text shown on the phone's screen next to the key.
- Target — varies by purpose: Number or extension for Speed dial, Parking spot for Call parking, shared voicemail box for Shared voicemail. Do not disturb needs no target.
Click a button row to edit it; use the row's delete action to remove it.
Reordering buttons
Drag the handle at the left of a button row to move it. Dropping a button on another row gives it that row's position, and the buttons in between shift one slot — the set of occupied positions stays the same, so any gaps you've left in the layout are preserved.
Binding a template to a device
Open a deskphone or DECT handset from the Devices page and use the Buttons card. (DECT bases don't expose a Buttons card — bind templates on each paired handset instead.)
- Choose a template from the Button template dropdown. Templates that wouldn't render any supported button on this device's model are hidden; empty templates (no buttons configured yet) are listed so you can bind and then fill them in.
- The Effective buttons table shows exactly what the phone will provision — template buttons merged with any per-device overrides.
To remove the layout, pick No template bound.
Per-device overrides
A bound template is shared, but a single phone sometimes needs a tweak. From the device's Buttons card:
- Add override — pick a free slot, then add a button for this phone only (or replace the template's button at that slot).
- Suppress — hide a template button on this phone. Suppressed positions are listed separately and can be restored at any time.
- Click a row to edit it. If the row is backed by an override, deleting it falls back to the underlying template button.
Overrides apply only to the one device and never change the underlying template.
Compatibility
Not every phone model supports every button type or position. When a bound template includes a button the device can't render, it appears under Won't render on this device with the reason (for example, the model has fewer keys, or the vendor doesn't support that type). The phone still provisions every button it can render; unsupported ones are simply skipped.