Page 1 of 1

Call Time Exception

PostPosted: Mon Apr 27, 2009 5:11 pm
by aspitzer
We call all over the US Business to Business. I was wondering if there was an intelligent way to exception a couple of hours during the day from the call time rules ie. lunch. We have found that calling during those hours wastes our leads and the agents time. We set the local call time to 0800 - 1700, but there is nothing to prevent the agent from calling between 1100 - 1300, when the decision maker is most likely at lunch.

I thought about setting state rules to do this but it will inevitably leave a gap where no leads are available to call. We do shifts here so there is no lunch break on our end.

PostPosted: Mon Apr 27, 2009 5:27 pm
by Op3r
Im thinking about doing this

Create a calltime called break.

specify 9am to 11am.

then create a state call time called break2

specify 1pm to 5pm

then go back to the call time break

add the state time called break.

Is this going to work?

PostPosted: Mon Apr 27, 2009 5:41 pm
by mflorell
Not sure that will work.

What I've been thinking of doing is dumping call times and moving that functionality to SHIFTS, which you would be able to select multiple shifts per campaign or in-group, or even just allowing multiple state call times per campaign/in-group. Of course this will probably take a lot of time to do and I'm backlogged as it is, so just put it in the never-ending todo list for free development time...

PostPosted: Mon Apr 27, 2009 5:54 pm
by Op3r
Edited..

I was thinking about doing a filter.

But

As Alex said, how about modifying the hopper script.

As this is a feature on some dialers like Noble. Maybe vicidial should have a feature to block certain hours on what ever state it is trying to dial.

Im going to scratch my head until I find a very simple way to do this.

PostPosted: Mon Apr 27, 2009 6:05 pm
by Op3r
Or how about just creating a state rule for each state like 1pm to 5pm?

Still thinking on how to do this efficiently

PostPosted: Mon Apr 27, 2009 7:56 pm
by mflorell
This has been brought up a few times in the past actually, but noone has wanted the feature enough to fund the development of this.