Skip to content
English - United States
Go to website
  • There are no suggestions because the search field is empty.

Plan callback: music on hold, timeout and overflow

Calculate the timing dependencies between callback eligibility, music on hold, queue timeout and exception handling.

Callback timing must be planned as one sequence. A valid eligibility threshold does not help if the queue times out before the callback prompt can be played.

Timeline showing callback eligibility, remaining music on hold, prompt and queue timeout

Allow enough time for the complete sequence

  1. The caller meets at least one callback condition.
  2. The current music-on-hold file finishes.
  3. The callback prompt plays and the caller makes a choice.
  4. The callback request waits for an agent, and the agent answers.

The queue timeout must be longer than this combined sequence. Microsoft gives a clear failure example: with callback eligibility after 60 seconds, a 120-second queue timeout and the default two-minute music-on-hold file, the prompt is never offered.

Dependencies between music on hold, eligibility, timeout, overflow and agent availability

Planning checklist

  • Measure the complete duration of the music-on-hold file; the prompt waits until it ends.
  • Choose thresholds that match real queue capacity and expected wait.
  • Leave time after the prompt for an agent to become available and answer.
  • Check overflow and no-agent rules so they do not remove the request earlier.
  • Test with a public E.164 number and record the actual timestamps.

Read Microsoft's guidance about callback and call queue timeouts, music on hold and exception handling.

Part 2 of 3 in Callback in Microsoft Teams

Previous topic: Understand callback and when it is offered

Continue with: Troubleshoot callback in a call queue

Also relevant: Configure callback in VoiceQ365 Call Flow Designer