Busy Lamp Field is the row of little lights on a desk phone that tells the receptionist whether you are on a call. It is not new technology, it is not complicated, and it solves a real problem: stop transferring calls to people who are already on the phone.
What BLF actually does
A BLF key is a programmable button on a SIP desk phone that is subscribed to another extension's state. Idle, the light is off or green. On a call, the light goes solid red. Ringing, it blinks. One button press on a lit key transfers the active call to that extension, or initiates a call to it if you are not already on one.
On the phones we deploy most often, the math is concrete:
- Yealink T54W: 10 line keys plus 17 paged side keys with full BLF support.
- Yealink T57W: 29 BLF keys across the touchscreen pages.
- Polycom VVX 450: 12 line keys, expandable with a sidecar to 28 or 84.
- Expansion modules (EXP50, VVX EM50): 60 more keys per module if you need a wall of extensions for a front desk.
Specifications and pricing on each model live on the hardware page. We provision them out of the box, so the phone arrives at your office knowing its extension and its BLF map.
How the SIP subscription works under the hood
BLF is a SIP SUBSCRIBE/NOTIFY relationship. The desk phone subscribes to another extension's dialog state. Our platform sends NOTIFY messages whenever that extension's state changes. The light updates within a fraction of a second. There is a soft limit on how many subscriptions a single phone can hold before the platform throttles updates; in practice, a single Yealink or Polycom base plus two sidecars (about 130 buttons) sits comfortably under the limit. Past that, you are in custom-build territory and we will spec it differently.
Presence vs. BLF
BLF is a SIP feature tied to the phone. Presence is a broader status that lives in our portal and in softphone apps: available, busy, in a meeting, do not disturb, on PTO. Presence pulls from calendar integrations when we set them up, so if you have a meeting on your Microsoft 365 calendar, your status flips automatically.
The two work together. The receptionist's desk phone shows BLF lights; the manager's laptop shows presence in the softphone client. Calls are still routed in real time on either signal.
Which status wins?
If a user is on an active call (BLF says red) but their calendar says "available," BLF wins. The phone is busy because the phone is busy. Presence is a layer on top, used for routing rules (do-not-disturb sends calls to voicemail, away forwards to mobile). BLF is the ground truth of whether a SIP endpoint is in a call right now.
Presence and Microsoft Teams
If your team lives in Teams, the Microsoft Teams integration mirrors presence between Teams and our platform. A user who flips to "do not disturb" in Teams shows DND on the desk phone's BLF light, and inbound calls follow the DND routing rule. This is the closest thing to a single status across both worlds.
The workflows where this matters
Front desks with field staff
This is the original use case and still the best one. A receptionist with a 28-button sidecar sees the entire team at a glance and never transfers a call to someone who is already on the phone. For law firms and medical practices, that one feature pays for the phones.
Specific build: a Yealink T54W on the receptionist desk with one EXP50 sidecar. 10 line keys on the base phone for the receptionist's own lines and the firm's main DIDs. 60 BLF keys on the sidecar mapped to every attorney, paralegal, conference room phone, and the breakroom. Cost: under $500 for the base and sidecar combined. Time saved per dropped transfer: roughly 90 seconds of caller annoyance per attempt.
Property management with leasing agents in the field
When your leasing team is split between the office and showings, presence on the mobile app tells the office who is reachable. We see this with AppFolio and Buildium integrations, where presence ties into the CRM. Rent Manager users get the same routing behavior. The receptionist sees green dots in the softphone client for agents who are reachable and red dots for agents on calls or out of the office.
Real estate teams using shared lead lines
Lead routing in Follow Up Boss respects agent availability via presence. If you are on a showing with DND on, the lead goes to the next agent in the round-robin instead of bouncing to voicemail. For brokerages running shared buyer lead lines, this is the difference between a lead reaching a live agent and a lead leaving a voicemail nobody hears for 45 minutes.
Medical and dental practices with multiple operatories
The hygienist's phone shows BLF lights for the dentist, the front desk, and each operatory. When the hygienist needs the doctor for an exam, one button press pages directly without walking back to the front. For dental practices and healthcare practices this is the daily-use feature.
Sales teams running outbound
BLF on the sales manager's phone shows which reps are on calls at any moment. Whisper-coaching becomes possible without waiting for someone to finish. For inbound shared queues, presence drives the routing. For sales teams we typically deploy this alongside CRM integration so click-to-dial and call logging work in concert with presence.
Multi-location offices with a shared receptionist
A single receptionist supporting three small offices needs to see all three sites on one phone. We build the BLF map across all three location extensions and the receptionist transfers between them as easily as within a single office. For multi-location deployments this collapses what used to require three separate phone systems.
The configuration honesty
BLF keys are programmed in our portal per phone, per user. For a 20-person office, the initial setup is a couple of hours of clicking and a quick provisioning push. When people get added, moved, or fired, the keys need to get updated. Plan on revisiting the layout once a quarter.
Sidecars (expansion modules) are not free. A Yealink EXP50 runs about $130; a Polycom VVX EM50 is in the same range. If your receptionist needs to see 40+ extensions, two sidecars on one base phone is the standard build.
Provisioning at scale
For multi-location deployments (we see this with multi-location customers), the BLF map can mirror the org chart per site or roll up into a single global view. Global views are useful for executive assistants supporting officers across multiple locations. Per-site views are usually what front-desk staff actually want, because they need to see their own people, not the whole company.
The maintenance overhead
Every time someone joins, leaves, or changes role, the BLF map needs an update. For a 30-person office, that is usually a 15-minute portal change once a month. For a 200-person company, dedicate someone to the role or hand it back to us. We handle ongoing BLF map maintenance for managed-service customers as part of the seat price.
What does not work the way people expect
- BLF across federated systems. If half your team is on our platform and half is on a different VoIP provider, BLF does not bridge. Presence might, through Microsoft Teams. BLF will not.
- BLF on cell phones. The mobile app shows presence and recent activity, but the green/red light metaphor is a desk-phone thing. Pro Mobile users see presence in the app and in the desktop client, just not as a physical light.
- Presence on calendar conflicts. If your calendar lies, your presence lies. Garbage in, garbage out.
- BLF for queues. A queue is not an extension. BLF tells you the state of a single user. To see queue depth, you need the wallboard view in the portal, not a BLF light.
- BLF on shared lines. If two users share a DID via shared call appearance, BLF reflects the line state, not the user state. People expect the per-user behavior and get confused. Use it only when shared lines are genuinely required (small law firms with paralegal coverage, for example).
Common mistakes when laying out a sidecar
- Alphabetizing by first name. When Andrew leaves and Adam joins, every key shifts. Group by role or department instead.
- Mixing BLF with speed dial. The lights mean different things on the same row. Pick one purpose per page.
- Forgetting paging zones. A BLF key can also page a zone. Reserve one row for the warehouse page, the lobby page, all-page, and so on.
- Skipping the labels. Yealink and Polycom phones support paper labels and on-screen labels. Use them. A wall of unlabeled red lights is useless under pressure.
- Putting park slots and BLF on the same page. Park slots earn their own page so the receptionist knows where to look.
- Underestimating the sidecar count. A receptionist who needs to see 80 extensions needs two sidecars, not one. Order the right hardware up front; bolting on a second sidecar later is more disruptive than ordering it correctly.
What to ask before ordering hardware
- How many people does the receptionist actually need to see at once?
- Is a sidecar physically going to fit on the desk?
- Will the receptionist use the touchscreen or the hard keys more?
- Do you need wireless DECT for staff who roam the building?
- Are there shared-line scenarios (two people on one DID) where presence behaves differently than BLF?
- How often does your staff turn over? More turnover means more BLF map maintenance.
- Do you have a separate paging system or does paging happen through the phones?
A small example of the math
A 25-attorney firm with a receptionist who answers about 600 calls a week. Before BLF: blind transfers, two attempts per call on average to reach the right attorney, with about 8% of calls ending up at voicemail when the intended attorney was busy. That is roughly 48 blind-transfer voicemails per week, each of which becomes a callback chain. After BLF: receptionist sees who is on a call before transferring, walks the caller through their options if the target is busy, voicemail rate drops to about 2%. The difference is roughly 36 fewer voicemail chains per week, which is real time saved across the firm, not just at the front desk.
Pricing context for the hardware
BLF is a software feature; the cost is the phone and the sidecar. Yealink T54W base phones run in the low $200s; T57W with touchscreen runs higher. EXP50 sidecars are around $130. Polycom VVX 450 base phones and VVX EM50 sidecars price similarly. We do not mark phones up to bury margin in the seat price; the per-seat Phone Service charge is $15 or $32 per user per month and BLF is included at both tiers. If you would rather lease phones than buy them outright, we can finance the hardware over 36 months, which lands at roughly $10-$20 per seat per month depending on the model.
How BLF and presence fit into the rest of the stack
BLF is a desk-phone feature, but presence shows up everywhere: in the softphone, in the mobile app on Pro Mobile, in Microsoft Teams via the Teams integration, and in the CRM screen-pop when a call is in progress. Sales managers who never sit at a desk still see who is on a call in real time from their laptop. Dispatchers who manage field crews see presence dots in the dispatch view. The desk-phone light is the most visible expression of the same underlying state, but it is not the only one. For a frontline-heavy operation, the mobile app and softphone presence are usually more important than the BLF light at the front desk.
Where to start
If your front desk is transferring blind and getting calls bounced back, BLF is the fix and it is included with our Phone Service at no extra cost beyond the hardware. Hardware lives at our hardware catalog with the Yealink and Polycom models we provision. Tell us how your front desk works today and we will spec the phone, the sidecar, and the BLF layout before you order anything. Pricing detail at pricing.