Hi Stephanie,
To add to what Robert has said, you can also use the "Output Active Schedules" field from the Evaluate Schedule Group function to know which Schedules are active at the time.
So let's say you create a Schedule Group consisting of 3 different Schedules (all categorized as "Open" schedules). Whenever you go through the evaluation it will tell you which of the 3 were open, so you can make a decision based on that to route to the appropriate queue.
Also, if your times are set in stone, you could check for the time directly in the call flow, there are functions like "GetCurrentDateTimeUtc()" that will give you the current hour, so you can make a decision based on that. (But again, only if your times will never be changing, otherwise you would need to constantly go back to the flow and change it there).
Only reason I see to go with a Data Table would be if you have other parameters unrelated to the Date/Times that you want to add there.. Like the destination queue for example, if you intend to have the queue as something that can change constantly, then the Data Table would help with that.
------------------------------
Marcello Jabur
------------------------------