Added ability to set scheduled callbacks with Agent API.
Added alt_phone and address3 field searches to DID and Call Menu in-group call routing, to allow searching first by phone number, then optionally by alt_phone and address3. Fixed admin change log display issue git-svn-id: svn://192.168.202.10@1755 3d104415-ff17-0410-8863-d5cf3c621b8a
This commit is contained in:
+11
-2
@@ -1,4 +1,4 @@
|
||||
AGENT API DOCUMENT Started: 2008-07-03 Updated: 2011-09-11
|
||||
AGENT API DOCUMENT Started: 2008-07-03 Updated: 2011-11-14
|
||||
|
||||
This document describes the functions of an API(Application Programming Interface)
|
||||
for the VICIDIAL Agent screen. This functionality will be rather limited at first
|
||||
@@ -106,7 +106,16 @@ DESCRIPTION:
|
||||
Sets the status of the current customer call on the agent dispotion screen
|
||||
|
||||
VALUES: (value)
|
||||
Any valid status in the VICIDIAL system will work for this function
|
||||
value -
|
||||
Any valid status in the VICIDIAL system will work for this function
|
||||
callback_datetime -
|
||||
YYYY-MM-DD+HH:MM:SS, date and time of scheduled callback. REQUIRED if callback is set and status is flagged as a scheduled callback
|
||||
callback_type -
|
||||
USERONLY or ANYONE, default is ANYONE
|
||||
callback_comments -
|
||||
Optional comments to appear when the callback is called back, must be less than 200 characters in length
|
||||
qm_dispo_code -
|
||||
Option callstatus code used if QM is enabled
|
||||
|
||||
EXAMPLE URL:
|
||||
http://server/agc/api.php?source=test&user=6666&pass=1234&agent_user=1000&function=external_status&value=A
|
||||
|
||||
@@ -15,7 +15,7 @@ Development Stages:
|
||||
1. Create admin interface to manage dynamic fields per list_id
|
||||
2. Create display of custom fields within the ViciDial agent interface, including variables to be used in web forms and scripts
|
||||
3. Add exporting of custom tables to list download feature as well as the calls export report
|
||||
4. Create list loading interface to put leads into the vicidial_list table and the custom fields, includes reusable template definitions(field mapping)
|
||||
4. Create list loading interface to put leads into the vicidial_list table and the custom fields, includes reusable template definitions(field mapping pending)
|
||||
|
||||
Limitations:
|
||||
- You could not dial leads sorted by any custom fields
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
NON-AGENT API DOCUMENT Started: 2008-07-24 Updated: 2011-09-28
|
||||
NON-AGENT API DOCUMENT Started: 2008-07-24 Updated: 2011-11-06
|
||||
|
||||
This document describes the functions of an API(Application Programming
|
||||
Interface) for all functions NOT directly relating to the VICIDIAL Agent screen.
|
||||
This functionality will be rather limited at first and will be built upon as
|
||||
critical functions are identified and programmed into it.
|
||||
|
||||
There is also an agent API script, for more information on that, please read
|
||||
There is also an Agent API script, for more information on that, please read
|
||||
the AGENT_API.txt document.
|
||||
|
||||
|
||||
|
||||
@@ -232,7 +232,7 @@ data2: callerID or number called(sometimes prepended by DNIS) [3101-9015556189],
|
||||
vicidial_list field you would like to prefend to the phone number on
|
||||
ENTERQUEUE/CALLOUTBOUND events
|
||||
|
||||
data3: ??
|
||||
data3: optional qm_dispo_code variable for CALLSTATUS verbs, submitted through the agent-API external_status function
|
||||
|
||||
data4: ??
|
||||
|
||||
|
||||
Reference in New Issue
Block a user