BLF and Call Park: What Every Operator Needs to Know
BLF tells your team who's available, who's ringing, and who's on a call. Call park lets anyone pick up a held call from any seat. Together they define how well a phone system handles shared inbound traffic.
What BLF is
BLF stands for Busy Lamp Field. It's a panel that shows the status of other extensions in real time. Who's available. Who's on a call. Who's ringing.
The name comes from physical desk phones, where the BLF was a row of colored lights, one per extension. The idea is the same in a softphone: you glance at the panel and know, without asking anyone, whether a colleague is free to take a call or handle a transfer.
For teams that handle shared inbound calls, a BLF panel isn't a convenience feature. It's how agents make routing decisions without calling out across the room or slacking each other to ask who's free.
The three states that matter
A BLF panel that does its job shows three distinct states for each extension:
These three states are different in ways that matter. Ringing means someone might need help. On a call means they're occupied. Available means they can take work now.
Why most softphones only show two
Most softphones collapse "ringing" and "on a call" into a single "busy" state. Agents see the same indicator whether a colleague's phone is ringing or they're 20 minutes into a call.
This is a technical shortcut, not a deliberate design choice. Showing ringing state correctly requires the softphone to interpret SIP presence notifications at a finer level of detail. Many skip this and show "busy" for anything that isn't available.
The result: agents can't tell if a ringing call needs backup. They see red, assume the person is occupied, and route elsewhere. The call that needed one more ring to be answered gets missed.
What call park is
Call park puts a call on hold in a shared slot that any agent can pick up from their own seat. Instead of a blind transfer to an extension, you park the call to slot 701. Any agent who sees that slot 701 is occupied can pick it up without the caller knowing anything happened.
This is different from a transfer. A transfer sends the call to a specific extension. If that person is busy, the caller waits or gets voicemail. Call park sends the call to a neutral slot. Any available agent can retrieve it.
Call park is useful in any environment where calls move around during handling. A receptionist parks an inbound call for a department. An available agent in that department picks it up from their own desk. No blind transfers. No callbacks. No "can you hold while I find someone?"
Why these two features work best together
BLF and call park are separate features at the protocol level. In practice, they're the same workflow.
A call comes in for someone who's already occupied. You see on the BLF panel that they're on a call. You park the inbound call to slot 701. Another agent sees on the BLF panel that slot 701 is occupied and picks it up. The caller never knew anything happened.
If the BLF panel doesn't show ringing state, you're guessing about who needs backup. If the BLF panel doesn't show park slot occupancy, agents have to ask which slots are taken. Both gaps create confusion and missed calls.
What to look for when evaluating
If you're evaluating a softphone for a team that handles shared inbound calls, these questions cut through the feature list quickly:
- Does BLF show three states or two? Can you see the difference between ringing and on a call?
- Do park slots appear in the BLF panel alongside extension presence?
- Does the BLF update in real time, or is there a noticeable lag?
- How many BLF keys does it support? Eight or sixteen keys doesn't cover a team of twenty.
- Does BLF recover automatically after a network interruption, or do agents have to refresh?
A softphone where BLF actually works
Stylish Softphone shows three presence states, updates in real time, displays park slot occupancy in the BLF panel, and supports up to 100 BLF keys per user. Watch it in the live demo.