Hello,
I can see the auto answer for each channel on interaction workspace annex of configuration manager.
*voice.auto-answer
*email.auto-answer
*outbound.push-preview.auto-answer
There is no option for the pull preview interactions to set auto answer?
Something like… outbound.pull-preview.auto-answer
What? No because in that model calls are invoked by agent and shown on IWS by default…
What you say is redundant and illogical.
Thank you for your response cavagnaro.
I don´t know if it is ilogical. Let me explain:
PUSHPREVIEW(campaign)
In this type of campaign, when you press the button “get record” on campaign tab, desktop shows toaster to accept or reject the interaction. If you disable variable outbound.pull-preview.auto-answer on configuration the toaster doesn´t appear and interactions comes up directly.
PULLPREVIEW(Rescheduled records)
The same behaviour, without the button “get record”. The OCS sends you interaction. The Desktop shows the toaster to accept or decline the interaction. I want to disable this toaster. I realized there is no variable on configuration like outbound.pull-preview.auto-answer with pull instead of push.
As a conclusion. I need to disable the toaster on Rescheduled interactions, like we do on PushPreview interactions.
Please, feel free to correct whatever i have written wrong.
Thank you in advance.
It is because as it states, is for rescheduled records, what if your agent is with another call or interaction?
Yes, for rescheduled records (pull preview i suppose). It doesn’t matter if the agent it´s working with another interaction, it will be fine if the new rescheduled interaction it´s opened automatically on another interaction.
When toaster appears it´s not calling any chain of command. When the agent press the button call chain of command to open it (or reject it).
Remember rescheduled records have in theory a window to be called to. If agent does accept while on another call which you don’t know the length it will have, you may lose a contact. Also, those records have a life span, which expire after a while. Then you control them by treatment. Imagine an agent with 3 records on his screen…what would happen then?
Yes, we are controlling this time to accept the interaction.
The problem is the Agent can have a big number of reschedule for the same time. Once this time comes, the rescheduled records will appear on toasters… If you have 15 rescheduled records, the agent have to press the button 15 times. And the time of pressing 15 times this button it´s time lost for Business…
The same if i have accepted the previous15 rescheduled interactions of the example, i suppose.
Any idea?
Thank you very much for your time.
And he handles those 15? O.o is that humanly possible? What about next ones? Is this a worst scenario or a standard one? Personal or Group reschedules?
Personal reschedules. It´s something usual…
I think that it´s not bad. The agent have some interactions for a lot of time…
It is not logical to use “auto-answer” function for pull preview campaigns, where the interactions has to be dialed from an agent. So, it cannot be answered before is dialed 
The only way, how to achieve your goals, is through the custom module within IWS/WDE.
BTW: I am using IWS/WDE and have not encountered the toaster with accept/reject for pull preview campaigns (should by caused by configuration, but I have all allowed).
But, it´s the same behaviour in preview campaigns. The agent have to dial on each interaction opened. I am not understanding what is the difference of reschedule and push or pull to auto accept ???
I tried with Toaster and Broadcast class, but it doesn´t work.
Thank you for your time.
It is not true that the behavior is the same. In general, in out-of-box IWS version there is no way how to achieve auto-dial (no auto-answer) - only through the custom module. It becomes from OCS solution design for preview, where the agent must decide whether the customer will be dial or not. All is described in documentation very well.
Yes i´m not talking about auto dial. The agent will dial on each interaction.
What i was trying to say is:
In Preview campaigns. You can presh the button “Get Record” a lot of times. You will have lot of interactions opened (not dialed).
In pull preview (rescheduled), agent have to accept the reschedule pressing the accept button.
I was trying someting. ???
I´m suscribed to events of campaign. When a Rescheduled interaction comes to desktop i´m trying to open with
_container.Resolve().GetChainOfCommandByName(“StartPreviewRecordOutbound”).Execute(parametersStart)
I can see in genesys documentation, this chain have no parameters. http://docs.genesys.com/Documentation/IW/8.1.3/Developer/Outbound
I´m trying to construct the call to chain like the worskpace desktop do. But it´s not working 100% for me. Some help?
Pull preview has nothing to do with “reschedule”. From my point of view, the auto-answer on voice preview campaigns does not make a sense.
The auto answer there is more an auto accept on this scenario… As there is no voice yet. Now, reschedule means you need to call on a specific time, right? Plus less a few minutes with a max of 10? Something reasonable, that is why the other person asked you to call that time.
So, if you have 15 preview interactions needed to be dialed in a window of 15 minutes, so so, you say each call will have a 1 minute or less duration?
Remember Preview interactions are to keep quality and satisfaction of the customer interaction.
If not, then do Predictive or Progressive and auto dial…what is the point to Preview if it is more likely bothering your business agent control model.
What should happen to a good quality is if agent rejects interaction because he is busy should go to the agent group or reschedule again in 2 or 5 minutes. Then on reports, you will see a HUGE number of Record Rescheduled with Error marked and some business decisions will need to be made. There is obviously something to improve with the scenario you describe.
Hi, little step forward.
I have created auto.answer for Rescheduled Records.
Based on Campaign events, desktop is able to detect a rescheduled record campaign event and start this command:
_container.Resolve().GetChainOfCommandByName(“StartPreviewRecordOutbound”).Execute(parametersStart)
The interactions open correctly :). The problem is, the toaster is opening too :-\
Some idea to hidde the Toaster?
Thank you.
Set the logging to the debug on all levels (PSDK,ESDK,..) and try to find out which commands are fired during the toaster opening.
That is the problem… It´s not executing anny command when the Workspace shows the Toaster.
So, you can only check the Genesys code and overwrite this part of application behavior- but be aware that similiar “changes” are not supported. You can only open a FR to the Genesys.