Short answer
Put the call on hold if you will resume it yourself shortly. Park it when the person who should take it is in the warehouse or on another floor without a fixed desk: it sits in a slot with a code that any authorised user retrieves from another phone and, if nobody does, it returns to whoever parked it. Transfer it when you know the destination and it is available.
Key verification: Park a test call, do not pick it up and check that it returns to reception within the configured time.
Sources and limitationsPut the call on hold if you will return to the same conversation yourself shortly. Park it when you do not know which phone the other person will pick it up from: the call sits in a slot with a code, any authorised user can retrieve it by dialling that code and, if nobody does, it returns to whoever parked it. Transfer it when you already know which extension or person should take it and they are available.
What each party sees and hears
| Action | The caller | The person handling it | Who can resume it | If nobody resumes it |
|---|---|---|---|---|
| Hold | Hold audio or silence, depending on configuration | Their line stays busy with the paused call | Only the person who put it on hold, unless shared features exist | Depends on the system; it may keep waiting |
| Park | Whatever the system plays in the slot | Their line is freed and they receive a code | Any authorised user who dials the code | Returns to whoever parked it after a set time, in systems such as Teams |
| Transfer | Hold audio or ringing until the destination answers | Leaves the call once it is completed | The chosen destination | Follows the destination's no-answer route |
The practical difference is in the third column. On hold, the call stays tied to your desk; if the person who needs it is in the warehouse, you cannot move with it. Parked, the call sits in a shared place and is picked up by whoever reaches the nearest phone. Exactly what the waiting caller hears is not stated on every page consulted, so it must be checked in a test.
CloudTalk describes hold as pausing the call for both sides, distinct from muting the microphone and from transferring: CloudTalk call controls, consulted on 22 October 2026. The comparison between muting and holding is in mute versus hold, and how to pass a conversation to someone else is in attended or blind transfer.
Slots, codes and who retrieves the call
In Microsoft Teams, parking generates a pickup code. The default range runs from 10 to 99 and can be extended up to 10-9999; codes are assigned in order and start again when they reach the end. The feature is off by default, requires Enterprise Voice users and a call park policy; if the person parking and the person retrieving do not have the same policy, retrieval fails. This is set out in the Teams call park admin guide, consulted on 22 October 2026.
In the RingCentral app, the public park location is generated automatically between *801 and *899 and can be shared by chat or text message; another person retrieves it by dialling that extension. Source: RingCentral call park guide, a 2023 document consulted on 22 October 2026. Confirm with the provider whether your plan uses public or private locations and whether that range still applies.
Maximum time, return and announcements
Teams lets you set between 120 and 1,800 seconds before a parked call rings back on the phone of the person who parked it; the default is 300. The Teams user help summarises it like this: if nobody picks it up within five minutes, it rings again. For RingCentral, the guide cited does not state the time limit, so you need to ask for it in writing.
The announcement is the other half of the procedure. Microsoft's examples include a receptionist announcing the code over the public address system for someone on a factory floor and an agent posting the code in a Teams channel so a specialist can pick it up. Over the public address system, announce only the code and the recipient, never the customer's name or the reason for the call, because anyone nearby can hear it. In chat, use an agreed channel so the notice does not get lost in a private conversation.
Decision table
| Situation | Action | Why |
|---|---|---|
| You need to look something up and you will come back yourself | Hold | The conversation stays with you |
| You know which extension should take it and it is available | Attended transfer | You introduce the case before handing it over |
| Clear destination, simple case and a configured no-answer route | Blind transfer | You free the line without waiting |
| The person is in the warehouse or on another floor without a fixed desk | Park and announce | They pick up the call from the nearest phone |
| You are switching devices, for example from mobile to desk phone | Park | You retrieve the call yourself on another device |
| You do not know whether anyone can take it in the next few minutes | Offer a callback | You avoid a wait that may end in abandonment |
Configuration to ask for
- Which users can park and retrieve, and whether they share the same policy or group.
- Range of slots or codes and the maximum number of calls parked at once.
- Time before return and the return destination: the person who parked, reception or voicemail.
- Audio the caller hears while parked and whether it matches the hold audio.
- Phones in shared areas that can dial the code, including the warehouse.
- Announcement channel: integrated public address, paging group or chat channel.
- Call logging: which user appears as the recipient after pickup.
Warehouse and shared-area extensions should be in the extension directory with a named owner.
Fictitious exercise: a reception desk with a warehouse and a first floor
Invented company: a distributor with reception, a warehouse and offices on the first floor. In the busiest hour, reception parks up to 8 calls for people without a fixed desk. A warehouse operative takes up to 90 seconds to reach the nearest wall phone.
- Return time: it must exceed the walking time with a margin. With 90 seconds of walking, 180 is chosen, within the 120 to 1,800 range that Teams allows.
- Slots: if all 8 calls coincide within the same 180-second interval, 8 free codes would be needed at once. The default range of 10 to 99 offers 90, so there is plenty.
- Worst case for the caller: 180 seconds parked and 20 seconds ringing at reception after the return, that is 200 seconds before speaking to someone again. Reception should then offer a callback rather than parking the call again.
Acceptance tests
| Test with your own numbers | Expected result |
|---|---|
| Park from reception and pick up from the warehouse with the code | Conversation restored and logged under the person who picked up |
| Park and do not pick up | The call returns to reception when the configured time expires |
| Pick up with a user who lacks the policy or group | Retrieval rejected |
| Listen from the calling phone while it is parked | Agreed audio, no prolonged silence |
| Announce over the public address system or in chat | The notice contains the code and recipient, without customer data |
Record the expected and observed results separately in each row. If the return or the pickup from the warehouse fails, do not roll out the procedure: use attended transfer or callbacks until it is fixed.
Sources and limitations
Documentary review: . Content type: Documentation-based guide with original exercise.
Linked sources describe the terms and capabilities each provider publishes. Examples that use fictional data are labelled in the text.
- CloudTalk call controlshelp.cloudtalk.io
- Teams call park admin guidelearn.microsoft.com
- RingCentral call park guidesupport.ringcentral.com
- Teams user helpsupport.microsoft.com
Official sources, explained calculations and clearly labelled examples. Read about our methodology and use of AI in writing.