...
The following parameters are provided:
| Field Name | Description | ||
|---|---|---|---|
REST Parameters | $filter=CustomerID eq '$SAPBusinessPartnerID' $expand=IndividualCustomerSalesData | SalesForceID | The Id of the record in SalesForce which should be called. |
CallerID | The number to be called (the number clicked on in SalesForce, cleaned to remove unnecessary characters, punctuation and characters which cannot be dialled). | ||
| AgentUID | The UID of the agent currently logged into the Jtel system. It is recommended, that for example the "NickName" field in SalesForce be used to map values between the systems, if the login UID cannot be made equal. |
...
| Status Code | Meaning |
|---|---|
200 – OK | OK, dialling may proceed using the supplied information. |
400 - Bad Request | Bad input parameter, for example SalesForce SAP record not found. |
403 – Forbidden | Call is not allowed. The Jtel system will refuse to place the call if this code is returned. |
| 404 - Not found | Sales Force SAP record not found. The Jtel system will refuse to place the call if this code is returned. |
...
Data should be returned from this request in JSON format. The following fields should be supplied:
| Field Name | Description | ||
|---|---|---|---|
ServiceNumber | The service number to be used (Jtel field ServiceNumbers.Name). | ||
distributionChannelCodeText | This parameter will be parsed from the JSON Result path and will be used to match a service number. | ||
| countryCode | This parameter will be parsed from the JSON Result path and will be used to match a service number | ServiceNumberName | The name of the service number to be used (Jtel field ServiceNumbers.Name2). |
The Jtel system will attempt to match a match ServiceNumber based on the ServiceNumber, then NameContract Number by concatinating the distributionChannelCodeText and countryCode . The found ServiceNumber will be used for signalling the outbound call.