List of disposition that PureCloud Edge may return

It appears that there is a way to write dialer rules

Call Analysis Available in wrap-up rule conditions only. Allows you to perform an action when call analysis detects a busy signal, answering machine, live person, or when no one answers the call. For example, you can set the rule action to schedule a callback in 10 minutes if a line is busy.

The Disposition box allows you to select Busy, Machine, No Answer, or Person. In special cases, you may type a **free-form call analysis condition instead. For example, you might type disposition.classification.callable.sit** . This feature supports any call analysis disposition that PureCloud Edge may return..

I cannot find any documentation that defines what all of them are and the format needed. Can you assist?

Thanks

AG

Hi any update or thoughts on this?

You can use the Outbound APIs to manage rules. Specifically, the APIs under /api/v2/outbound/campaignrules. If you're trying to replicate the UI's functionality, the easiest thing to do is configure an example in the UI and then retrieve that rule via the API to see what the data looks like. You can then use that as a guide for future requests.

@tim.smith - Take a look at the link which Anthony shared. On that page it shares details about "Call Analysis".

The Disposition box allows you to select Busy, Machine, No Answer, or Person. In special cases, you may type a free-form call analysis condition instead. For example, you might type disposition.classification.callable.sit . This feature supports any call analysis disposition that PureCloud Edge may return.

What are all of the possible values like "disposition.classification.callable.sit" as we need to create special rules based on the Edge disposition?

The possible values aren't currently documented anywhere. If you need a discrete list, I would suggest opening a case with PureCloud Care to ask for this information since it's not available elsewhere. Although this is a "how to use the API" question that is generally appropriate for the forum, going through care will prioritize a request to the dev team to provide that list via the case or create public documentation for it.

@tim.smith - My team was able to pull this list. So I have to ask do you have a mapping of these values to the ININ_ dispositions that get set on the list? I have 0002693996 opened as well if you want to collaborate with them.

"responses": {

"disposition.classification.uncallable.sit": {

"reactionType": "hangup"

},

"disposition.classification.callable.busy": {

"reactionType": "hangup"

},

"disposition.classification.callable.noanswer": {

"reactionType": "hangup"

},

"disposition.classification.callable.sit": {

"reactionType": "hangup"

},

"disposition.classification.callable.fax": {

"reactionType": "hangup"

},

"disposition.classification.callable.disconnect": {

"reactionType": "hangup"

},

"disposition.classification.callable.machine": {

"reactionType": "hangup"

},

"disposition.classification.uncallable.notfound": {

"reactionType": "hangup"

},

"disposition.classification.callable.person": {

"reactionType": "transfer"

1 Like

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.