Contact centre customer callback planning
A callback offer defers customer contacts — it does not eliminate them. The volume moves in time. The WFM function must plan for callback-return demand as an additional stream on top of new inbound contacts, not as a replacement for the original demand.
The WFM error most callback implementations make
The most common WFM mistake in callback implementations is treating the callback uptake rate as a volume reduction. If 30% of customers offered a callback accept it, the WFM team reduces the peak staffing requirement by 30% — and then discovers that the callback-return contacts arrive in the same or following interval, recreating the peak that the callback was supposed to flatten.
The correct model: reduce peak inbound demand by the callback uptake rate, then add the callback-return volume to the planned demand in the return window. Net total volume is unchanged; only the shape of the demand profile is different.
Three callback models and their WFM implications
Virtual queuing (position-in-queue callback)
How it works
Customer is offered a callback when they reach the estimated wait threshold (e.g. wait exceeds 3 minutes). They accept and hang up, retaining their position in the queue. The ACD calls them back when they would have reached the front of the virtual queue.
Volume timing effect
Smooths the inbound peak without materially deferring the demand. Callback contacts return within the same interval or the immediately following interval. The peak is flatter but the demand returns almost immediately — there is very limited capacity relief for the WFM function.
How to model the staffing
Staff as inbound with a modest AHT uplift for callback initiation and redialling. The callback-return demand overlaps with residual inbound demand and must be served by the same agents. Do not separate callback into a dedicated outbound capacity pool — the volume is too interleaved with inbound.
Key risk
Treating virtual queuing as a capacity solution. It improves customer experience during peaks by eliminating the hold experience, but it does not reduce the staffing requirement. An operation that is 5 agents short in a peak interval is still 5 agents short after implementing virtual queuing.
Scheduled callback (time-slot selection)
How it works
Customer selects a specific future time slot for a callback, typically from a menu of available slots that the WFM function has configured (e.g. 'Call me back at 14:00–14:30 today' or 'Call me back Tuesday 09:00–09:30'). The ACD initiates the outbound call at the start of the selected slot.
Volume timing effect
Defers demand to a specific future interval. Effectively transfers inbound demand from the peak interval to a chosen lower-demand interval. The WFM function controls the available slots — high-demand intervals should have fewer available slots; low-demand intervals more. This is the most controllable callback model from a WFM perspective.
How to model the staffing
Configure callback slot availability based on the interval-level staffing position. Open more slots in intervals where the staffing model shows excess capacity; close or restrict slots in intervals where staffed headcount is already at or near the SL threshold. Model callback-return demand as a distinct outbound demand stream within the scheduled slot, added to the inbound volume forecast for that interval.
Key risk
Slot availability not linked to the WFM staffing model. If slot availability is configured once and never updated, callbacks accumulate in slots that have become over-committed. The customer experience in the callback slot becomes worse than the original inbound peak would have been.
Proactive outbound follow-up
How it works
The contact centre initiates outbound contact to customers who abandoned the queue, experienced a service issue, or have a pending case. Differs from callback in that the customer did not request the outbound contact — the operation is proactively reaching out.
Volume timing effect
Does not reduce inbound demand. Adds a new outbound demand stream that must be staffed alongside the inbound queue. The timing of the proactive outbound demand is within WFM control — it should be scheduled for intervals with spare capacity relative to inbound volume.
How to model the staffing
Model as an explicit outbound demand stream with its own volume, AHT, and staffing requirement. Schedule outbound dialling attempts in low-inbound-demand intervals (e.g. 14:00–16:00 on Wednesdays) and suspend outbound dialling when inbound queue positions deteriorate. Agents handling proactive outbound must be reservable for inbound if the queue builds — blending must be configured in both the routing system and the WFM schedule.
Key risk
Outbound dialling continuing during inbound volume spikes. Agents tied up on outbound calls cannot receive inbound contacts, compounding the inbound queue crisis. The intraday team must have clear decision rights to suspend outbound dialling immediately when inbound SL falls below threshold.
Why callback AHT is higher than inbound AHT
Four reasons callback handle time exceeds equivalent inbound AHT:
Outbound initiation overhead
The agent must initiate the outbound call, wait for the customer to answer, and confirm the customer's identity before the contact begins. This adds 30–60 seconds before the substantive conversation starts.
No-answer and redial attempts
A proportion of callback contacts will go unanswered on the first attempt and require a redial. Each attempt consumes agent time even when unanswered. Typically 10–20% of callback contacts require at least one redial.
Customer frustration handling
Customers who waited for a callback may be more frustrated than equivalent inbound customers, particularly if the callback was late or the wait for the callback was longer than the original queue. Agents spend additional time managing the customer's experience before addressing the underlying reason for contact.
Longer explanation requirement
The customer may need to re-explain their original issue if they called about a complex topic and time has passed since their original contact. In scheduled callback environments where the callback is the following day, context may have changed.
Apply a 10–20% AHT uplift to callback contacts relative to equivalent inbound contacts in the WFM staffing model. Validate against actuals once the callback solution has been live for 4+ weeks.
Callback planning questions
How does a callback offer change contact centre staffing requirements?
Three effects: (1) Peak flattening — contacts that accept callback exit the inbound queue, reducing peak interval demand by the uptake rate (typically 20–40%). This lowers peak staffing requirement by the same proportion. (2) Callback-return demand — the deferred contacts must be served in the callback window. This adds an outbound demand stream to the return interval. If returns are immediate (virtual queuing), they overlap with residual inbound. If scheduled for a future slot, they add to that interval's forecast. Net volume is unchanged. (3) AHT uplift — callback contacts run 10–20% longer than equivalent inbound contacts due to outbound initiation, redialling, and potential customer frustration. Apply this uplift in the staffing model for the callback-return demand.
Related guides
Intraday management
Managing callback queues in real time
Queue management
Intraday queue management tools
Queue waiting communication
What customers hear while waiting
Abandonment rate
What callback offer is designed to reduce
AHT guide
Managing callback AHT uplift
Outbound staffing
Staffing outbound and blended operations
Erlang C calculator
Model queue behaviour with and without callback active