On Hold Prompts: messages while callers wait
An on-hold prompt plays a short recurring message to waiting callers, but it blocks them from reaching an agent while it plays. Here are the rules that keep it from quietly inflating your hold times.
Sometimes you want a caller on hold to hear an actual message at intervals, not just music: a reassurance that they are still in the queue, or a nudge toward your website. VICIdial calls this an on-hold prompt, and it is a separate feature from your hold music. It is useful, but it has a sharp edge you need to respect.
What an on-hold prompt does
On an Ingroup, the On Hold Prompt Filename points at a short audio file that plays at a set interval while a caller waits. Think of it as a recurring spoken interruption layered over the silence or music, typically something like a thank-you-for-holding line every minute.
You control the gap between plays with the interval setting, which defaults to sixty seconds. So the prompt fires, the caller goes back to waiting, and a minute later it fires again until they reach an agent.
The blocking problem
Here is the catch, and it is a real one: while an on-hold prompt is playing to a caller, that caller cannot be sent to an agent. The connection is held until the prompt finishes. If an agent frees up mid-prompt, the caller waits out the rest of the recording first.
By default this also affects callers queued behind the one hearing the prompt. That can quietly add hold time and hurt your Service level if the prompt is long or fires often. There is a no-block option you can switch on so waiting callers behind the prompt can still be connected while it plays to someone ahead of them.
Keeping it safe
Because of the blocking behavior, on-hold prompts have strict rules:
- Keep the audio file to nine seconds or shorter.
- Set the prompt-length field to the actual length of the file, not longer.
- Turn on the no-block option so callers behind the prompt are not held up.
- Use a generous interval so the prompt is not constantly interrupting routing.
If the length value does not match the real file, or the file runs long, you will see odd routing behavior, so treat those two settings as a pair.
When to use music instead
For most messages, you are better off putting them into Music on hold rather than an on-hold prompt, because music can be interrupted the instant an agent is free and never blocks a connection. Reserve the on-hold prompt for cases where the message genuinely must play uninterrupted at intervals.
Our inbound call handling guide puts these waiting-experience settings in context, and the music-on-hold setup is the better home for most spoken messages. To trial the difference with live callers, our plans get you a working queue in under a minute.
Frequently asked
- Keep it to nine seconds or shorter, and set the prompt-length field to match the real length of the file. A prompt longer than that, or a mismatched length value, causes routing problems.
- By default, callers queued behind someone hearing the prompt also cannot be sent to an agent while it plays. Turning on the no-block option lets those waiting callers be connected even while the prompt is playing to someone ahead of them.
› How long can an on-hold prompt be?
› What is the no-block option for?
About VICIfast LLC
VICIfast LLC operates a managed VICIdial hosting + BYOI service for outbound and inbound call centers. We run the dialers, the carriers, the recordings pipeline, and the compliance plumbing so operators don’t have to.
Citing this article
VICIfast Engineering. “On Hold Prompts: messages while callers wait”. VICIfast LLC, June 20, 2026. Retrieved from https://vicifast.com/blog/vicidial-ingroup-on-hold-prompt
Have questions?
Related posts
You might be interested in
VICIfast newsletter
Liked this? Get the next one in your inbox.
We ship the kind of stuff you just read — concrete, numbers-first, no drip. One email when a new post goes live. Unsubscribe in one click.
Comments
No comments yet — be the first.