- DarkLight
Set Non-PEWC Contact Outcome
- DarkLight
Overview
The SetNonPEWCContactOutcome API should be called along with Business or Telephony disposition method, since this creates an entry in the t_Dialer_Detail table that is mandatory for processing the disposition.
Pre-requisite
The Agent must be on an active call or logged in to the application.
Sequence Diagram

Message Structure
Request Parameters | Value |
|---|---|
channel | LCM |
topic | Webservice |
subtopic | SetNonPEWCContactOutcome |
source | «app-name-broadcasting-this-message» |
data | N/A |
Data Parameters
Parameter | Mandatory | Data Type | Description |
|---|---|---|---|
LCMKey | Yes | String | The LCM Key. |
AgentID | Yes | String | The agent ID. |
PhoneNumber | Yes | String | The phone number currently dialed. |
Response Parameters | Value |
|---|---|
channel | LCM |
topic | Webservice |
subtopic | SetNonPEWCContactOutcomeResult |
message | «JSON Object» |
Message Parameters
Parameter | Mandatory | Data Type | Description |
|---|---|---|---|
callid | Yes | String | The Call ID generated by the application. |
response | Yes | JSON Object | The response data. |
Response Parameters | |||
success | Yes | Boolean | The non-PEWC contact outcome update. |
Sample Request
{
"channel": "LCM",
"topic": "WebService",
"subtopic": "SetNonPEWCContactOutcome",
"data":
{
"AccountNumber": "5|3|1|0|0|44|1",
"AgentID": "prakashr",
"PhoneNumber": "9873635"
}
}Sample Response
{
"channel": "LCM",
"topic": "WebService",
"subtopic": "SetNonPEWCContactOutcomeResult",
"message":
{
"response":
{
"success": true
}
}
}