IP Library Granted Patent US 9,456,085
Granted Patent B1
US 9,456,085 · App. 14/333,969 · Granted Sep 27, 2016

Managing contact attempts to an account in a contact center

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,456,085
App. No.
14/333,969
Granted
Sep 27, 2016
Kind
B1
Abstract

A party associated with multiple contact addresses, such as a home, cell, and/or work telephone numbers, is contacted by a dialer using a contact attempt sequence that defines how the various contact addresses are used. A graphical user interface allows a user to create a visual representation of the contact attempt sequence flow for contacting the party, e.g., a template, where logic is defined indicating how and when the various contact addresses are to be used. Thus, in one instance, the dialer may use the template to make multiple attempts to reach the party using first their home number and then their cell phone number, and if such attempts are unsuccessful, then make a further attempt to the reach the party using their work number, wherein attempts to reach the party using the home, cell, and/or work phone numbers may be limited over one or more defined time periods.

Claims (31)

1. A method for identifying a contact address to use in attempting to contact a party associated with a delinquent account by a contact center comprising:

using a graphical user interface tool by a user to define a visual representation of a contact attempt sequence flow, wherein the visual representation of the contact attempt sequence flow comprises a plurality of icons connected in a sequential order that includes a first contact icon defining a first contact address, a second contact icon defining a second contact address, and at least one of an action icon defining an action to be carried out based on a corresponding action value defined by the user, a wait time icon defining a wait time to be carried out based on a corresponding wait time value defined by the user, and a condition icon defining a condition to be evaluated based on a corresponding condition value defined by the user;

converting the visual representation of the contact attempt sequence flow into a template representing the plurality of icons connected in the sequential order;

using the template by a dialer component to initiate contact attempts to the party; and

based on the sequential order:

initiating one or more contact attempts to the party using the first contact address defined by the first contact icon by the dialer component in response to evaluating one or more current values with respect to at least one of the corresponding action value for the action to be carried out defined by the action icon, the corresponding wait time value for the wait time to be carried out defined by the wait time icon, and the condition value for the condition to be evaluated defined by the condition icon; and

after a number of unsuccessful contact attempts has occurred using the first contact address, initiating another contact attempt to the party using the second contact address defined by the second contact icon by the dialer component in response to evaluating another one or more current values with respect to at least one of the corresponding action value for the action to be carried out defined by the action icon, the corresponding wait time value for the wait time to be carried out defined by the wait time icon, and the condition value for the condition to be evaluated defined by the condition icon, wherein the second contact address is a work telephone number and the template indicates that no more than one contact attempt per week should be initiated to the second contact address.

2. The method of claim 1 , further comprising:

using the graphical user interface tool to indicate the number of unsuccessful contact attempts that should occur using the first contact address before using the second contact address.

3. The method of claim 2 , wherein the number of unsuccessful contact attempts is indicated in a context of a defined time period.

4. The method of claim 1 , wherein the visual representation of the contact attempt sequence flow further indicates that a text call should be attempted to the party.

5. A system for initiating contact to a party associated with a delinquent account comprising:

a processor configured to:

receive input via a graphical user interface from a user for defining a visual representation of a contact attempt sequence flow, wherein the visual representation of the contact attempt sequence flow comprises a plurality of icons connected in a sequential order that includes a first contact icon defining a first contact address, a second contact icon defining a second contact address, and at least one of an action icon defining an action to be carried out based on a corresponding action value defined by the user, a wait time icon defining a wait time to be carried out based on a corresponding wait time value defined by the user, and a condition icon defining a condition to be evaluated based on a corresponding condition value defined by the user; and

convert the visual representation of the contact attempt sequence flow into a template representing the plurality of icons connected in the sequential order; and

a dialer component configured to:

use the template to initiate contact attempts to the party; and

based on the sequential order:

initiate one or more contact attempts to the party using the first contact address defined by the first contact icon in response to evaluating one or more current values with respect to at least one of the corresponding action value for the action to be carried out defined by the action icon, the corresponding wait time value for the wait time to be carried out defined by the wait time icon, and the condition value for the condition to be evaluated defined by the condition icon; and

after a number of unsuccessful contact attempts has occurred using the first contact address, initiate another contact attempt to the party using the second contact address defined by the second contact icon in response to evaluating another one or more current values with respect to at least one of the corresponding action value for the action to be carried out defined by the action icon, the corresponding wait time value for the wait time to be carried out defined by the wait time icon, and the condition value for the condition to be evaluated defined by the condition icon, wherein the second contact address is a work telephone number and the template indicates that no more than one contact attempt per week should be initiated to the second contact address.

6. The system of claim 5 , wherein the dialer component processor is further configured to:

initiate a text call to the party in response to the template indicating the text call be initiated to the party.

7. The system of claim 5 , wherein the template indicates a threshold value with respect to the number of unsuccessful contact attempts using the first contact address and a time period associated with the threshold value.

8. A non-transitory computer readable medium storing computer instructions that when executed by a dialer component cause the dialer component to:

retrieve a template created based on a visual representation of a contact attempt sequence flow defined by a user on a graphical user interface, wherein the visual representation of the contact attempt sequence flow comprises a plurality of icons connected in a sequential order that includes a first contact icon defining a first contact address, a second contact icon defining a second contact address, and at least one of an action icon defining an action to be carried out based on a corresponding action value defined by the user, a wait time icon defining a wait time to be carried out based on a corresponding wait time value defined by the user, and a condition icon defining a condition to be evaluated based on a corresponding condition value defined by the user;

use the template to initiate contact attempts to a party associated with a delinquent account; and

based on the sequential order:

initiate one or more contact attempts to the party using the first contact address defined by the first contact icon in response to evaluating one or more current values with respect to at least one of the corresponding action value for the action to be carried out defined by the action icon, the corresponding wait time value for the wait time to be carried out defined by the wait time icon, and the condition value for the condition to be evaluated defined by the condition icon; and

after a number of unsuccessful contact attempts has occurred using the first contact address, initiate another contact attempt to the party using the second contact address defined by the second contact icon in response to evaluating another one or more current values with respect to at least one of the corresponding action value for the action to be carried out defined by the action icon, the corresponding wait time value for the wait time to be carried out defined by the wait time icon, and the condition value for the condition to be evaluated defined by the condition icon, wherein the second contact address is a work telephone number and the template indicates that no more than one contact attempt per week should be initiated to the second contact address.

9. The non-transitory computer readable medium of claim 8 , wherein the instructions further cause the dialer component to:

initiate a text call to the party in response to the template indicating the text call be initiated to the party.

Assignments (10)
RELEASE OF SECURITY INTEREST Recorded Oct 27, 2025
From: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
To: ALVARIA CAYMAN (WEM); ALVARIA CAYMAN (CXIP)
Reel/Frame 073360/0209 →
PATENT SECURITY AGREEMENT Recorded Mar 20, 2024
From: ALVARIA CAYMAN (WEM); ALVARIA CAYMAN (CXIP)
To: JEFFERIES FINANCE LLC
Reel/Frame 066850/0334 →
RELEASE OF SECURITY INTEREST Recorded Mar 20, 2024
From: JEFFRIES FINANCE LLC
To: ALVARIA, INC.; NOBLE SYSTEMS, LLC
Reel/Frame 066850/0384 →
RELEASE OF SECURITY INTEREST Recorded Mar 20, 2024
From: JEFFRIES FINANCE LLC
To: ALVARIA, INC.; NOBLE SYSTEMS, LLC
Reel/Frame 066850/0428 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 20, 2024
From: NOBLE SYSTEMS, LLC
To: ALVARIA CAYMAN (CX)
Reel/Frame 066850/0556 →
CERTIFICATE OF CONVERSION Recorded Mar 12, 2024
From: NOBLE SYSTEMS CORPORATION, A GEORGIA CORPORATION
To: NOBLE SYSTEMS, LLC, A DELAWARE LIMITED LIABILITY COMPANY
Reel/Frame 066794/0435 →
RELEASE OF SECURITY INTEREST Recorded May 10, 2021
From: WELLS FARGO CAPITAL FINANCE, LLC
To: NOBLE SYSTEMS CORPORATION
Reel/Frame 056193/0363 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded May 6, 2021
From: NOBLE SYSTEMS CORPORATION; ASPECT SOFTWARE, INC.
To: JEFFERIES FINANCE LLC
Reel/Frame 057261/0093 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded May 6, 2021
From: NOBLE SYSTEMS CORPORATION; ASPECT SOFTWARE, INC.
To: JEFFERIES FINANCE LLC
Reel/Frame 057674/0664 →
AMENDMENT Recorded Jun 2, 2015
From: NOBLE SYSTEMS CORPORATION
To: WELLS FARGO CAPITAL FINANCE, LLC
Reel/Frame 035812/0507 →