...
To load Members into the Dialer concerning a particular Agent, you must use the Bucket. A Bucket is created for each Agent for which a Member must be bound. Thus, when downloading a Member, the Bucket of the responsible Agent is indicated. To do this, use the POST request block:
An example of Soft and Precollection dialers
| Code Block | ||
|---|---|---|
| ||
{
"items": [
{
"communications": [
{
"description": "Description1", //a field to which you can pass data on a particular destination. This description can be sent in hooks when calling.
"destination": "Destination", //number or another edition means of communication
"priority": 0, // the priority of the destination within the Member. Works when there are several numbers within one communications array
"type": {
"id": "1"
}
}
],
"expire_at": "string", // dialer termination time for this Member, timestamp (end of the current day)
"name": "Member1",
"priority": 1, // Member priority within the same Queue.
"variables": {
"additionalProp1": "string", // additional variables for the client, which can be used for statistics and are available for sending to a third-party system by event
"additionalProp2": "string",
"additionalProp3": "string"
}
},
{
"communications": [
{
"description": "Description1",
"destination": "Destination",
"priority": 0,
"type": {
"id": "1"
}
},
{
"description": "Description1",
"destination": "Destination",
"priority": 0,
"type": {
"id": "1"
}
},
{
"description": "Description2",
"destination": "Destination",
"priority": 10,
"type": {
"id": "2"
}
}
],
"expire_at": "string",
"name": "Member2",
"priority": 100,
"variables": {
"additionalProp1": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}
}
]
} |
...
| Code Block | ||
|---|---|---|
| ||
{
"items": [
{ "bucket": {
"id": "1" // The ID of the Bucket through which the agent and client are linked.
},
"communications": [
{
"description": "Description1", // a field to which you can pass data on a particular destination. This description can be sent in hooks when calling.
"destination": "Destination", //number or another edition means of communication
"priority": 0, // The priority of destination within the Member. It works when there are several numbers within one communications array
"type": {
"id": "1"
}
}
],
"expire_at": "string",
"name": "Member1",
"priority": 1, // Member priority within the same Queue
"variables": {
"additionalProp1": "string", // additional variables for the client, which can be used for statistics and are available for sending to a third-party system by event
"additionalProp2": "string",
"additionalProp3": "string"
}
},
{ "bucket": {
"id": "2"
},
"communications": [
{
"description": "Description1",
"destination": "Destination",
"priority":0,
"type": {
"id": "1"
}
},
{
"description": "Description1",
"destination": "Destination",
"priority": 0,
"type": {
"id": "1"
}
},
{
"description": "Description2",
"destination": "Destination",
"priority": 10,
"type": {
"id": "2"
}
}
],
"expire_at": "string",
"name": "Member2",
"priority": 100,
"variables": {
"additionalProp1": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}
}
]
} |
1.3. Example for dialer Outbound IVR: