Genesys & Blaster Campaigns

[cavagnaro]

I heard the "Blaster" term on Aspect...
Here is a little sample:
http://www.tek-tips.com/viewthread.cfm?qid=1500275&page=4

[amarceau]

Funny since my old dialer for 15 years was the Aspect Unison dialer

[fnunezsa]

Setting predictive_hot_start OCS parameter to yes or true will help you avoid the preliminary progressive mode. This option is used in conjuction with predictive_hit_ratio, predictive_outbound_call_duration, predictive_inbound_rate, and predictive_inbound_call_duration.

Please refer to OCS deployment guide for more info about those options.

HTH.

Franklin.

[amarceau]

[quote author=fnunezsa link=topic=6127.msg26660#msg26660 date=1296090505]
Setting predictive_hot_start OCS parameter to yes or true will help you avoid the preliminary progressive mode. This option is used in conjuction with predictive_hit_ratio, predictive_outbound_call_duration, predictive_inbound_rate, and predictive_inbound_call_duration.

Please refer to OCS deployment guide for more info about those options.

HTH.

Franklin.
[/quote]

Thanks Franklin - I'm going to give those settings a shot today and I'll keep you posted   I appreciate all the help

[Vikram_Joshi]

Very interesting topic indeed,
Blaster term is very old and well known on Aspect environment and operations likely to request the same from Genesys for collections.
As new to Genesys, looking forward for any updates.

Thanks.

[amarceau]

Well I've tried all these settings and some more based on what I've read in the documentation and I still can't seem to get this blaster campaign to run any faster then it does..... I ended up having to create an AgentID on my Avaya switch with a dummy skill assigned to it.  And I have to log that agentID into GAD and go ready in order to have that particular campaign call even at a pace of 100/hour.  It's still unacceptable, since I have about 2000 records a day to call virtually - and I'm not getting through them currently..... Following are the settings I currently have in my CampaignGroup:

[OCServer]
pa-selfcheck-awt-threshold=5
pa-selfcheck-bf-threshold=90
pa-selfcheck-interval=60
pa-selfcheck-odr-threshold=100
predictive_algorithm=advanced_small_group
predictive_hit_ratio=10
predictive_hot_start=true
predictive_inbound_call_duration=10
predictive_inbound_rate=0
predictive_outbound_call_duration=10
time-to-ready-tolerance=1

Any suggestions on these settings would be appreciated.

[cavagnaro]

Already told you...add more agents...1 isn't enought

[Fra]

[quote author=Fra link=topic=6127.msg26644#msg26644 date=1296052885]
[quote author=amarceau link=topic=6127.msg26637#msg26637 date=1296047850]
1.  We don't have dedicated outbound ports.  We use whatever's available on the PBX.
[/quote]

Not correct - Genesys-wise, you are limited by the number of outbound ports that you have purchased by Genesys and that are hardcoded into the license.dat file. OCS will dial at its best as many calls as the number of outbound ports licensed.

[quote author=amarceau link=topic=6127.msg26637#msg26637 date=1296047850]
4.  I have looked at OCS logs, but as far as I can see - since it's only recognizing 1 agent available for my Blaster camapign it's pacing itself according to that one agent.  Even if I put the Over Dial rate at 200-300 it still does not change the dial rate
[/quote]

That's your problem: regardless of the parameters you set, if OCS sees only one available agent, it will never ever overdial, or potentially switch to predictive; one of the input parameters of the OCS pacing algorithm is the number of logged in / ready agents.

Fra
[/quote]

Just to stress it, if you are expecting Genesys to run blaster campaigns, you have gone for the very wrong choice, mate.

Fra

[cavagnaro]

Unless you do a Genesys OCS integration with GVP
Or do what I told you to do....