Busy Lamp Field (BLF) is a business phone feature that turns programmable keys on a desk phone, or entries in a softphone, into status lights for other extensions. Each key shows whether a colleague’s line is idle, ringing or on a call, and pressing it typically calls, transfers to or picks up that extension. Receptionists, assistants and small teams that hand calls back and forth rely on it to route calls without guessing who is free.
At a glance
- BLF shows the real-time call status of other extensions on lights or icons, commonly idle, ringing and busy.
- Pressing a BLF key typically dials, transfers to or picks up the monitored extension, depending on the system.
- It is most used by receptionists and teams that answer for each other; expansion modules add more keys.
- Support, key counts and behavior vary by phone model, provider and platform.
- In cloud systems BLF usually runs over SIP subscriptions, so it often doesn’t work across different phone systems.
What problem it solves
Transferring a call to someone who is already on the phone wastes the caller’s time and often ends in voicemail. Without a status view, a receptionist has to announce the call, wait, and pull it back if nobody answers. In teams that cover for each other, such as a front desk, a sales group or a clinic, people also need to grab a colleague’s ringing phone without walking over.
BLF gives everyone who needs it a live view of colleagues’ lines and one-touch actions on them. It is one of the features businesses most often check when moving from an older PBX or key system to a hosted PBX or UCaaS service, because front-desk staff notice immediately if their keys behave differently.
How it works
Programming the keys. An administrator or user assigns monitored extensions to programmable line keys on a phone, to keys on an expansion module, or to a list in a softphone. Many providers let this be done from a web portal and pushed to the phones automatically.
Subscribing to status. In SIP-based systems, the phone subscribes to the call state of each monitored extension, and the phone system sends notifications whenever that state changes. On older digital PBXs, the same function was proprietary to the phone system and its handsets.
Showing status. The phone translates each notification into a light color or pattern: idle, ringing, in use, and sometimes held or do-not-disturb. Some phones also show the caller’s name or number when a monitored line rings.
Acting on it. Pressing the key does different things depending on the state and the configuration: speed-dial an idle extension, blind or attended transfer during a call, or directed pickup of a ringing extension. Some systems also use BLF-style keys to monitor shared lines, parked calls, or call queue and night mode states.
Limits. Each subscription adds load, so providers may limit how many extensions a phone can monitor. Status usually depends on all extensions being on the same system; BLF between two different platforms, for example during a phased migration, often isn’t supported without extra integration.
When it matters for buyers
- When replacing a legacy phone system. List which users depend on BLF and confirm the new system and phones support the same behaviors, including pickup and transfer.
- When choosing phones. Count the keys each receptionist needs and budget for expansion modules where needed.
- When moving staff to softphones. Check whether the softphone or UC app shows true call status and offers one-click actions, or only presence.
- When setting up a new site. Plan front-desk call flows, BLF keys and auto attendant routing together during a new office rollout.
- When migrating in phases. Expect status lights to stop working between users on the old and new systems until everyone moves.
Our hosted PBX overview covers the features to compare when moving a phone system to the cloud.
Questions to ask vendors
- Which phone models and softphones support BLF on your platform, and how many monitored extensions are allowed per device?
- Does pressing a BLF key support directed pickup, attended transfer and blind transfer, and is any feature code needed?
- Can BLF keys monitor parked calls, shared lines, queues or day/night mode?
- Do expansion modules work with your phones, and are they managed from your portal?
- Will BLF work between users on our old system and your platform during migration?
- Can we program BLF keys centrally for groups of users, and can users change their own?
How it differs from presence status
BLF shows telephone state, whether an extension is idle, ringing or on a call, and is tied to actions on phone keys. Presence in a UCaaS or team chat app is broader: it may combine call status with calendar meetings, chat activity and a status the user sets, such as away or do-not-disturb. Presence helps decide whether to message or call someone; BLF helps a receptionist move a live call in one press. Many platforms offer both, and how closely they are linked varies by provider.