Required security profile permissions: Dispositions Edit
The following table defines the system dispositionResult that the agent or system assigns to the contact when the interaction ends. values:
Codes showing -1 or -4 indicate that the record is in play and queued up for calling.
| Disposition | Name | Description | Reporting Group Name | Dialing Outcome ID |
|---|---|---|---|---|
| 1 | Positive w/Amount | The agent must enter an amount (final). | Positive Outcome | 10 |
| 2 | Positive no Amount | The agent does not need to enter an amount (final). | Positive Outcome | 10 |
| 3 | Negative — DNC — Skill | The contact's request for the agent to add him to the do not call list only applies to this skillClassification used to facilitate the delivery of contacts; assigned to agents based on abilities, specialties, and knowledge (final). | Negative Outcome | 99 |
| 4 | Negative — DNC — BU | The contact's request for the agent to add her to the do not call list applies to all skills (final). | Negative Outcome | 98 |
| 5 | Negative | The agent received some kind of negative response (final). | Agent Retry | 10 |
| 6 | Other | The contact is not qualified, no decision, no further effort required or various bad number responses (destination/phone number final only). | Other Complete | 10 |
| 7 | Retry — Rescheduled Agent Specific | The agent received some kind of negative response and scheduled a callbackHolds a customer's place in queue and automatically calls the customer when they move to the front of the queue. with himself in particular. | Agent Retry | 86 |
| 8 | Retry — Rescheduled Specified Date/Time — Any Agent | The contact specified a date and time for a callback, but any agent can handle the call. | Agent Retry | 87 |
| 9 | Retry — Rescheduled Later Date/Time Unspecified | The contact did not specify a date and time to reschedule. | Agent Retry | 88 |
| 10 | Retry — Not Available | The requested person was unavailable. | Agent Retry | 89 |
| 11 | Retry — Answering Machine | If AMD settings are off in your business unitFile format associated with Microsoft Excel; may also be expressed as .xlsx, an agent must retry this record later. | Connect Retry | 5 |
| 12 | Final — Answering Machine | If AMD settings are off in your business unit, the system met the primary goal by leaving a message (final). | Positive Outcome | |
| 13 | Fax Machine | The agent labeled this number as a fax machine. If AMD settings are off in your business unit, the number of retries is determined by your retry logic. | Connect Retry | 3 |
| 14 | Answering Machine Left Message | The dialer reached an answering machine and played a pre-recorded message. | System Retry | 33 |
| 15 | Busy | The dialer reached a busy signal. | System Retry | 1 |
| 16 | Error | The phone network was unable to place the call. | System Final | 6 |
| 17 | Fax | The dialer detected a fax machine. | System Retry | 3 |
| 18 | Invalid Number | The number the dialer called was invalid. | System Final | 20 |
| 19 | Answering Machine | The dialer reached an answering machine but did not play a pre-recorded message. | System Retry | 5 |
| 20 | No Answer | The contact did not answer before the configured timeout. | System Retry | 2 |
| 21 | Number Changed | The Called Party Number is no longer assigned. | System Final | 22 |
| 22 | Disconnect | The dialer reached a disconnected number. | System Final | 21 |
| 23 | Network Busy | The dialer did not connect because no circuit or channel was available. | System Retry | 26 |
| 24 | Abandon | Predictive Only — The caller abandoned the call prior to being connected to an agent. | System Retry | 7 |
| 25 | Agent Abandon | The agent ended the call prior to being connected to the contact. | System Retry | 96 |
| 26 | Manual Suppression | The system suppressed the call because of an entry in the call suppressionTemporarily skips a contact when using the outbound dialer. list that someone entered manually. | Suppressed Final | 90 |
| 27 | Webservice Suppression | The system suppressed the call through a web service call. | Suppressed Final | 91 |
| 28 | IVR Suppression | The system suppressed the call through an IVRInteractive Voice Response; an automated phone menu that allows callers to interact through voice commands, key inputs, or both, to obtain information, route an inbound voice call, or both. response. | Suppressed Final | 92 |
| 29 | Script Action Suppression | The system suppressed the call through a script action. | Suppressed Final | 93 |
| 30 | Bulk Upload Suppression | The system suppressed the call because of an entry in the call suppressionTemporarily skips a contact when using the outbound dialer. list that someone added with bulk upload. | Suppressed Final | 94 |
| 31 | None | None | System Final | |
| 32 | Called Party Hang Up | The contact hung up before being connected to an agent. | Connect Retry | 31 |
| 33 | Force Agent Disconnect | The agent forced a disconnect through the Active Agent Report. | Forced Closed Final | 85 |
| 34 | Call Takeover | A supervisor took over the call. | Forced Closed Final | 84 |
| 35 | Disposition Timeout | The agent did not select a dispositionResult that the agent or system assigns to the contact when the interaction ends. for the call before the configured timeout (final). | Negative Outcome | |
| 36 | No Disposition | The agent did not select a disposition option. | System Final | 82 |
| 37 | Forced Remove Call | A web administrator force removed the agent's call. | Forced Closed Final | 81 |
| 38 | System Failure | A system failure, such as a failover, occurred. | System Retry | 8 |
| 39 | No Ports | The call did not connect because no portsWhere information transfers, over a network, between a computer and a server. were available. | System Retry | 97 |
| 40 | Bad Number | The telephone number does not match existing dialing patterns. | System Final | 24 |
| 41 | Retry - Preview Requeue | The agent selected the Requeue button in the user interface during a dialer preview. | Preview Reject - Retry | 80 |
| 42 | Third Party — Cell Phone | A custom script identified this record as a cell phone when it did not previously have a mark for compliance. | Suppressed Retry | 101 |
| 43 | Third Party — DNC | A custom script marked this record for addition to the do not call list. | Suppressed Final | 100 |
| 44 | Third Party — Time Zone Restricted | A custom script identified this record as restricted because of its time zone. | Suppressed Retry | 102 |
| 45 | Third Party — Legislative Restricted | A custom script identified this record as restricted by legislation. | Suppressed Retry | 103 |
| 46 | Script Action 1 | A custom script identified this record as restricted by generic reason 1. | Suppressed Retry | 104 |
| 47 | Script Action 2 | A custom script identified this record as restricted by generic reason 2. | Suppressed Retry | 105 |
| 48 | No Scripting Disposition | Scripting did not select a dispositionResult that the agent or system assigns to the contact when the interaction ends.. | System Final | 106 |
| 49 | Agent Specific — Queue Is Full Final | The agent exceeded the maximum queue size for a single agent (final). | System Final | 107 |
| 50 | Agent Specific — Queue Is Full | The agent exceeded the maximum queue size for a single agent (not final). | System Retry | 108 |
| 51 | Callback Undeliverable | The system did not deliver the callbackHolds a customer's place in queue and automatically calls the customer when they move to the front of the queue. to an agent before the end of the delivery expiration window. | System Retry | 109 |
| 52 | Agent Specific — Agent Unavailable Final | The system queued the agent-specific call but was unable to deliver it to the agent (final). | System Final | 110 |
| 53 | Agent Specific — Agent Unavailable | The system queued the agent-specific call but was unable to deliver it to the agent (not final). | System Retry | 111 |
| 54 | Agent Specific — Agentless Skill Final | The system queued an agent-specific call for an agentlessContacts made without a live agent for tasks such as one-way delivery of information or messages.. skill (final). | System Final | 112 |
| 55 | ISDN Cause Code 18 | The phone network was unable to place the call (not final). | System Retry | |
| 56 | ISDN Cause Code 21 | The phone network was unable to place the call (non final). | System Retry | |
| 57 | ISDN Cause Code 102 | The phone network was unable to place the call (non final). | System Retry | |
| 58 | SysUnclassified | The system did not specify a classification. | System Final | |
| 60 | DialerBlendingRetry | The system failed to add a call to belnding. | System Retry | |
| 61 | Reactivation | Reactivated record | System Retry | |
| 62 | SMS Final - Destination | The SMS was successful and other destinations in the record are available to attempt. The record is still active. | System Final | |
| 63 | SMS Transport Failure Retry | The SMS was successful but the system will make more attempts on the record. See Retry Management for information about setting the frequency of SMS retries. | System Retry | |
| 64 | SMS Failure | The SMS did not send successfully. | System Final | |
| 65 | SMS Failure Message too Long | The SMS message is too long and did not send. | System Final | |
| 66 | SMS Failure Invalid Transport Code | The SMS message failed due to an invalid transport code | System Final | |
| 67 | Email Final | Email was successful. | System Final | |
| 68 | Email Failure | Email did not send successfully. | System Final | |
| 69 | Email Retry | Email did not send successfully. | System Retry | |
| 70 | SMS Final - Record | SMS was successful and the system makes no more attempts on the record. The record is final. | Positive | |
| 71 | SMS Retry | The SMS was successful but the system will make more attempts on the record. See Retry Management for information about setting the frequency of SMS retries. | Connect Retry | |
| 72 | Retry - Snooze | The agent clicked the Snooze button from a dialer preview window. The attempt snoozed for a pre-defined period of time. | Preview Reject - Retry | |
| 73 | Retry - Preview Rescheduled Agent Specific | The agent rescheduled the contact from a dialer preview window and the same agent will handle the rescheduled call. | Preview Reject - Retry | |
| 74 | Retry - Preview Rescheduled Any Agent | The agent rescheduled the contact from the dialer preview window and any agent can handle the rescheduled call. | Preview Reject - Retry | |
| 75 | Preview Reject - Positive | The agent set a dispositionResult that the agent or system assigns to the contact when the interaction ends. from a dialer preview window with a positive sentiment and no amount entered. | Preview Reject - Positive | |
| 76 | Preview Reject - Positive w/Amount | The agent set a disposition from a dialer preview window with a positive sentiment and an amount entered. | Preview Reject - Positive | |
| 77 | Preview Reject - Negative | The agent set a disposition from a dialer preview window with a negative sentiment. | Preview Reject - Negative | |
| 78 | Preview Reject - Negative DNC BU | The agent set a disposition from a dialer preview window with a negative sentiment. The contact requested to be added to the business unit do not call list. | Preview Reject - Negative | |
| 79 | Preview Reject - Negative DNC Skill | The agent set a disposition from a dialer preview window with a negative sentiment. The contact requested to be added to the skill do not call list. | Preview Reject - Negative | |
| 80 | Preview Reject - Negative Other | The agent set a disposition from a dialer preview window with a negative sentiment for a reason classified as "other." | Preview Reject - Other | |
|
81 |
Proactive Identified - Fax | The agent identified the destination as a fax number by pressing the Fax button in the MAX interface. | System Retry | |
| 82 | Proactive Identified - Answering Machine | The agent identified the destination as an answering machine by pressing the Answering Machine button in the MAX interface. | System Retry | |
| 83 | Proactive Identified - Bad Number | The agent identified the destination as a bad number by pressing the Bad Number button in the MAX interface. | System Retry | |
| 84 | Proactive Identified - Answering Machine Left Message Long | The agent identified the destination as an answering machine by pressing the Answering Machine button in the MAX interface. Additionally, the system initialed the default action for Classify with Answering Machine Detection options in CPA Management. | System Retry |
