What is virtual hold?

Virtual hold is the feature behind “press 1 for a callback.” It lets a caller hang up instead of holding and get a call back when an agent is ready. This guide explains the concept, where it came from, how the callback actually works under the hood, and how the native and purpose-built options compare for teams on RingCentral RingEX.

Virtual hold lets a caller swap holding time for a callback. Rather than waiting on the line, the caller opts in — often by pressing 1 — hangs up, and the system rings them back when an agent is ready.

Where the term comes from

The category is generally credited to a company literally named Virtual Hold Technology, which commercialized in-queue callback for contact centers and gave the idea its name. That company later went by VHT and today operates as Mindful. Over time “virtual hold” became a generic description for any feature that replaces holding with a callback, and vendors across the market now ship their own versions under names like queue callback, callback-in-queue, or virtual queuing.

The idea caught on for a simple reason: hold time is dead time for the caller and a source of abandoned calls for the business. Letting people reclaim that time while still being served in order was a better deal for everyone.

How placeholder-call callback works

The honest mechanics matter, because “we’ll call you back” can mean very different things. The robust approach uses a live placeholder call to hold a spot for the caller in the queue:

  1. A caller is waiting in the queue and is offered a callback instead of continuing to hold.
  2. The caller opts in and confirms a callback number, then hangs up.
  3. The system places a live placeholder call that occupies a spot in the queue, so the caller doesn’t have to stay on the line.
  4. When that placeholder reaches an agent, the system dials the caller back and bridges the two together.

The distinction to watch for is whether a system keeps a real call waiting in the queue for the caller. A simple “leave your number and we’ll call eventually” is a voicemail with extra steps. Placeholder-call virtual hold keeps a live call in the queue on the caller’s behalf, so callers don’t have to call back and start over.

Native vs purpose-built on RingCentral RingEX

If you run your queues on RingCentral RingEX, you have two ways to get virtual hold, and the honest answer is “yes, but” on the native option.

Native RingEX callback. RingCentral RingEX does include a native call-queue callback. It works, and for short queues with callers who are happy to be rung back on the number they’re calling from, it can be all you need. Its limits are worth knowing, though: it’s a paid add-on (the Call Queues Booster add-on) billed per user in the queue, it calls back the number the caller is calling from, and a callback no agent reaches before RingCentral’s callback timeout is counted unsuccessful (sources: Call Queues Booster licenses, Wait message settings, Live Reports metrics, as of October 2026). (A separate note: RingCentral’s RingCX contact-center product includes queue callback, but it’s a separate product, priced per user from $65 per user per month billed annually as of October 2026 (source: RingCX pricing), not the RingEX native feature.)

Purpose-built callback. A dedicated option adds callback to the same RingEX plan and handles those limits differently. QueueCallback’s RingCentral call queue callback solution automatically re-queues callbacks past your queue’s limits, lets the caller confirm the number or enter a different 10-digit one, and is licensed per queue at a flat $100/month, with no per-agent or per-caller fees. For the full side-by-side, see does RingCentral have callback and the dedicated RingCentral virtual hold page.

When a business needs virtual hold

Virtual hold earns its place when callers regularly wait long enough to get frustrated — busy queues, predictable peaks, or lean teams where adding agents is not realistic. If your queues are short and rarely back up, callers may prefer to just hold. But once your reports show meaningful hold times and abandoned calls, giving people a way to stop holding and still get a call back is one of the highest-leverage changes you can make to the phone experience.

Frequently asked questions

What is virtual hold?

Virtual hold is a call-queue feature that lets a caller stop holding without giving up on being served. Instead of holding, the caller opts for a callback — often by pressing 1 — and the system rings them back when an agent is ready. It trades holding time for a callback.

What does 'press 1 for a callback' mean?

It is the everyday name for virtual hold. While a caller waits, the system offers an option — commonly 'press 1 for a callback' — that swaps continued holding for a callback. The caller hangs up, and the system calls them back when an agent is ready for them.

How does placeholder-call virtual hold work?

Purpose-built systems hold a spot in the queue with a live placeholder call. When a caller opts in, the system places a call that waits in the queue for them, so the queue advances normally. When an agent picks up that placeholder, the system dials the caller back and bridges them to the agent, so the caller doesn't have to stay on the line.

Does RingCentral have virtual hold?

RingCentral RingEX includes a native call-queue callback, which is a form of virtual hold. It comes with the Call Queues Booster add-on, billed per user in the queue, calls back the number the caller is calling from, and a pending callback is counted unsuccessful if no agent is available before RingCentral's callback timeout expires. A purpose-built option like QueueCallback adds a choice of callback number, callbacks that automatically re-queue past the queue's limits, and one flat per-queue price.

Add virtual hold to your RingCentral queue

Give callers a callback instead of a hold. $100/month per queue, with no per-agent or per-caller fees, for your RingEX call queues.

14-day free trial. No credit card needed.You'll need a RingCentral account and one extra RingCentral user per queue for QueueCallback to connect to.

Read more