IP Library Granted Patent US 8,996,642
Granted Patent B1
US 8,996,642 · App. 14/554,963 · Granted Mar 31, 2015

Systems and methods for prioritizing and servicing support tickets using a chat session

Inventors: Arnold Bellini, III (Tampa, FL); Linda Brotherton (Tampa, FL)
Assignee: ConnectWise Inc.
H04L29/08837H04N21/4788
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 8,996,642
App. No.
14/554,963
Granted
Mar 31, 2015
Kind
B1
Abstract

The present disclosure facilitates servicing information technology support tickets. In some embodiments, the system includes a server configured to access a database storing two support tickets, each of which can have a ticket identifier and information to facilitate providing information technology support to a computing device. The server can receive an indication of a status from two computing devices, each of which can be associated with one of the support tickets. The server can determine a priority of each ticket based on its status, where the priority of the first ticket is higher than the priority of the second ticket. The server can initiate a chat session associated with the first computing device and the first ticket to provide information technology support to the first computing device, based on the priority of the first ticket and the status of the first computing device.

Claims (111)

1. A method of servicing information technology tickets via a computer network, comprising:

retrieving, by a server from a database stored in memory, a first ticket having a first ticket identifier, the first ticket having first information to facilitate providing information technology support or services to a first computing device;

identifying, by the server, based on the first information, a first priority and a first chat queue for the first ticket;

receiving, by the server, an update to the first information of the first ticket;

determining, by the server responsive to the update to the first information, a second priority and a second chat queue for the first ticket, the second priority different from the first priority; and

assigning, by the server, the first ticket to the second chat queue with the second priority to initiate a first chat session associated with the first ticket and the first computing device to provide information technology support or services to the first computing device.

2. The method of claim 1 , further comprising:

identifying, by the server, a second ticket in the second chat queue with a third priority;

determining, by the server, that the third priority of the second ticket is greater less than the second priority of the first ticket; and

initiating, by the server responsive to the determination, the first chat session associated with the first ticket and the first computing device.

3. The method of claim 1 , further comprising:

identifying, by the server, a second ticket in the second chat queue with a third priority less than the second priority; and

establishing, by the server based on the second priority and the third priority, the second chat queue with the first chat session ahead of a second chat session associated with the second ticket.

4. The method of claim 1 , further comprising:

assigning the first ticket to the second chat queue responsive to the second priority being greater than the first priority.

5. The method of claim 1 , further comprising:

receiving, by the server from the first computing device associated with the first ticket, a first indication of a first status of the first computing device; and

determining, by the server, the first priority of the first ticket based on the first status.

6. The method of claim 5 , further comprising:

receiving, by the server from the first computing device associated with the first ticket, a second indication of a second status of the first computing device; and

determining, by the server, the second priority of the first support ticket based on the second status, the second priority greater than the first priority; and

assigning, by the server, the second priority to the first ticket.

7. The method of claim 1 , further comprising:

receiving, by the server from the first computing device associated with the first ticket, a first indication of interaction with one or more input devices of the first computing device, the first indication associated with a timestamp;

identifying, by the server, a current time;

determining, by the server, a time interval between the current time and the timestamp of the first indication, wherein the server has not received a subsequence subsequent indication of interaction with the one or more input devices of the first computing device during the time interval;

comparing, by the server, the time interval with a threshold to determine that the time interval is greater than or equal to the threshold;

setting, based on the comparison, a first status of the first computing device to indicate that a user of the first computing device is away; and

assigning, by the server, the first priority to the first ticket based on the first status.

8. The method of claim 7 , further comprising:

receiving, by the server subsequent to the time interval, a second indication of interaction with the one or more input devices of the first computing devices; and

setting, by the server, the second status responsive to the second indication, the second status indicating that the user of the first computing device is present.

9. The method of claim 1 , further comprising:

determining at least one of the first priority or the second priority based on at least one of a microphone, a camera, a proximity sensor, or a position sensing system.

10. The method of claim 1 , further comprising:

receiving, by the server from a second computing device, an indication to initiate a remote control session to support the first computing device in accordance with the first ticket; and

initiating, by the server responsive to the indication, the remote control session between the second computing device and the first computing device.

11. The method of claim 10 , further comprising:

monitoring, via the remote control session, outputs of the first computing device; and

controlling, via the remote control session, an input device of the first computing device to support the first computing device in accordance with the first ticket.

12. The method of claim 1 , further comprising:

receiving, by the server from a monitoring system, activity information of the first computing device; and

updating, by the server, the first ticket with the activity information.

13. The method of claim 1 , further comprising:

initiating, by the server, the first chat session associated with the first ticket and the first computing device, the first chat session initiated between the first computing device and a second computing device;

identifying, by the server, a second ticket associated with the first computing device, the second ticket having second information to facilitate providing information technology support or services to the first computing device; and

initiating, by the server, a second chat session associated with the second ticket and the first computing device, the second chat session between the first computing device and a third computing device, the second chat session at least partially overlapping with the first chat session.

14. The method of claim 1 , further comprising:

initiating, by the server, the first chat session associated with the first ticket and the first computing device, the first chat session initiated between the first computing device and a second computing device; and

adding, by the server, a third computing device to the first chat session, the first chat session configured to display messages from each of the first computing device, second computing device and third computing device to participants of the first chat session.

15. The method of claim 1 , further comprising:

receiving, by a workflow engine executing on the server, the first ticket;

applying, by the work flow engine, a rule to the first information of the first ticket;

determining, based on the applying the rule, that the first ticket satisfies a condition associated with the rule; and

assigning, by the work flow engine, the first ticket to the second chat queue responsive to determining that the first ticket satisfies the condition.

16. A system for servicing information technology tickets via a computer network, comprising:

a server including a processor and memory configured to:

retrieve, from a database stored in the memory, a first ticket having a first ticket identifier, the first ticket having first information to facilitate providing information technology support or services to a first computing device;

identify, based on the first information, a first priority and a first chat queue for the first ticket;

receive an update to the first information of the first ticket;

determine, responsive to the update to the first information, a second priority and a second chat queue for the first ticket, the second priority greater than the first priority; and

assign the first ticket to the second chat queue with the second priority to initiate a first chat session associated with the first ticket and the first computing device to provide information technology support or services to the first computing device.

17. The system of claim 16 , wherein the server is further configured to:

identify a second ticket in the second chat queue with a third priority;

determine that the third priority of the second ticket is less than the second priority of the first ticket; and

initiate, responsive to the determination, the first chat session associated with the first ticket and the first computing device.

18. The system of claim 16 , wherein the server is further configured to:

identify a second ticket in the second chat queue with a third priority less than the second priority; and

establish, based on the second priority and the third priority, the second chat queue with the first chat session ahead of a second chat session associated with the second ticket.

19. The system of claim 16 , wherein the server is further configured to:

assign the first ticket to the second chat queue responsive to the second priority being greater than the first priority.

20. The system of claim 16 , wherein the server is further configured to:

receive, from the first computing device associated with the first ticket, a first indication of a first status of the first computing device; and

determine the first priority of the first ticket based on the first status.

21. The system of claim 20 , wherein the server is further configured to:

receive, from the first computing device associated with the first ticket, a second indication of a second status of the first computing device; and

determine the second priority of the first support ticket based on the second status, the second priority greater than the first priority; and

assigning, by the server, the second priority to the first ticket.

22. The system of claim 16 , wherein the server is further configured to:

receive, from the first computing device associated with the first ticket, a first indication of interaction with one or more input devices of the first computing device, the first indication associated with a timestamp;

identify a current time;

determine a time interval between the current time and the timestamp of the first indication, wherein the server has not received a subsequent indication of interaction with the one or more input devices of the first computing device during the time interval;

compare the time interval with a threshold to determine that the time interval is greater than or equal to the threshold;

set, based on the comparison, a first status of the first computing device to indicate that a user of the first computing device is away; and

assign the first priority to the first ticket based on the first status.

23. The system of claim 22 , wherein the server is further configured to:

receive, subsequent to the time interval, a second indication of interaction with the one or more input devices of the first computing devices; and

set the second status responsive to the second indication, the second status indicating that the user of the first computing device is present.

24. The system of claim 16 , wherein the server is further configured to:

determine at least one of the first priority or the second priority based on at least one of a microphone, a camera, a proximity sensor, or a position sensing system.

25. The system of claim 16 , wherein the server is further configured to:

receive, from a second computing device, an indication to initiate a remote control session to support the first computing device in accordance with the first ticket; and

initiate, responsive to the indication, the remote control session between the second computing device and the first computing device.

26. The system of claim 25 , wherein the server is further configured to:

monitor, via the remote control session, outputs of the first computing device; and

control, via the remote control session, an input device of the first computing device to support the first computing device in accordance with the first ticket.

27. The system of claim 16 , wherein the server is further configured to:

receive, from a monitoring system, activity information of the first computing device; and

update the first ticket with the activity information.

28. The system of claim 16 , wherein the server is further configured to:

initiate the first chat session associated with the first ticket and the first computing device, the first chat session initiated between the first computing device and a second computing device;

identify a second ticket associated with the first computing device, the second ticket having second information to facilitate providing information technology support or services to the first computing device; and

initiate a second chat session associated with the second ticket and the first computing device, the second chat session between the first computing device and a third computing device, the second chat session at least partially overlapping with the first chat session.

29. The system of claim 16 , wherein the server is further configured to:

initiate the first chat session associated with the first ticket and the first computing device, the first chat session initiated between the first computing device and a second computing device; and

add a third computing device to the first chat session, the first chat session configured to display messages from each of the first computing device, second computing device and third computing device to participants of the first chat session.

30. The system of claim 16 , further comprising a workflow engine configured on the server to:

receive the first ticket;

apply a rule to the first information of the first ticket;

determine, based on the application of the rule, that the first ticket satisfies a condition associated with the rule; and

assign the first ticket to the second chat queue responsive to the determination that the first ticket satisfies the condition.

Assignments (12)
RELEASE OF SECURITY INTEREST Recorded Oct 6, 2021
From: OWL ROCK CAPITAL CORPORATION
To: CONNECTWISE, LLC; CONTINUUM MANAGED SERVICES HOLDCO, LLC
Reel/Frame 057718/0617 →
SECURITY INTEREST Recorded Oct 5, 2021
From: CONNECTWISE, LLC; DIPPELL & ASSOCIATES, INC.
To: BANK OF AMERICA, N.A.
Reel/Frame 057771/0004 →
SECURITY INTEREST Recorded Mar 5, 2019
From: CONNECTWISE, LLC
To: OWL ROCK CAPITAL CORPORATION, AS COLLATERAL AGENT
Reel/Frame 048509/0936 →
RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 037190/0351 Recorded Feb 28, 2019
From: JPMORGAN CHASE BANK, N.A.
To: CONNECTWISE, INC. (SUCCESSOR-BY-MERGER WITH CONNECTWISE.COM, INC.)
Reel/Frame 048477/0819 →
RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 037701/0825 Recorded Feb 28, 2019
From: JPMORGAN CHASE BANK, N.A.
To: CONNECTWISE, INC. (SUCCESSOR-BY-MERGER WITH CONNECTWISE.COM, INC.)
Reel/Frame 048477/0897 →
RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 037701/0764 Recorded Feb 28, 2019
From: JPMORGAN CHASE BANK, N.A.
To: CONNECTWISE, INC. (SUCCESSOR-BY-MERGER WITH CONNECTWISE.COM, INC.)
Reel/Frame 048478/0019 →
CERTIFICATE OF CONVERSION Recorded Feb 26, 2019
From: CONNECTWISE, INC.
To: CONNECTWISE, LLC
Reel/Frame 048447/0076 →
MERGER AND CHANGE OF NAME Recorded Jan 6, 2016
From: CONNECTWISE.COM, INC.; CONNECTWISE, INC.
To: CONNECTWISE, INC.
Reel/Frame 037419/0221 →
SECURITY INTEREST Recorded Dec 2, 2015
From: CONNECTWISE.COM, INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 037190/0351 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 9, 2015
From: CONNECTWISE IT, INC.
To: CONNECTWISE.COM, INC.
Reel/Frame 036765/0001 →
CHANGE OF NAME Recorded Sep 28, 2015
From: CONNECTWISE, INC.
To: CONNECTWISE IT, INC.
Reel/Frame 036699/0953 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 1, 2014
From: BELLINI, ARNOLD, III; BROTHERTON, LINDA
To: CONNECTWISE INC.
Reel/Frame 034283/0970 →
Continuity (1)
Continuation 14336705 · Jul 21, 2014