

Combine/link operator and time based routes - now we have to loop callsħ.

Create global phone templates (If you can today let please let me know)Ĭouldn't agree with Matt more. Discussed this numerous times with you historically and even provided a very detailed writeup on call flow either on the forums or in an email to you on the need for improved call flow (Matt's "6c") with custom flow destinations and variables. We too have to loop calls in all kinds of hackish ways to meet our customer's needs with the existing very basic routing options. I would say the order is fix bugs, fix bugs, improve call routing, enhance mobile applications.

I do not really agree with Matt on the need for a dedicated holiday schedule because that just opens up a new can of worms because I am sure every company operates with a different holiday schedule. Some companies are open "black Friday", others close. Some may work Christmas Eve/New Years Eve, others close and consider those days holidays. The only day you cannot code is Easter, because there is no set rules, its based on Paschal moons If the comment about holidays is true, then here's a list suitable in the United States: Route on Labor day, Thanksgiving & day after, etc instead of having to update every year - "įrom voip-info on the command GoToIfTime: Matt youre going to love me with regards to this.Īs such, I do not think you can ever eliminate the manually oversight for call routing on holidays, but it can be made easier with more advanced call routing options (custom call destinations/variables). So for thanksgiving, its always a thursday and always falls on a 22nd - 28th, Labor Day is always the first monday in september, so dates 1-7, as long as its a monday, will solve your variable day holidays.
