A customer is concerned over the fact that there will be additional details in the result sent that do not relate to the appointment request id and they have to filter it to get the slots that do pertain.

The Appointment_Offer object is related to a PSO plan which is only generated every few minutes depending on various factors. What this means is multiple appointment requests (e.g. customer 1 in patch A, customer 2 in patch will have all their respective Appointment_Offer items contained within the same plan. This means that the response for customer 2 could contain the offers for customer 1 as well as customer 2.

From Customer

We currently have 150 service agents including the Outbound agents that assist with service when there are peaks. we typically run at 80% concurrent agent peak rate.  During light up and cool down ~180 logged in to support serivce (we borrow agents from other queues).  So about 144 agents (estimates only)

What it means:

If we configure the system with 21 slots in the Appointment template then it means that for every request that we make it to PSO, each get appointment response from PSO could contain  up to 3024 appointment offers. Out of which only 21 are relevant for the request that is made. This could pose significant performance to the system.