VoiceGuide IVR Software Main Page
Jump to content

Evaluate Expression Module

Recommended Posts

Earlier I posted a question pertaining to evaluating expressions for time open/closed. The resolution posted follows this message.

 

I set this up as the entrance point to the script. Customers are calling 9:30 onward and Voiceguide is evaluating the expression to True to go through the scripts when we're open, instead of when we're closing. We're getting some irate customers as to why we're not answering the phones (when we're not here).

 

Is there a correction to the evaluation or is there a problem with Voiceguide?

 

Lance Rasmussen

(Voiceguide 5.1.8)

 

 

((($RV_DAY >= 2) and ($RV_DAY <= 4)) and (($RV_HOUR >= 10) and ($RV_HOUR < 16))) or ((($RV_DAY = 1) or ($RV_DAY = 5)) and ((($RV_HOUR >= 10) and ($RV_HOUR < 17)) or (($RV_HOUR = 17) and ($RV_MINUTE < 30)))

Share this post


Link to post

Could you please post a copy of VoiceGuide's Debug Printout which captures an incoming call from a customer which was not answered when it should have been.

 

When running the script click on VoiceGuide's View menu and select 'Event Trace Log' option - any log information will then appear in this window. (You must open the trace window before making the call.)

Select the "save to file" option - this will result in the log file being created in VoiceGuide's \log\ subdirectory called MMDDvgm.txt

.ZIP the log file for the day when the customer complained and post it here, indicating the time the call was made.

 

Next version of VG will have a "Time Switch" module which makes the switching based on time/date much easier:

post-2-1077660510.gif

Share this post


Link to post

Will do.

 

My suggestion along with the time module would be a module/function for vacation closures. So we can easily indicate permanent closures (Christmas, New Years, etc) and one time holidays/closures.

 

Lance

Share this post


Link to post
My suggestion along with the time module would be a module/function for vacation closures. So we can easily indicate permanent closures (Christmas, New Years, etc) and one time holidays/closures.

To do this in the Time Switch module you would just specify the start date/time of the closure and the end date/time of the closure. Then if the call is made within this time the "True" path is taken which would lead to the module which says "We are closed for xxxx holiday".

 

 

Looking at the expression:

 

((($RV_DAY >= 2) and ($RV_DAY <= 4)) and (($RV_HOUR >= 10) and ($RV_HOUR < 16))) or ((($RV_DAY = 1) or ($RV_DAY = 5)) and ((($RV_HOUR >= 10) and ($RV_HOUR < 17)) or (($RV_HOUR = 17) and ($RV_MINUTE < 30)))

 

we can see that it is lacking a bracket ")" at the end of it - that is why it is always returning an error - which you can see in the trace log:

 

094631.48 4 Error: 1006

 

Change expression to:

 

((($RV_DAY >= 2) and ($RV_DAY <= 4)) and (($RV_HOUR >= 10) and ($RV_HOUR < 16))) or ((($RV_DAY = 1) or ($RV_DAY = 5)) and ((($RV_HOUR >= 10) and ($RV_HOUR < 17)) or (($RV_HOUR = 17) and ($RV_MINUTE < 30))))

 

and it should work fine.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×