RingEX native callback — and what it does not cover
RingCentral RingEX queues include a native callback. That is the one most RingCentral admins reach for first, because it is part of the license you already pay for. This page covers the specific cases where RingEX customers ask us if there is something better, and what QueueCallback actually changes.
What the RingEX native callback gives you
A caller waiting in a RingCentral RingEX queue can request a callback rather than continue holding. The native flow is configured inside the queue itself — when overflow or hold conditions are met, the caller is offered the option. This is included in the RingEX license tier and does not require a Contact Center upgrade.
For a non-trivial number of teams, this is exactly the right thing. If the native option handles your callers’ expectations, we have nothing to sell you. Keep using it.
Where RingEX customers hit limits
The two questions we get most often from RingEX admins:
1. Can the caller be rung back at a different number?
Per QueueCallback’s product behavior testing of the native RingEX queue callback, the answer is no — the caller is rung back on the number they originally dialed in on, and the native flow does not surface a prompt to confirm or change that number. For callers who dialed in from a desk phone but want to be reached on a mobile (or vice versa), that is a real friction point.
2. What happens if the caller waits a long time before requesting the callback?
RingCentral’s public documentation does not clearly describe an unbounded in-queue wait for the native callback. Based on observed behavior, the callback request can time out when the caller has been in the queue past an extended threshold (the customer reports we have seen put this around the 30-minute mark — treat that as a description of behavior we have observed, not a published RingCentral spec). For a busy queue at peak hours, that is the case where the native flow stops doing what callers expect.
What QueueCallback changes for RingEX
- Caller controls the callback number. When the QueueCallback flow offers the callback, the caller hears the number they dialed in on and can confirm it or enter a different one. That single behavior is the most common reason RingEX customers replace the native flow with QueueCallback.
- Callback held independently of the queue session. QueueCallback keeps a placeholder call live in the RingCentral queue while the caller hangs up. The placeholder reaches an agent on the same schedule a live caller would have. The callback is not tied to the caller’s in-queue session.
- RingEX licensing stays the same. QueueCallback does not change your RingCentral plan. You stay on RingEX, you keep your existing queues, you keep your existing licenses. QueueCallback layers on top at $100/month per RingCentral queue.
Licensing model differences
The native RingEX callback is bundled with the RingEX license tier you already pay for. No additional per-callback fee. RingCentral Contact Center (which has more extensive callback behavior) is licensed per agent seat, with actual pricing set by your RingCentral contract.
QueueCallback’s licensing is per RingCentral queue, $100 per queue per month, unlimited callbacks on that queue. The model does not scale with agent count or callback volume — only with how many queues you want callback on. For a team that wants callback on one or two specific queues, that is a very different cost shape from a per-seat Contact Center license.
Honest decision rule
If your callers always want to be rung back on the number they dialed in on, and your queues do not run long enough for the observed time-out behavior to bite, the native RingEX callback is included with your license and you should keep using it. If either of those is wrong for your team, that is where QueueCallback earns its $100/queue/month.