When a contact is placed back into the queue with a minimum time before routing (e.g., End of Queue Minimum 16 hours), it puts that contact 'on hold' and will not be routed for at least the amount of time that has been set. This prevents the contact from being called again too quickly. These contacts are prioritized lower than Scheduled Callbacks, available contacts, due Retry-ins, and Uncalled contacts, ensuring they get another chance to be contacted but not right away.

When setting this waiting time, you have two options:

• End Of Queue, Minimum: This option lets you choose from preset waiting times. If you don't want any waiting time, select "No Minimum" from the drop-down.
• Custom End Of Queue: With this option, you can decide exactly how long a contact should wait before they're eligible to be called again. You can enter the waiting time in minutes, hours, days, weeks, or months. This flexibility allows you to tailor the waiting time to fit your specific needs.

Contacts are placed back into the queue and prioritized based on the retry-in period (e.g., retry in 4 hours). They route behind Scheduled and Calendared calls and new web leads but ahead of uncalled and End of Queue contacts. Caution: Avoid over-relying on Retry In to prevent the constant reoccurrence of the same contacts at the expense of new ones.

Similar to "Retry In" but with a set date and time that the contact should be routed for a retry. If other contacts have a higher priority, those contacts will be routed before any contacts with a "Retry At" result code selected. Note: Many factors come into play when prioritizing the routing queue. Therefore, a "Retry At" contact may not necessarily be routed at the exact date and time that was selected depending on the rest of your routing queue.

Create custom rules to determine where a contact should go in the queue. For more information on Rule-Based Routing, visit the Setup Rule Based Routing article.

Users will pick a specific date and time to schedule a callback, making it a top priority for routing when due. The scheduled callbacks are added to the calendar for easy tracking.

Allow Callers to schedule appointments for themselves or another Caller. To enable this feature, the Appointment Setting feature must be configured. More information on appointment-setting Result Codes can be found in the Create a Result Code to Schedule an Appointment article. 

This action allows active control of the calling queue through flagging and unflagging in Contact Management. A flagged contact is a contact that is in the calling queue. If a contact is unflagged, they are no longer routing through the calling queue. However, this will not close a contact. More on the difference between a closed contact and an unflagged contact can be found in the Difference Between 'Call Flag' and 'Closed Flag' article.

Sets the closed flag on the contact, removing it from the queue. The contact can be brought back into the queue by reopening and re-flagging. More on the difference between a closed contact and an unflagged contact can be found in the Difference Between 'Call Flag' and 'Closed Flag' article.

• Diversify Result Actions: Use a combination of Result Actions to balance priority for important contacts and prevent over-reliance on specific actions.
• Regularly Review and Adjust: Evaluate the effectiveness of Result Actions periodically and adjust strategies based on evolving business needs.
• Train Users: Ensure users are well-versed in utilizing Result Actions to maximize their potential for efficient contact management.