Hi Linda,
I don't know if this helps, but I'll detail a little of what I did for a customer.
The customer did not want the service level to be impacted by interactions that came in after hours, nor by interactions that occurred in the queue after closing time (example: interaction arrived at 7 pm, service hours are until 8 pm).
Basically, I created a queue name "queue_wait" and for that queue, the customer ignored the service level.
Considering that the service hours end at 8 PM, if the interaction occurs after that time, it will go to the "queue_wait" queue.
In this "queue_wait" queue, I've placed a in-queue-flow that validates the opening hours, and when it identifies that the hours are open (8am for example), it transfers the queue to the queue that the customer actually considers based on the service level.
This also happens when the interaction is in the queue and the service hours end.
I have another in-queue-flow that checks the time of the interactions in the queue and, if the time ends, transfers the interaction to the "queue_wait" queue.
------------------------------
Kaio Oliveira
GCP - GCQM - GCS - GCA - GCD - GCO - GPE & GPR - GCWM
PS.: I apologize if there are any mistakes in my English; my primary language is Portuguese-Br.
------------------------------
Original Message:
Sent: 02-16-2026 08:15
From: Linda Martinez
Subject: Calculating accurate SLA for email queues based on Hours of Operation
Hello, I am seeking guidance on properly configuring an email group so that SLA calculations align with defined business hours. For example, our hours of operation are Monday–Friday, 8 AM to 8 PM, with a 48‑hour SLA. If an email arrives after 8 PM on Friday, it currently appears to breach SLA before work resumes on Monday.
#WFMConfiguration,BestPractices
------------------------------
Linda Martinez
Workforce Management
------------------------------