Page 1 of 1

Disposition after every call/hangup ?

PostPosted: Mon Jun 09, 2008 9:19 am
by rcphq
is there a way to "force" agents to disposition a call BEFORE dialing alt numbers (and still be able to dial alt numbers?)

(does this belong in support?)

PostPosted: Mon Jun 09, 2008 2:55 pm
by mflorell
You can only disposition a customer record once, not after every call attempt in alt-dial mode.

This would be a new feature request. You can add it to the issue tracker, but unless it is a sponsored feature or a consulting project by us it will probably not be done for some time.

PostPosted: Mon Jun 09, 2008 3:09 pm
by rcphq
hmmm
i see, let me re-position the problem,
is there any way to know/implement the "hangup" reason (or ending state) of a call to a certain phonenumb ?
im currently working on a external (to vicidial) way to handle this, im wondering how best to approach it

PostPosted: Mon Jun 09, 2008 8:08 pm
by mflorell
Hangup-reason is actually a new feature for the SVN codebase of vicidial and is based on who hung up the phone call. Are you looking for a disposition or a hangup reason?

PostPosted: Mon Jun 09, 2008 10:59 pm
by rcphq
hmm, well, what we're actually looking for is knowing "exactly" what happened to each number... did they dial the alt_phone because of a disconnect, a busy, person no longer there, etc, so we can better work "cleaning" the list with useless numbers (or resort the numbers).

we're considering a system so that agents can log why they changed phone numb, how doesthe hangup-reason work in the codebase??

PostPosted: Tue Jun 10, 2008 1:15 am
by mflorell
The system currently doesn't do that, the only record of the calls before the last call on the same customer record are the call_log records.

PostPosted: Tue Jun 10, 2008 8:21 am
by rcphq
this is why we're gonna build a external tool to record the reasons for this,
our call_log shows lot's of incall,cbhold,etc, and our client would like more information on "why" a second/third number had to be used.

how does the hangupreason work in the svn latest? agents write comments when a hangup happens? or is it something the system handles?

PostPosted: Tue Jun 10, 2008 1:41 pm
by mflorell
hangupreason is not controlled by the agent, it is only a way of showing whether the agent hungup or the customer.

PostPosted: Thu Jun 12, 2008 12:14 pm
by Freddy_rixcom
Hi all,
on the wave of this topic i wuould like to ask why disconnected calls don't appear in vicidial_log table.
When an agent submit a disposition code like "disconnected" to a congestioned call it doesn't insert any record in the vicidial_log table.
therefore in vicidial_list leads status is correct! Any idea?.
Thanks in advance

PostPosted: Thu Jun 12, 2008 7:13 pm
by mflorell
astguiclient version?

PostPosted: Fri Jun 13, 2008 1:44 am
by Freddy_rixcom
2.0.4
Maybe a dialplan error with h extension?
Thansk in advance

PostPosted: Fri Jun 13, 2008 5:37 am
by mflorell
There have been several bugs fixed in the 2.0.4.1rc2 release and a few more larger changes in the logging in the SVN codebase. A lot of the problems that you mention have been fixed.