IP Library Granted Patent US 12,321,947
Granted Patent B2
US 12,321,947 · App. 17/386,370 · Granted Jun 3, 2025

Method and system for predicting next steps for customer support cases

Inventors: Parminder Singh Sethi (Ludhiana, IN); Vasanth DS (Bangalore, IN); Akanksha Goel (Bangalore, IN); Shelesh Chopra (Bangalore, IN)
Assignee: Dell Products L.P.
G06Q30/016G06N5/04G06N20/00G06Q10/06316
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,321,947
App. No.
17/386,370
Granted
Jun 3, 2025
Kind
B2
Abstract

Techniques described herein relate to a method for managing support cases of clients. The method may include obtaining a support case associated with a client of the clients; in response to obtaining the support case, obtaining contextual information associated with the support case; obtaining client telemetry data associated with the support case; selecting a portion of training data that is similar to the support case based on the client telemetry data, the contextual information, and the support case; generating a prediction model using the portion of the training data and a classification algorithm; and generating predictions using the prediction model, the client telemetry data, the contextual information, and the support case.

Claims (80)

1. A method for managing support cases associated with clients, comprising:

obtaining, by a computing device, a support case associated with a failure of a client of the clients;

in response to obtaining the support case:

obtaining, by the computing device, contextual information associated with the support case, wherein the contextual information comprises:

client component identifiers,

client component types,

client component performance information,

temperature information, and

issue severity;

obtaining, by the computing device, client telemetry data associated with the support case;

selecting, by the computing device, a portion of training data that is similar to the support case based on a similarity calculation between the client telemetry data, the contextual information, and the support case and the training data, wherein the training data comprises past contextual information from previous support cases of the clients, wherein the portion of the training data comprises baseline training data stored on a training data repository;

generating, by the computing device, a prediction model by executing a classification algorithm using the portion of the training data, wherein the prediction model reflects a subset of features included in the portion of the training data; and

generating, by the computing device, predictions by executing the prediction model using the client telemetry data, the contextual information, and the support case, wherein generating the predictions using the client telemetry data, the contextual information, and the support case comprises:

identifying a number of times each prediction of the predictions occurs in the predictions, and

ranking the predictions of the predictions based on the number of times each prediction occurs to generate ranked predictions, wherein a highest occurring prediction is ranked highest.

2. The method of claim 1 , wherein the predictions comprise steps to be taken by a user to resolve the support case.

3. The method of claim 1 , wherein selecting the portion of the training data comprises:

generating similarity scores between previous support cases included in the training data and the support case; and

selecting the portion of the training data, wherein the portion of the training data comprises support cases associated with similarity scores above a threshold similarity score.

4. The method of claim 1 , wherein generating predictions using the prediction model, the client telemetry data, the contextual information, and the support case further comprises:

generating the predictions by applying the prediction model to the client telemetry data, the contextual information, and the support case;

providing the ranked predictions to a user via a graphical user interface;

obtaining a portion of the ranked predictions, wherein the portion of the ranked predictions were used by the user to resolve the support case; and

updating a cyclic training data of the training data repository to include the support case, the contextual information, the client telemetry data, and the portion of the predictions, wherein the updated cyclic training data is used to train new prediction models for new support cases.

5. The method of claim 4 , wherein the portion of the ranked predictions comprise the portion of the predictions that were used by the user to resolve the support case.

6. The method of claim 4 , wherein the cyclic training data comprises more data than the training data.

7. A non-transitory computer readable medium comprising computer readable program code, which when executed by a computer processor enables the computer processor to perform a method for managing support cases associated with clients, wherein the method comprising:

obtaining, by a computing device, a support case associated with a failure of a client of the clients;

in response to obtaining the support case:

obtaining, by the computing device, contextual information associated with the support case, wherein the contextual information comprises:

client component identifiers,

client component types,

client component performance information,

temperature information, and

issue severity;

obtaining, by the computing device, client telemetry data associated with the support case;

selecting, by the computing device, a portion of training data that is similar to the support case based on a similarity calculation between the client telemetry data, the contextual information, and the support case and the training data, wherein the training data comprises past contextual information from previous support cases of the clients, wherein the portion of the training data comprises baseline training data stored on a training data repository;

generating, by the computing device, a prediction model by executing a classification algorithm using the portion of the training data, wherein the prediction model reflects a subset of features included in the portion of the training data; and

generating, by the computing device, predictions by executing the prediction model using the client telemetry data, the contextual information, and the support case, wherein generating the predictions using the client telemetry data, the contextual information, and the support case comprises:

identifying a number of times each prediction of the predictions occurs in the predictions, and

ranking the predictions of the predictions based on the number of times each prediction occurs to generate ranked predictions, wherein a highest occurring prediction is ranked highest.

8. The non-transitory computer readable medium of claim 7 , wherein the predictions comprise steps to be taken by a user to resolve the support case.

9. The non-transitory computer readable medium of claim 7 , wherein selecting the portion of the training data comprises:

generating similarity scores between previous support cases included in the training data and the support case; and

selecting the portion of the training data, wherein the portion of the training data comprises support cases associated with similarity scores above a threshold similarity score.

10. The non-transitory computer readable medium of claim 7 , wherein generating predictions using the prediction model, the client telemetry data, the contextual information, and the support case further comprises:

generating the predictions by applying the prediction model to the client telemetry data, the contextual information, and the support case;

providing the ranked predictions to a user via a graphical user interface;

obtaining a portion of the ranked predictions, wherein the portion of the ranked predictions were used by the user to resolve the support case; and

updating a cyclic training data of the training data repository to include the support case, the contextual information, the client telemetry data, and the portion of the predictions, wherein the updated cyclic training data is used to train new prediction models for new support cases.

11. The non-transitory computer readable medium of claim 10 , wherein the portion of the ranked predictions comprise the portion of the predictions that were used by the user to resolve the support case.

12. The non-transitory computer readable medium of claim 10 , wherein the cyclic training data comprises more data than the training data.

13. A system for managing support cases associated with clients, the system comprising:

a persistent storage comprising a training data repository;

a computing device, comprising a processor and memory, configured to:

obtain a support case associated with a failure of a client of the clients;

in response to obtaining the support case:

obtain contextual information associated with the support case, wherein the contextual information comprises:

client component identifiers,

client component types,

client component performance information,

temperature information, and

issue severity;

obtain client telemetry data associated with the support case;

select a portion of the training data that is similar to the support case based on a similarity calculation between the client telemetry data, the contextual information, and the support case and the training data, wherein the training data comprises past contextual information from previous support cases of the clients, wherein the portion of the training data comprises baseline training data stored on a training data repository;

generate a prediction model by executing a classification algorithm using the portion of the training data, wherein the prediction model reflects a subset of features included in the portion of the training data; and

generate predictions by executing the prediction model using the client telemetry data, the contextual information, and the support case, wherein generating the predictions using the client telemetry data, the contextual information, and the support case comprises:

identifying a number of times each prediction of the predictions occurs in the predictions, and

ranking the predictions of the predictions based on the number of times each prediction occurs to generate ranked predictions, wherein a highest occurring prediction is ranked highest.

14. The system of claim 13 , wherein the predictions comprise steps to be taken by a user to resolve the support case.

15. The system of claim 13 , wherein selecting the portion of the training data comprises:

generating similarity scores between previous support cases included in the training data and the support case; and

selecting the portion of the training data, wherein the portion of the training data comprises support cases associated with similarity scores above a threshold similarity score.

16. The system of claim 13 , wherein generating predictions using the prediction model, the client telemetry data, the contextual information, and the support case comprises:

generating the predictions by applying the prediction model to the client telemetry data, the contextual information, and the support case;

providing the ranked predictions to a user via a graphical user interface;

obtaining a portion of the ranked predictions, wherein the portion of the ranked predictions were used by the user to resolve the support case; and

updating a cyclic training data of the training data repository to include the support case, the contextual information, the client telemetry data, and the portion of the predictions, wherein the updated cyclic training data is used to train new prediction models for new support cases.

17. The system of claim 16 , wherein the portion of the ranked predictions comprise the portion of the predictions that were used by the user to resolve the support case.

18. The system of claim 16 , wherein the cyclic training data comprises more data than the training data.

Assignments (8)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (058014/0560) Recorded Jun 10, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
Reel/Frame 062022/0473 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (057931/0392) Recorded Jun 10, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
Reel/Frame 062022/0382 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (057758/0286) Recorded Jun 10, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
Reel/Frame 061654/0064 →
SECURITY INTEREST Recorded Oct 6, 2021
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 058014/0560 →
SECURITY INTEREST Recorded Oct 6, 2021
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 057758/0286 →
SECURITY INTEREST Recorded Oct 6, 2021
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 057931/0392 →
SECURITY AGREEMENT Recorded Oct 1, 2021
From: DELL PRODUCTS, L.P.; EMC IP HOLDING COMPANY LLC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 057682/0830 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 30, 2021
From: SETHI, PARMINDER SINGH; DS, VASANTH; GOEL, AKANKSHA; CHOPRA, SHELESH
To: EMC IP HOLDING COMPANY LLC
Reel/Frame 057032/0493 →
Priority Claims (1)
IN 202141026090 · Jun 11, 2021 · national
Continuity (1)
Related Publication 20220398599A1 · Dec 15, 2022
References Cited (150)
US 6697962B1 · Mccrory · 2004 [cited by applicant]
US 7698131B2 · Bennett · 2010 [cited by applicant]
US 7970720B1 · Heidenreich et al. · 2011 [cited by applicant]
US 8577016B1 · Duva et al. · 2013 [cited by applicant]
US 9602560B1 · Moody · 2017 [cited by applicant]
US 9754263B1 · Apple · 2017 [cited by applicant]
US 9922649B1 · Lore et al. · 2018 [cited by applicant]
US 10048996B1 · Bell et al. · 2018 [cited by applicant]
US 10192179B1 · Agarwal · 2019 [cited by applicant]
US 10410219B1 · El-nakib · 2019 [cited by applicant]
US 10721142B1 · Mathur et al. · 2020 [cited by applicant]
US 10956822B1 · Kern et al. · 2021 [cited by applicant]
US 11436642B1 · Podgorny et al. · 2022 [cited by applicant]
US 11461787B1 · Riley · 2022 [cited by applicant]
US 11561849B1 · Kairali et al. · 2023 [cited by applicant]
US 20010047270A1 · Gusick et al. · 2001 [cited by applicant]
US 20020022986A1 · Coker et al. · 2002 [cited by applicant]
US 20030041088A1 · Wilson · 2003 [cited by applicant]
US 20040162724A1 · Hill et al. · 2004 [cited by applicant]
US 20050105712A1 · Williams et al. · 2005 [cited by applicant]
US 20060010110A1 · Kim · 2006 [cited by examiner]
US 20060080107A1 · Hill et al. · 2006 [cited by applicant]
US 20070276631A1 · Subramanian et al. · 2007 [cited by applicant]
US 20080152122A1 · Idan et al. · 2008 [cited by applicant]
US 20090083246A1 · Coker et al. · 2009 [cited by applicant]
US 20090228264A1 · Williams et al. · 2009 [cited by applicant]
US 20100050074A1 · Nachmani et al. · 2010 [cited by applicant]
US 20110055122A1 · Andreoli · 2011 [cited by applicant]
US 20110071869A1 · Obrien et al. · 2011 [cited by applicant]
US 20110118932A1 · Singh et al. · 2011 [cited by applicant]
US 20110320228A1 · Kowalski · 2011 [cited by applicant]
US 20120102371A1 · Tonouchi · 2012 [cited by applicant]
US 20120185290A1 · Mueller · 2012 [cited by applicant]
US 20130110520A1 · Cheyer et al. · 2013 [cited by applicant]
US 20130268260A1 · Lundberg et al. · 2013 [cited by applicant]
US 20140067375A1 · Wooters · 2014 [cited by applicant]
US 20140281739A1 · Tuffs · 2014 [cited by applicant]
US 20140324276A1 · Weaks · 2014 [cited by applicant]
US 20140337377A1 · De Assuncao et al. · 2014 [cited by applicant]
US 20140344565A1 · Wu · 2014 [cited by applicant]
US 20150088784A1 · Dhara et al. · 2015 [cited by applicant]
US 20150127322A1 · Clark · 2015 [cited by applicant]
US 20150180985A1 · Seibert · 2015 [cited by applicant]
US 20150193429A1 · Bohra et al. · 2015 [cited by applicant]
US 20150278534A1 · Thiyagarajan · 2015 [cited by applicant]
US 20150310445A1 · Chan et al. · 2015 [cited by applicant]
US 20160027019A1 · Michaelangelo et al. · 2016 [cited by applicant]
US 20160055044A1 · Kawai et al. · 2016 [cited by applicant]
US 20160132812A1 · Beasley et al. · 2016 [cited by applicant]
US 20160171505A1 · Johri et al. · 2016 [cited by applicant]
US 20160179928A1 · Alkov et al. · 2016 [cited by applicant]
US 20160371756A1 · Yokel · 2016 [cited by applicant]
US 20170011308A1 · Sun et al. · 2017 [cited by applicant]
US 20170060995A1 · Boule et al. · 2017 [cited by applicant]
US 20170068976A1 · Wawrzynowicz · 2017 [cited by applicant]
US 20170109222A1 · Singh et al. · 2017 [cited by applicant]
US 20170132060A1 · Nomura et al. · 2017 [cited by applicant]
US 20170169325A1 · Mccord et al. · 2017 [cited by applicant]
US 20170230312A1 · Barrett et al. · 2017 [cited by applicant]
US 20170270419A1 · Sánchez et al. · 2017 [cited by applicant]
US 20180007204A1 · Klein · 2018 [cited by applicant]
US 20180012231A1 · Sapoznik et al. · 2018 [cited by applicant]
US 20180095814A1 · Patil · 2018 [cited by applicant]
US 20180129785A1 · Pal · 2018 [cited by applicant]
US 20180174020A1 · Wu · 2018 [cited by applicant]
US 20180191903A1 · Yokel · 2018 [cited by applicant]
US 20180278687A1 · Handa · 2018 [cited by applicant]
US 20180285320A1 · Yang et al. · 2018 [cited by applicant]
US 20180322509A1 · Walthers et al. · 2018 [cited by applicant]
US 20180329768A1 · Bikumala et al. · 2018 [cited by applicant]
US 20180349394A1 · Hu · 2018 [cited by applicant]
US 20190108270A1 · Dunne et al. · 2019 [cited by applicant]
US 20190163594A1 · Hayden et al. · 2019 [cited by applicant]
US 20190196682A1 · Madafferi · 2019 [cited by applicant]
US 20190228107A1 · Trim et al. · 2019 [cited by applicant]
US 20190228296A1 · Gefen et al. · 2019 [cited by applicant]
US 20190228315A1 · Xu et al. · 2019 [cited by applicant]
US 20190236132A1 · Zhu · 2019 [cited by examiner]
US 20190268470A1 · Amir et al. · 2019 [cited by applicant]
US 20190340249A1 · Connell, II · 2019 [cited by applicant]
US 20190349321A1 · Cai · 2019 [cited by examiner]
US 20190355042A1 · Swierk et al. · 2019 [cited by applicant]
US 20200013070A1 · Walthers et al. · 2020 [cited by applicant]
US 20200027094A1 · Consalvo et al. · 2020 [cited by applicant]
US 20200133755A1 · Bansal et al. · 2020 [cited by applicant]
US 20200184355A1 · Mehta · 2020 [cited by applicant]
US 20200218492A1 · Farivar · 2020 [cited by applicant]
US 20200240875A1 · Venkateswaran et al. · 2020 [cited by applicant]
US 20200302018A1 · Turkkan · 2020 [cited by examiner]
US 20200311738A1 · Gupta et al. · 2020 [cited by applicant]
US 20200364638A1 · Molloy et al. · 2020 [cited by applicant]
US 20210103703A1 · Galitsky · 2021 [cited by applicant]
US 20210109832A1 · Ladkani · 2021 [cited by applicant]
US 20210136195A1 · Adibi et al. · 2021 [cited by applicant]
US 20210157985A1 · Rotkop et al. · 2021 [cited by applicant]
US 20210208971A1 · Srinivasan · 2021 [cited by applicant]
US 20210209635A1 · Czajka et al. · 2021 [cited by applicant]
US 20210264438A1 · Singh · 2021 [cited by applicant]
US 20210319189A1 · Trehan · 2021 [cited by applicant]
US 20210357598A1 · Li · 2021 [cited by applicant]
US 20220019935A1 · Ghatage et al. · 2022 [cited by applicant]
US 20220036175A1 · Krishnamurthy et al. · 2022 [cited by applicant]
US 20220050733A1 · Selvaraju · 2022 [cited by applicant]
US 20220066791A1 · Drury · 2022 [cited by applicant]
US 20220067746A1 · Thakkar · 2022 [cited by applicant]
US 20220068263A1 · Roy · 2022 [cited by applicant]
US 20220094789A1 · Lau et al. · 2022 [cited by applicant]
US 20220129257A1 · Touati et al. · 2022 [cited by applicant]
US 20220172079A1 · Kalandyk et al. · 2022 [cited by applicant]
US 20220172222A1 · Chin et al. · 2022 [cited by applicant]
US 20220197725A1 · Liu · 2022 [cited by applicant]
US 20220208188A1 · Yoffe et al. · 2022 [cited by applicant]
US 20220215273A1 · Sethi · 2022 [cited by examiner]
US 20220308943A1 · Srinivasan et al. · 2022 [cited by applicant]
US 20220394348A1 · Hatambeiki et al. · 2022 [cited by applicant]
US 20220398383A1 · Sethi et al. · 2022 [cited by applicant]
US 20220400060A1 · Sethi et al. · 2022 [cited by applicant]
US 20230047346A1 · Daniel et al. · 2023 [cited by applicant]
US 20230053913A1 · De Souza et al. · 2023 [cited by applicant]
US 20230073644A1 · Thakkar et al. · 2023 [cited by applicant]
US 20230132116A1 · Sethi et al. · 2023 [cited by applicant]
CA 2568137A1 · 2007 [cited by applicant]
CA 2793743A1 · 2011 [cited by applicant]
CA 3052174A1 · 2020 [cited by examiner]
CA 3206778A1 · 2022 [cited by examiner]
CA 2867335C · 2023 [cited by applicant]
CN 105493446A · 2016 [cited by applicant]
CN 108415789A · 2018 [cited by applicant]
CN 113127746A · 2021 [cited by applicant]
EP 1873699A1 · 2008 [cited by applicant]
EP 1602102B1 · 2010 [cited by applicant]
WO 9858356A2 · 1998 [cited by applicant]
WO 2009087489A1 · 2009 [cited by applicant]
WO 2013151808A1 · 2013 [cited by applicant]
WO WO2014043623A1 · 2014 [cited by examiner]
WO 2021050170A1 · 2021 [cited by applicant]
Walid Maalej, Mathias Ellmanna, Romain Robbes, Using contexts similarity to predict relationships between tasks, The Journal of Systems and Software, Published by Elsevier Inc., 2017. (Year: 2017). [cited by examiner]
Dhoolia et al., “A cognitive system for business and technical support: A case study”, 2017, IBM Journal of Research and Development, vol. 61, No. 1, paper 7, pp. 74-85 (Year: 2017). [cited by applicant]
Law et al., “An Integrated Case-Based Reasoning Approach for Intelligent Help Desk Fault Management”, 1997, Expert Systems with Applications, vol. 13, No. 4, pp. 265-274 (Year: 1997). [cited by applicant]
Anonymous, “Cloud-Based Contact Center Market Next Big Thing / Major Giants Five9, CloudTalk, Talkdesk”, M2 Presswire (Year: 2021). [cited by applicant]
Caporuscio Mauro et al., “Smart-troubleshooting connected devices: Concept, challenges and opportunities”, Future Generation Computer Systems, Elsevier Science Publishers. Amsterdam, NL, vol. 111. Sep. 16, 2019, pp. 681… [cited by applicant]
International Search Report and Written Opinion mailed May 8, 2023, issued in corresponding PCT Application No. PCT/US2023/010749. [cited by applicant]
Shannon Keown, “What Call Center Location is Right for You? (& Considerations)”, Sep. 1, 2021. [cited by applicant]
Unknown, “Multi-Site Contact Centers—Can they work for your business?”, May 13, 2021. [cited by applicant]
Mark Granger, “ServiceNow products and services explained”, https://web/archive.org/web/20210420101531/https://www.nelsonfrank.com/insights/servicenow-products-services-explained <accessed date Aug. 12, 2022>, 10 pages. [cited by applicant]
Anonymous, “Retailcustomerexperience.com—Networld Media Group: 5 best practices for building the omnichannel customer service strategy”, Newstex Entrepreneurship Blogs, 2019 (Year: 2019), pp. 1-2. [cited by applicant]
Anonymous, “Chongqing Centre Service Outsourcing Ind Files Chinese Patent Application for Call Center Service Management System”, Global IP News.Information Technology Patent News, 2020 (Year: 2020). [cited by applicant]
D. Hoogeveen et al., “Detecting misflagged duplicate questions in community question-answering archives”, 12th International AAAI Conference on Web and Social Media, ICWSM 2018 (Year: 2018). [cited by applicant]
T. E. Workman et al., “Rethinking information delivery: using a natural language processing application for point-of-care data discovery*[dagger]”, Journal of the Medical Library Association, vol. 100, (2), pp. 113-120,… [cited by applicant]
Ranchal et al, “Protection of Identity Information in Cloud Computing without Trusted Third Party”, 2010 29th IEEE International Symposium on Reliable Distributed Systems, pp. 368-372. [cited by applicant]