Ideas on an automated call flow schedule? 1

[bdelmar]

Wanted to see if anyone had any good ideas on how to do the follow automated schedule. If if it between March 1st and Oct 31st, the calls needs to go to one group. But, if its outside of the calendar range and it is Nov 1st to Feb 28th, they want it to go to a different group.

Now I can certainly create condition for the calendar and mark all the days between March 1st and Oct 31st, then test against that condition. They want this for every year so I'm trying to think of a way where they wouldn't have to go in and select all the days between March 1st and Oct 31st for every year. And no, they don't want a button on the phone to do it, they want it automated so they don't have to remember or worry about it.

 

[amriddle01]

Just create conditions for that period for every year, then link them with an "OR"


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

 

[bdelmar]

I know, Ive done that but i have to select all the days between Match 1st and Oct 31st for that condition so calls route where they need to during those calendar days. Im trying to see if there is a way to do it without having to select every day between March 1st and Oct 31st. Because next year, they'll have to go back in and again select all those days again, and again for the following year, and so on.

 

[amriddle01]

Because next year, they'll have to go back in and again select all those days again, and again for the following year, and so on

Are you talking about the IPO or VM Pro? VM Pro uses conditions which can be linked as I said so they can do many years in advance, if you are talking about the IPO itself that uses time profiles, hence the confusion


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

 

[IPOtech111]

Do this:

In VMPro create 2 separate conditions. Name one something like "Nov 1" and on your calendar select Nov. 1st for this year and however many years ahead you would like. Then Create a second test condition and name it "Mar 1" and select March 1st on your calendar.

Create a User Variable and name it something like "Date"

Now route your incoming call to a VMPro module.

From your start point go to a test condition that tests "Nov 1"

From your true result go to a Set User Variable that sets your "Date" variable with a value of "NovToFeb"

Now go back to your Test condition action and from the False result go to another Test condition that tests "Mar 1"

From that True result go to a Set User Variable the sets the "Date" variable with a value of "MarToOct"

Now on your screen you should have 2 "Set User Variables" and a false result, point all 3 to a Test User Variable action that will return TRUE if "Date" matches the value "NovToFeb".

From your True result go to a transfer with you Nov. through Feb. group in the destion.

From your False result go to another Test User Variable that will return TRUE if "Date" matches the value "MarToOct"

From that True result go to a transfer with your Mar. through Oct. group in the destination.

 

[IPOtech111]

One possible problem with this though to be aware of is if they happen to not get any incoming calls on November or March 1st, your variable will not change thus not automatically changing the call route. So to be safe instead of only selecting November 1st and March 1st on your conditions you may want to select the whole first week or first few days for November and March.

 

[intrigrant]

Why not use the $DATE variable. You can pick the month out of it and if it is equal or greater then 3 and it is lesser or equal to 10 then route 1 is used, if not then route 2 is used.
Here you have a example, copy the text and save it as a test.con file, import it in your VM Pro client and check it out:

<?xml version="1.0" standalone="yes"?>
<diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1">
<VMProImportExportDataSet xmlns="

http://avaya.com/VMProImportExportDataSet.xsd">

<ModuleImportExport diffgr:id="ModuleImportExport1" msdata:rowOrder="0">
<ID>Date 3 to 10</ID>
<Data>AAACAA5EYXRlIDMgIHRvIDEwAARBTkQABEFORAAPbWlkKCREQVRFLDMsMikAAz49AAMwMwAEQU5EAA9taWQoJERBVEUsMywyKQADPD0AAzEwAA==</Data>
</ModuleImportExport>
</VMProImportExportDataSet>
</diffgr:diffgram>

A simple mind delivers great solutions

 

[IPOtech111]

I suppose that would work too and maybe be a bit simpler....Never used that function. Thanks for showing me up

 

[bdelmar]

Thanks for the suggestions guys. I'll give Integrants solution a try and I'll let you know how ti works out.

 

[IPGuru]

thats worth a star in anyones book

A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear