Call park is the feature you use when a call needs to land at "whoever is free" instead of a specific extension. Receptionist picks up, parks the call on slot 701, walks over to the warehouse and yells "call on 701," warehouse manager picks up from any phone in the building. That is the whole feature.
What it actually is
A parked call lives in a virtual slot, not on a specific phone. The slot is a number (701, 702, 703 in a default configuration) that any user on the system can dial to pick the call up. The original phone that parked it is free to do other things.
It is different from hold (which keeps the call on your phone) and different from transfer (which sends the call to a specific extension). Park is for "I do not know yet which person should take this."
The history, briefly
Call park existed on legacy PBX systems for the same reason it exists now: someone in the back office picks up the closest phone instead of the one assigned to them. SIP made it easier to configure (no physical wiring of park appearances) but the user experience is identical to the one your front-desk staff already knows from any phone system built since the 1980s.
Directed vs. system-wide park
- Directed park: The receptionist chooses where to park it (slot 701, 702, etc.). The slot number gets announced or posted somewhere people can see it. Most flexible. Most error-prone.
- System-wide park: The system picks the next available slot automatically. The receptionist says "park 4" and the system tells them "parked at 704." Less flexible, less to mess up.
For offices with paging, system-wide is what we deploy. For offices where the front desk uses BLF keys to monitor specific park slots visually, directed is the right choice.
When directed is the right call
If the receptionist has a sidecar with BLF lights mapped to specific park slots, directed park gives them control. They know slot 701 is the "sales floor" slot and slot 702 is the "warehouse" slot. The labels make pickup intuitive. The cost is that the receptionist has to think about which slot to use, which is fine for an experienced operator and a problem for a new hire.
When system-wide is the right call
If the office has a paging system and the receptionist mostly says "call on 7-oh-whatever" over the speaker, system-wide is simpler. The system picks the slot, the receptionist reads the number off their phone, paging carries the message. New hires learn it in a single training pass.
How we set it up
For a typical 20-person office on our Phone Service:
- We provision 5 to 10 park slots (701-710) in the portal. More than 10 slots is rarely used in practice; calls just sit.
- On the receptionist's phone, we program a BLF key per slot so they can see at a glance which slots are occupied and pick up with one button.
- We set a park timeout. After 90 seconds, the parked call rings back to the phone that parked it. This is the most important step and the one most setups skip. A parked call with no timeout becomes a forgotten call becomes an angry caller.
- If you use paging (a ceiling speaker system or a paging zone over the phones), we link park to page so "park and page" is a single workflow.
Hardware that supports it well
Any of our standard Yealink and Polycom desk phones support park slots with BLF lights. Specifically:
- Yealink T54W or T57W as a receptionist phone with park slots on the primary key page.
- Yealink EXP50 sidecar if the receptionist also monitors a wall of staff extensions; reserve a row for park slots.
- Polycom VVX 450 with VVX EM50 sidecar for the same use case in a Polycom shop.
Models, prices, and provisioning details on the hardware page.
Paging integration in detail
Most offices that use park heavily also have either a ceiling-speaker paging system or paging zones programmed through the phones themselves. The phones can act as overhead speakers via the paging codec, or we can integrate with an existing Bogen or Valcom system. Park-and-page becomes a single workflow: receptionist parks the call, system picks slot 704, receptionist hits the page key and says "call on 704 for sales." Tech in the back room picks up from the nearest phone.
Where call park earns its keep
Front desks with field staff
Receptionist takes a call for a leasing agent who is showing a unit. Park the call, page the agent, agent calls back into the slot from their mobile app when they are free. The caller waits with hold music instead of getting bounced to voicemail.
Service shops
HVAC dispatcher takes a call for a tech who is on a roof. Park, page over the radio, tech picks up from the shop phone when they come down. Common pattern with ServiceTitan customers and other field service shops.
Multi-floor offices
Anywhere people move around the building during the day. Park-and-page beats hunting through hunt groups.
Medical and dental practices
Front desk takes a call for the doctor who is mid-procedure. Park, walk back, signal the doctor when they are between patients. Common in dental practices and healthcare clinics where the desk staff cannot just transfer a call to a phone that is unattended.
Property management offices
Maintenance call comes in for a tech who is on a service call. Park, page, tech picks up from the shop or from a Pro Mobile eSIM. Tenants do not get bounced to a voicemail nobody checks. The pattern works with AppFolio, Buildium, and Rent Manager for tenant lookup before the park.
Legal firms with paralegals
Receptionist takes a call for an attorney who is meeting with a client. Park, walk to the office door, attorney finishes the conversation and picks up the parked call when they are ready. Common pattern in legal firms where blind transfers to a busy attorney's phone would just generate voicemail.
Where it does not work
- Remote-first teams. If half your people are home, the "page the office" piece falls apart. Use direct transfers to mobile apps instead.
- Caller patience. Park is hold with extra steps. If the caller is going to wait, they need hold music, and they need that 90-second timeout to bring them back to a human, not to die in voicemail.
- Forgotten calls. Without the timeout, somebody walks away from a parked call and the caller hangs up convinced you are amateurs. The timeout is not optional in our configurations.
- Open-plan offices with no paging. If the receptionist has to walk across an open floor to flag someone, the noise carries to the caller. Quiet handoffs need either silent presence/BLF on a screen or actual paging zones, not yelling.
- Privacy-sensitive calls. A parked call is pickable by anyone with extension privileges. For attorney-client matters or HIPAA-sensitive calls, use attended transfer to a specific extension instead.
Call park vs. its alternatives
- Hold: Same phone resumes the call. Use for 15-second pauses.
- Blind transfer: Sends to a specific extension, no introduction. Fastest, riskiest.
- Attended transfer: You introduce the call before connecting. Use when context matters.
- Park: Anyone can pick it up. Use when you do not yet know who should.
- Hunt group / queue: Same idea as park but automated. If you find yourself parking calls to the same group of people every time, build a queue.
When to use each, by example
A dental practice front desk takes a call for the hygienist who is in the back. Park (anyone in the back can grab it) is right if multiple hygienists could handle the call. Attended transfer is right if you know which hygienist needs it. Queue is right if calls for hygienists come in constantly and you want them distributed automatically.
A property manager takes a call for "maintenance." Park is wrong unless you know a specific tech is available. Queue is right because any of three techs can take it, and the queue routes to whoever is free first.
A real estate brokerage takes a buyer-lead call. Park is wrong because no specific agent is expecting the call. Queue (round-robin to available agents) is right because the lead should go to whoever is reachable.
Common mistakes with call park
- No timeout. Number one mistake. Always set the 90-second ring-back.
- Too many park slots. 30 park slots on a 10-person office is clutter. Five or ten is usually plenty.
- Park slots without BLF lights. The receptionist cannot see which slots are occupied, so they guess. Always pair slots with BLF keys.
- Using park instead of a queue. If you find yourself parking calls to the same group every time, build a hunt group or queue. Park is for ad hoc, not for routine routing.
- Paging the whole building when only one zone is needed. Configure paging zones (warehouse, sales floor, second floor) so park-and-page does not announce to everyone.
- Not training staff on the timeout behavior. When the ring-back comes, the receptionist needs to know what to do. Brief everyone.
- Letting the park slot label drift from the actual workflow. If slot 705 is labeled "warehouse" but the warehouse moved to a different building, the label is a trap. Audit park labels annually.
- Mixing park and intercom on the same keys. Different functions, different feedback. Pick one purpose per key.
What to ask before configuring it
- Who needs to be able to grab parked calls? (Anyone? A specific group?)
- How will people be alerted that a call is parked? (Paging, BLF, intercom?)
- What is the timeout and where does the call go if nobody picks up?
- Are park slot BLF keys on the receptionist's primary page or on a sidecar?
- Are paging zones configured separately from park, or linked?
- Do you have any privacy-sensitive call types that should not be parkable?
- How will you train new hires on the park-and-page workflow?
How call park fits with the rest of your call flow
Call park is one tool in a routing toolkit that includes IVR, queues, hunt groups, transfer, and direct dial. Mature configurations layer them: callers hit the IVR first, route to a queue or directly to a person, and park is the safety net when the intended recipient is not at their desk. Built correctly, the caller never knows park was involved; they just wait briefly and the right person picks up. Built poorly, park becomes the place where calls go to die.
A worked example: warehouse and storefront
A 25-employee distributor with a front-of-house showroom and a warehouse in the back. Receptionist at the front desk has a Yealink T54W with an EXP50 sidecar. Park slots 701-705 are programmed as BLF keys on the right side of the sidecar, labeled "Warehouse," "Showroom," "Manager," "Sales," and "Generic." Paging zones are configured: zone 1 is the warehouse ceiling speakers, zone 2 is the showroom, zone 3 is the manager's office intercom, zone 4 is all-page.
A customer calls asking about a special order. The receptionist takes the call, sees nobody at the sales desk, parks the call at slot 704 (the sales park slot), and pages zone 2: "Sales call on 704." A salesperson on the showroom floor walks to the nearest phone, dials 704, and picks up the call. The receptionist's phone shows slot 704 going from red back to green. Total time from inbound ring to salesperson on the line: under 30 seconds.
Without park, the same scenario looks like: receptionist transfers blind to the sales hunt group, all the sales phones ring, the salesperson on the floor cannot get to a phone before the timeout, the call rolls to voicemail. The customer leaves a message and the deal cools.
Where to start
Call park is included with every seat on our Phone Service. There is no upsell here, just a configuration that has to be done right. Tell us how your front desk routes calls today and we will configure park slots, BLF keys, and timeouts before you go live. Hardware specs at hardware; full pricing at pricing.