Smarter Callbacks with Availability-Aware Scheduling CCAAS APIs (Integration of workforce schedules and real-time capacity into the callback request system).
Real-time User Journey
This journey illustrates how a customer experiences a “guaranteed” callback time rather than a generic “as soon as possible” wait:
- High Volume Encounter: A customer calls a support line during a peak period. The system informs them of a 30-minute wait time.
- Smart Callback Offer: The system offers a callback. Using the Availability-aware API, it doesn’t just look at current queues; it checks the Shift Schedule for the next few hours.
- Specific Slot Selection: The IVR (or bot) says, “We can call you back between 2:15 PM and 2:30 PM today when we have a specialist available. Does that work?”
- Confirmed Booking: The customer confirms. The system creates a “Scheduled Callback” record that is pinned to the workforce’s available capacity.
- Agent Assignment: At 2:15 PM, the Unified Routing engine identifies an agent who has just started their shift and has the required skills.
- The Connection: The system dials the customer first, then connects the agent, fulfilling the promise made during the initial call.
Step-by-Step: How to Enable This Feature
This feature requires a combination of Admin Center configuration and API integration for custom IVRs or Portals.
- Step 1: Enable Workforce Management Go to Contact Center Admin Center > Operations > Workforce Management. Ensure Shift Planning is active and shifts are published for your agents.
- Step 2: Activate Callback Channel Navigate to Channels > Voice > Manage. Ensure “Direct Callback” is enabled in your voice channel settings.
- Step 3: Configure the CCAAS API Access the Developer Resources section in the Admin Center to retrieve your CCAAS (Contact Center as a Service) API endpoints. You will need these to feed availability data into your IVR or Website.
- Step 4: Map Capacity to Routing In Routing > Queues, select your Voice queue and enable the setting “Consider agent shifts for callback scheduling.”
- Step 5: Set Buffer and Grace Periods Define your “Schedule Buffers” (e.g., don’t offer a callback 5 minutes before an agent’s shift ends).
- Step 6: Update IVR/Bot Logic Update your Copilot Studio bot or IVR workflow to call the GetAvailability API action, which will present the available time slots to the customer.
Infographic: Traditional vs. Smarter Callbacks
| Feature | Traditional Callbacks (ASAP) | Smarter Callbacks (Availability-Aware) |
| Trigger | Triggered by queue length only. | Triggered by Shift Schedules + Queue Length. |
| Timing | “We will call you back when it’s your turn.” | “We will call you back at 2:15 PM.“ |
| Agent Impact | Can hit agents right at shift-end. | Respects shift boundaries and breaks. |
| Customer Experience | Uncertain wait; customer might miss the call. | High certainty; customer expects the call at a specific time. |
| Routing Logic | First available agent. | Best agent starting a shift or with open capacity. |
References