Agents
Inbound calls
Upon an incoming call, Webitel sends an HTTP request to the Customer's web service, where the GET request (parameter cid-CallerID Number) contains the client's number if defined. In response, we receive JSON with the parameters necessary for routing:
- Number found / not found;
- The client has a debt / no deb.
When a call is assigned to an employee (Agent), Webitel sends an HTTP request to the Customer's web service, wherein the body of the POST request passes the parameters necessary to display information about the call in the Customer's system:
- event - information about the event:
- offering - distribution per Agent,
- bridged - Agent answer;
- direction - direction of the call:
- inbound - incoming,
- outbound - outgoing or dialer call;
- queue - identifier of the incoming Queue or dialer;
- member - subscriber identifier ( needed for postprocessing);
- attempt - identifier of the dialer's dialing attempt (required for postprocessing);
- uuid - call identifier;
- agent - identifier of the Agent or his extension number (need to agree on the format);
- cid - client's telephone number.
Outgoing call
To make an outgoing call from the Customer's system, the Agent must have a registered SIP phone (software or hardware) and a token to fulfill requests.
An example of a POST request to initiate a call:
http://swagger.webitel.com/#/CallService/CreateCall
Outgoing call
{ "destination": "Destination number", // required "from": { "extension": "Extensions" // required }, "params": { "audio": true, "auto_answer": true, "record": true, "variables": { "additionalProp1": "string", // Additional variables for the client can be used for statistics and outgoing call routing. "additionalProp2": "string", "additionalProp3": "string" } } }
0 Comments