Avaya Support Forums  

Go Back   Avaya Support Forums > IP Office Contact Center

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 08-13-2016, 05:03 AM
verma62 verma62 is offline
Brainiac
 
Join Date: Apr 2015
Posts: 59
verma62 has 10 reputation points
Default multiple group - Estimated Wait Time Announcement

Hi All,

I am able to use the sample IVR application for announcing estimated wait time without any issue. However in my application I have 2 Agent groups where call is transferred based in caller selection in IVR, and I am not able to understand how the average wait time will work differently/independently for 2 Agent groups as EWT is calculated based on Topic parameter i.e. Mon_AvgTConvWait.

Design
1. call comes to Topic - Main(7010)
2. Topic Routes the call to IVR which prompts the user to enter 1 for sales and 2 for support.
3. IVR returns the call to Topic -Main based on caller input.
4. Topic -Main routes the call to IVR (EWT) - where logic is kept for announcing the EWT. Here the topic variable Mon_AvgTConvWait is assigned for Topic-Main using (Configuration>System>Variables .

Now as EWT is calculated based on Topic-Main, I believe the awt should come same irrespective of I am transferring call to Sales group or Support group. Please correct me if my understanding is wrong.

I want to achieve that if caller is supposed to transfer to sales group then EWT should be announced for sales group or for support group if caller opted for that.

Should I create 2 different topics sales and support and route the call from Topic-Main to these groups. If yes how to define Mon_AvgTConvWait for mutiple topics.

Thanks,
Rajat Verma
Reply With Quote
  #2  
Old 08-14-2016, 05:38 AM
kruegerb kruegerb is offline
Genius
.
 
Join Date: Oct 2013
Location: Stuttgart-Germany
Posts: 276
kruegerb has 12 reputation points
Default

you have to create for sales and support a separate topic. after selecting in main topic sales or support announce the EWT for the respective topic, i.e. you need the varialbe at these both new topics
Reply With Quote
  #3  
Old 08-17-2016, 12:48 AM
verma62 verma62 is offline
Brainiac
 
Join Date: Apr 2015
Posts: 59
verma62 has 10 reputation points
Default

Thanks for your quick response and valuable guidance as always. I was not able to access the system in last 3-4 days so didnt get chance to check this.

I will implement this and check the same. But one thing I have noticed is that I am getting the value for Mon_AvgTConvWait as very less i.e. 18 seconds always. Is it because the system is current in implementation phase and while our testing we generally disconnect 90% of calls within 10-15 seconds, so using some logic system calculates avarage speaking time as 18 seconds. Or I am doing wrong in using this variable in some way?

Thanks,
Rajat Verma
Reply With Quote
  #4  
Old 08-23-2016, 12:31 AM
kruegerb kruegerb is offline
Genius
.
 
Join Date: Oct 2013
Location: Stuttgart-Germany
Posts: 276
kruegerb has 12 reputation points
Default

have you checked in historical reporting the counter AvgTConvWait?
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 10:30 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.