Customizable Park Location Timeouts and Routing Destinations
Currently, when a call is placed in a Park Location, the system uses a global or fixed timeout. Once that limit is reached, the call typically rings back to the user who parked it.
I am requesting the ability for administrators to customize the Park Location timeout duration and define a specific destination for the call once that timer expires (e.g., sending it to a Call Queue, an Auto-Receptionist, or a specific Extension), rather than just the original initiator.
Use Case / Business Impact
Flexibility: Different departments have different needs. A Warehouse might need a 5-minute park window, while a Front Desk might need a 2-minute window.
Improved CX (Customer Experience): If the person who parked the call is busy, the call currently "loops" or rings back to a busy station. By routing it to a secondary Queue or Operator after the timeout, we ensure the caller is never left stranded.
Operational Efficiency: Reduces dropped calls and ensures that "forgotten" parked calls are automatically handled by the next available resource.
Suggested Functional Changes
Timer Settings: Add a numerical field (in seconds or minutes) within the Park Location settings.
"If No Answer" Routing: Add a dropdown menu for "When time limit is reached, route call to:" with options for:
Original Initiator (Default)
Specific Extension/User
Call Queue
Voicemail