IP Library Granted Patent US 12,418,451
Granted Patent B2
US 12,418,451 · App. 18/203,021 · Granted Sep 16, 2025

Live-monitoring to trigger agent instance modification actions via an in-house management network

Inventors: Matthew Grady McConnell (Johns Creek, GA); Christopher Powell Busbee (Marietta, GA); Kevin Wilson (Bradenton, FL); Eric Victor Drucker (Roswell, GA); Jennifer Christine East (Milton, GA); Michael Carl Jarus (Suwanee, GA); Jennifer Lee (Hays, KS); Harper Flores (Cleveland, TX)
Assignee: Intradiem, Inc.
H04L41/046G06F9/54H04L63/08
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 12,418,451
App. No.
18/203,021
Granted
Sep 16, 2025
Kind
B2
Abstract

A computer-implemented method for managing a contact center one or more processors in a management network (a) receiving, from an end-user network, data associated with a plurality of agent instances servicing incoming communications for the contact center, wherein the contact center, the end-user network, and the management network are associated with the enterprise; (b) determining, based on a specification of a logical directive, an operation to be performed in relation to the plurality of agent instances, the specification of the logical directive having at least one condition that, if satisfied by the received data associated with the plurality of agent instances servicing the incoming communications for the contact center, defines the operation to be performed; and (c) providing, to one or more servers, the determined operation to be performed, wherein the operation includes making a modification relating to (i) at least one of the plurality of agent instances and/or (ii) the servicing of the incoming communications. A computing system and article of manufacture are also provided.

Claims (44)

1. A computing system for managing a contact center for an enterprise, the computing system comprising:

one or more processors in a management network, wherein the one or more processors are configured to execute instructions stored on a non-transitory computer readable medium to perform tasks including:

receiving, from an end-user network, data associated with a plurality of agent instances servicing incoming communications for the contact center, wherein the contact center, the end-user network, and the management network are associated with the enterprise;

determining, based on a specification of a logical directive, an operation to be performed in relation to the plurality of agent instances, the specification of the logical directive having at least one condition that, if satisfied by the received data associated with the plurality of agent instances servicing the incoming communications for the contact center, defines the operation to be performed; and

providing, to one or more servers, the determined operation to be performed, wherein the operation includes making a modification relating to (a) at least one of the plurality of agent instances and/or (b) the servicing of the incoming communications.

2. The computing system of claim 1 , wherein the operation is selected from the group consisting of (a) changing a state of at least one particular agent instance in the plurality of agent instances, (b) modifying an assigned schedule for the at least one particular agent instance, and (c) modifying an assigned queue of the at least one particular agent instance.

3. The computing system of claim 1 , wherein each agent instance in the plurality of agent instances is a computing device associated with one or more unique contact center agents, and wherein each of the one or more unique contact center agents is either a human agent or a robotic agent.

4. The computing system of claim 1 , wherein each agent instance is a chat bot.

5. The computing system of claim 1 , wherein the one or more servers comprise at least one of (a) a communication distributor server, (b) a workforce management server, or (c) a back-office case system server.

6. The computing system of claim 1 , wherein providing the determined operation comprises the one or more processors disposed within the management network making an application programming interface (API) request to the one or more servers to initiate the modification relating to (a) the at least one of the plurality of agent instances and/or (b) the servicing of the incoming communications.

7. The computing system of claim 1 , wherein the specification of the logical directive comprises a trigger, and wherein the tasks further comprise:

determining whether the trigger has occurred, based on the received data associated with the plurality of agent instances servicing the incoming communications for the contact center; and

determining whether the at least one condition in the specification is satisfied only upon determining that the trigger has occurred, and otherwise waiting to determine whether the at least one condition in the specification is satisfied until determining that the trigger has occurred.

8. The computing system of claim 7 , wherein the specification defines the trigger in relation to a threshold.

9. The computing system of claim 8 , wherein the threshold is an adaptive threshold that is modified by the one or more processors in the management network in response to (a) accumulating the received data associated with the plurality of agent instances servicing the incoming communications for the contact center, (b) identifying at least one trend in the accumulated received data and comparing to at least one defined goal, and (c) determining a modified threshold for the trigger based on a relation between the identified at least one trend and the at least one defined goal.

10. The computing system of claim 1 , wherein if a component of the received data will fail to satisfy the at least one condition in the specification of the logical directive, the one or more processors in the management network are configured to prevent further evaluation of the component of the received data.

11. The computing system of claim 1 , wherein receiving data associated with the plurality of agent instances servicing the incoming communications for the contact center comprises receiving data associated with processes of the one or more servers.

12. The computing system of claim 11 , wherein receiving data associated with the processes of the one or more servers involves the management network requesting data from a proxy server disposed on the end-user network.

13. The computing system of claim 1 , wherein making the modification relating to the at least one of the plurality of agent instances includes at least one of (a) initiating a software update to the at least one of the plurality of agent instances or (b) providing a coaching session to the at least one of the plurality of agent instances.

14. The computing system of claim 1 , wherein both the management network and the end-user network are administered by the enterprise and are on a network administered by the enterprise to manage only the contact center associated with an enterprise and not any other contact center associated with any other enterprise.

15. The computing system of claim 1 , wherein at least one of the one or more servers is a cloud-based server owned and/or hosted by a third-party entity distinctly different from the enterprise, and wherein the specification of the logical directive includes an authentication mechanism for use by the management network to access the one or more servers.

16. A computer-implemented method for managing a contact center for an enterprise, the method including tasks performed by one or more processors in a management network, the method comprising:

receiving, from an end-user network, data associated with a plurality of agent instances servicing incoming communications for the contact center, wherein the contact center, the end-user network, and the management network are associated with the enterprise;

determining, based on a specification of a logical directive, an operation to be performed in relation to the plurality of agent instances, the specification of the logical directive having at least one condition that, if satisfied by the received data associated with the plurality of agent instances servicing the incoming communications for the contact center, defines the operation to be performed; and

providing, to one or more servers, the determined operation to be performed, wherein the operation includes making a modification relating to (a) at least one of the plurality of agent instances and/or (b) the servicing of the incoming communications.

17. The computer-implemented method of claim 16 , wherein the operation is selected from the group consisting of (a) changing a state of at least one particular agent instance in the plurality of agent instances, (b) modifying an assigned schedule for the at least one particular agent instance, and (c) modifying an assigned queue of the at least one particular agent instance.

18. The computer-implemented method of claim 16 , wherein each agent instance in the plurality of agent instances is a computing device associated with one or more unique contact center agents, and wherein each of the one or more unique contact center agents is either a human agent or a robotic agent.

19. The computer-implemented method of claim 16 , wherein the one or more servers comprise at least one of (a) a communication distributor server, (b) a workforce management server, or (c) a back-office case system server.

20. The computer-implemented method of claim 16 , wherein the specification of the logical directive comprises a trigger, and wherein the method further comprises:

determining whether the trigger has occurred, based on the received data associated with the plurality of agent instances servicing the incoming communications for the contact center; and

determining whether the at least one condition in the specification is satisfied only upon determining that the trigger has occurred, and otherwise waiting to determine whether the at least one condition in the specification is satisfied until determining that the trigger has occurred.

21. The computer-implemented method of claim 20 , wherein the specification defines the trigger in relation to a threshold.

22. The computer-implemented method of claim 21 , wherein the threshold is an adaptive threshold that is modified by the one or more processors in the management network in response to (a) accumulating the received data associated with the plurality of agent instances servicing the incoming communications for the contact center, (b) identifying at least one trend in the accumulated received data and comparing to at least one defined goal, and (c) determining a modified threshold for the trigger based on a relation between the identified at least one trend and the at least one defined goal.

23. The computer-implemented method of claim 16 , wherein if a component of the received data will fail to satisfy the at least one condition in the specification of the logical directive, the one or more processors in the management network are configured to prevent further evaluation of the component of the received data.

24. The computer-implemented method of claim 16 , wherein receiving data associated with the plurality of agent instances servicing incoming communications for the contact center comprises receiving data associated with processes of the one or more servers.

25. The computer-implemented method of claim 16 , wherein making the modification relating to the at least one of the plurality of agent instances includes at least one of (a) initiating a software update to the at least one of the plurality of agent instances or (b) providing a coaching session to the at least one of the plurality of agent instances.

26. The computer-implemented method of claim 16 , wherein both the management network and the end-user network are administered by the enterprise and are on a network administered by the enterprise to manage only the contact center associated with an enterprise and not any other contact center associated with any other enterprise.

27. An article of manufacture including a non-transitory computer-readable medium, having stored thereon program instructions that, upon execution by one or more processors in a management network, cause the one or more processors to perform tasks comprising:

receiving data associated with a plurality of agent instances servicing incoming communications for a contact center in an end-user network associated with an enterprise, wherein both the management network and the end-user network are administered by the enterprise to manage only the contact center on behalf of the enterprise and not any other contact center associated with any other enterprise;

determining, based on a specification of a logical directive, an operation to be performed in relation to the plurality of agent instances, the specification of the logical directive having at least one condition that, if satisfied by the received data associated with the plurality of agent instances servicing the incoming communications for the contact center, defines the operation to be performed by the one or more servers, the servers comprising at least one of (a) a communication distributor server, (b) a workforce management server, or (c) a back-office case system server; and

providing, to one or more servers, the determined operation to be performed, wherein the operation includes making a modification relating to (a) at least one of the plurality of agent instances and/or (b) the servicing of the incoming communications.

28. The article of manufacture of claim 27 , wherein the operation is selected from the group consisting of (a) changing a state of at least one particular agent instance in the plurality of agent instances, (b) modifying an assigned schedule for the at least one particular agent instance, and (c) modifying an assigned queue of the at least one particular agent instance.

29. The article of manufacture of claim 27 , wherein each agent instance in the plurality of agent instances is a computing device associated with one or more unique contact center agents, and wherein each of the one or more unique contact center agents is either a human agent or a robotic agent.

30. The article of manufacture of claim 27 , wherein receiving data associated with the plurality of agent instances servicing incoming communications for the contact center comprises receiving data associated with processes of the one or more servers.

Assignments (3)
SECURITY AGREEMENT Recorded May 31, 2024
From: INTRADIEM, INC.
To: BMO BANK N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 067596/0408 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 29, 2023
From: BUSBEE, CHRISTOPHER POWELL; EAST, JENNIFER CHRISTINE; JARUS, MICHAEL CARL; LEE, JENNIFER; WILSON, KEVIN; FLORES, HARPER
To: INTRADIEM, INC.
Reel/Frame 063786/0582 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 29, 2023
From: MCCONNELL, MATTHEW GRADY; DRUCKER, ERIC VICTOR
To: INTRADIEM, INC.
Reel/Frame 063786/0586 →
Continuity (17)
Continuation 17966457 · Oct 14, 2022
Continuation In Part 17739655 · May 9, 2022
Continuation 17493760 · Oct 4, 2021
Continuation In Part 17364851 · Jun 30, 2021
Continuation In Part 17163126 · Jan 29, 2021
Continuation In Part 17061024 · Oct 1, 2020
Continuation 16912351 · Jun 25, 2020
Continuation 16804376 · Feb 28, 2020
Continuation 16580258 · Sep 24, 2019
Continuation In Part 17364851 · Jun 30, 2021
Continuation In Part 17382311 · Jul 21, 2021
Continuation 17364851 · Jun 30, 2021
Continuation In Part 17061024 · Oct 1, 2020
Continuation In Part 17163126 · Jan 29, 2021
Continuation In Part 17061024 · Oct 1, 2020
Continuation 16804376 · Feb 28, 2020
Related Publication 20230308340A1 · Sep 28, 2023
References Cited (60)
US 5790798A · Beckett et al. · 1998 [cited by applicant]
US 6324282B1 · McIllwaine et al. · 2001 [cited by applicant]
US 6628777B1 · McIllwaine et al. · 2003 [cited by applicant]
US 6700971B1 · Cohen et al. · 2004 [cited by applicant]
US 7023979B1 · Wu et al. · 2006 [cited by applicant]
US 7411939B1 · Lamb et al. · 2008 [cited by applicant]
US 7676034B1 · Wu et al. · 2010 [cited by applicant]
US 8300797B1 · Benesh · 2012 [cited by examiner]
US 8364509B1 · Marr · 2013 [cited by applicant]
US 8391465B1 · Porter · 2013 [cited by applicant]
US 8488769B1 · Noble, Jr. et al. · 2013 [cited by applicant]
US 8533743B2 · Houck et al. · 2013 [cited by applicant]
US 8644489B1 · Noble, Jr. et al. · 2014 [cited by applicant]
US 8675860B2 · Eicholz et al. · 2014 [cited by applicant]
US 8767948B1 · Riahi et al. · 2014 [cited by applicant]
US 8824664B1 · Ristock et al. · 2014 [cited by applicant]
US 8938063B1 · Hackbarth · 2015 [cited by examiner]
US 8971520B1 · Bryce et al. · 2015 [cited by applicant]
US 9047269B2 · Armstrong et al. · 2015 [cited by applicant]
US 9680995B2 · Tendick et al. · 2017 [cited by applicant]
US 9766953B2 · Beckett et al. · 2017 [cited by applicant]
US 9832315B1 · Jayapalan · 2017 [cited by examiner]
US 10268525B2 · Beckett et al. · 2019 [cited by applicant]
US 10289262B2 · Lockwood et al. · 2019 [cited by applicant]
US 10554817B1 · Sullivan et al. · 2020 [cited by applicant]
US 20020114441A1 · Coussement · 2002 [cited by applicant]
US 20030195653A1 · Lewis · 2003 [cited by examiner]
US 20040193468A1 · Mosquera et al. · 2004 [cited by applicant]
US 20050135601A1 · Whitman · 2005 [cited by applicant]
US 20060256953A1 · Pulaski · 2006 [cited by examiner]
US 20070206768A1 · Bourne et al. · 2007 [cited by applicant]
US 20080019500A1 · Torres et al. · 2008 [cited by applicant]
US 20080037761A1 · Cordell et al. · 2008 [cited by applicant]
US 20080123839A1 · Mccormack et al. · 2008 [cited by applicant]
US 20100198647A1 · Bowers, Jr. et al. · 2010 [cited by applicant]
US 20100303225A1 · Shashkov et al. · 2010 [cited by applicant]
US 20120284356A1 · Luna · 2012 [cited by applicant]
US 20120321070A1 · Smith et al. · 2012 [cited by applicant]
US 20130191185A1 · Galvin · 2013 [cited by applicant]
US 20140079207A1 · Zhakov et al. · 2014 [cited by applicant]
US 20140249873A1 · Stephan et al. · 2014 [cited by applicant]
US 20150074170A1 · Steiner et al. · 2015 [cited by applicant]
US 20150092936A1 · Riefel et al. · 2015 [cited by applicant]
US 20160094411A1 · Brennan · 2016 [cited by examiner]
US 20170111509A1 · McGann · 2017 [cited by examiner]
US 20180091651A1 · Slovacek · 2018 [cited by applicant]
US 20180197123A1 · Parimelazhagan et al. · 2018 [cited by applicant]
US 20180316729A1 · Chauvet et al. · 2018 [cited by applicant]
US 20180375998A1 · Beilis et al. · 2018 [cited by applicant]
US 20190207815A1 · Kirner et al. · 2019 [cited by applicant]
US 20190245973A1 · Dwyer et al. · 2019 [cited by applicant]
US 20190260779A1 · Bazalgette et al. · 2019 [cited by applicant]
US 20210136222A1 · Brown et al. · 2021 [cited by applicant]
US 20210266405A1 · Stepanov et al. · 2021 [cited by applicant]
US 20230388176A1 · McConnell et al. · 2023 [cited by applicant]
EP 1209887A2 · 2002 [cited by applicant]
U.S. Appl. No. 17/163,126, filed Jan. 29, 2021, Christopher Busbee. [cited by applicant]
“Hyperautomation Platform,” AppBus, https://www.appbus.com/platform/, accessed Mar. 4, 2021. [cited by applicant]
Qstory. How Intraday Automation Can Help Your Call Centre. Date unknown, p. 1-8, United Kingdom. [cited by applicant]
Qstory. Real-Time Management: Gaining real efficiencies in your Contact Centre. Date unknown, p. 1-8, United Kingdom. [cited by applicant]