IP Library Granted Patent US 9,692,893
Granted Patent B1
US 9,692,893 · App. 15/353,797 · Granted Jun 27, 2017

Pacing outbound communications that generate inbound communications

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,692,893
App. No.
15/353,797
Granted
Jun 27, 2017
Kind
B1
Abstract

Various embodiments of the invention provide methods, systems, and computer program products for pacing outbound communications that generate inbound communications. A number of outbound communications is set to be sent during a first time period and a number of inbound communications expected to be received as a result of sending the outbound communications is determined based on historical data along with a second time period during which the inbound communications are expected to be received. Accordingly, a present capacity is determined during the first time period with respect to one or more resources that are to be used during the second time period to handle the number of inbound communications expected to be received. A determination is made as to whether the present capacity is at an acceptable level and if so, then the outbound communications are sent.

Claims (31)

1. A method for pacing outbound communications that generate inbound communications for a contact center, the method comprising the steps of:

determining a number of inbound communications expected to be received as a result of sending a number of outbound communications based on a historical success rate at generating inbound communications by sending outbound communications using a same channel of communication as the number of outbound communications to be sent;

determining a present capacity of the contact center by a computer processor, wherein the present capacity is with respect to one or more resources that are to be used to handle the number of inbound communications expected to be received by the contact center;

determining by the computer processor whether a capacity with respect to the one or more resources required to handle the number of inbound communications expected to be received as a result of sending the number of outbound communications minus the present capacity is less than a threshold value; and

in response to the capacity with respect to the one or more resources required to handle the number of inbound communications expected to be received as a result of sending the number of outbound communications minus the present capacity being less than the threshold value, sending the number of outbound communications using a contact device.

2. The method of claim 1 , wherein the computer processor resides in the contact device.

3. The method of claim 1 , wherein the number of outbound communications are sent as SMS text messages or e-mails.

4. The method of claim 1 , wherein the number of expected inbound communications are received as at least one of SMS text messages, telephone calls, and e-mails.

5. The method of claim 1 , wherein the one or more resources comprise one or more of agents, trunks, hardware ports, memory, processing capacity, hardware-related licenses, software-related licenses, and bandwidth.

6. The method of claim 1 , wherein the historical success rate is based on at least one of a historical channel of communication preferred to be used for the number of expected inbound communications and a historical reply time for receiving an inbound communication generated from sending an outbound communication using the same channel of communication as the number of outbound communications to be sent.

7. A non-transitory, computer-readable medium comprising computer-executable instructions for pacing outbound communications for a contact center, that when executed cause at least one computer processor to:

determine a number of inbound communications expected to be received as a result of sending a number of outbound communications based on a historical success rate at generating inbound communications by sending outbound communications using a same channel of communication as the number of outbound communications to be sent;

determine a present capacity of the contact center, wherein the present capacity is with respect to one or more resources that are to be used to handle the number of inbound communications expected to be received by the contact center;

determine whether a capacity with respect to the one or more resources required to handle the number of inbound communications expected to be received as a result of sending the number of outbound communications minus the present capacity is less than a threshold value; and

in response to the capacity with respect to the one or more resources required to handle the number of inbound communications expected to be received as a result of sending the number of outbound communications minus the present capacity being less than the threshold value, facilitate sending the number of outbound communications.

8. The non-transitory, computer-readable medium of claim 7 , wherein the at least one computer processor resides in a contact device.

9. The non-transitory, computer-readable medium of claim 7 , wherein the number of outbound communications are sent as SMS text messages or e-mails.

10. The non-transitory, computer-readable medium of claim 7 , wherein the number of expected inbound communications are received as at least one of SMS text messages, telephone calls, and e-mails.

11. The non-transitory, computer-readable medium of claim 7 , wherein the one or more resources comprise one or more of agents, trunks, hardware ports, memory, processing capacity, hardware-related licenses, software-related licenses, and bandwidth.

12. The non-transitory, computer-readable medium of claim 7 , wherein the historical success rate is based on at least one of a historical channel of communication preferred to be used for the number of expected inbound communications and a historical reply time for receiving an inbound communication generated from sending an outbound communication using the same channel of communication as the number of outbound communications to be sent.

13. A system for pacing outbound communications for a contact center, the system comprising:

at least one computer processor configured to:

determine a number of inbound communications expected to be received as a result of sending a number of outbound communications based on a historical success rate at generating inbound communications by sending outbound communications using a same channel of communication as the number of outbound communications to be sent;

determine a present capacity of the contact center, wherein the present capacity is with respect to one or more resources that are to be used to handle the number of inbound communications expected to be received by the contact center; and

determine whether a capacity with respect to the one or more resources required to handle the number of inbound communications expected to be received as a result of sending the number of outbound communications minus the present capacity is less than a threshold value; and

a contact device configured to send the number of outbound communications in response to the capacity with respect to the one or more resources required to handle the number of inbound communications expected to be received as a result of sending the number of outbound communications minus the present capacity being less than the threshold value.

14. The system of claim 13 , wherein the at least one computer processor resides in the contact device.

15. The system of claim 13 , wherein the number of outbound communications are sent as SMS text messages or e-mails.

16. The system of claim 13 , wherein the number of expected inbound communications are received as at least one of SMS text messages, telephone calls, and e-mails.

17. The system of claim 13 , wherein the one or more resources comprise one or more of agents, trunks, hardware ports, memory, processing capacity, hardware-related licenses, software-related licenses, and bandwidth.

18. The system of claim 13 , wherein the historical success rate is based on at least one of a historical channel of communication preferred to be used for the number of expected inbound communications and a historical reply time for receiving an inbound communication generated from sending an outbound communication using the same channel of communication as the number of outbound communications to be sent.

Assignments (11)
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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 20, 2024
From: NOBLE SYSTEMS, LLC
To: ALVARIA CAYMAN (CX)
Reel/Frame 066850/0556 →
RELEASE OF SECURITY INTEREST Recorded Mar 20, 2024
From: JEFFRIES FINANCE LLC
To: ALVARIA, INC.; NOBLE SYSTEMS, LLC
Reel/Frame 066850/0428 →
RELEASE OF SECURITY INTEREST Recorded Mar 20, 2024
From: JEFFRIES FINANCE LLC
To: ALVARIA, INC.; NOBLE SYSTEMS, LLC
Reel/Frame 066850/0384 →
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 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded May 6, 2021
From: NOBLE SYSTEMS CORPORATION; ASPECT SOFTWARE, INC.
To: JEFFERIES FINANCE LLC
Reel/Frame 057674/0664 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded May 6, 2021
From: NOBLE SYSTEMS CORPORATION; ASPECT SOFTWARE, INC.
To: JEFFERIES FINANCE LLC
Reel/Frame 057261/0093 →
SECURITY INTEREST Recorded Apr 23, 2020
From: NOBLE SYSTEMS CORPORATION
To: WELLS FARGO CAPITAL FINANCE, LLC
Reel/Frame 052495/0287 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 17, 2016
From: OUIMETTE, JASON P; HAGGERTY, CHRISTOPHER S
To: NOBLE SYSTEMS CORPORATION
Reel/Frame 040351/0331 →