Methods and Systems for Script Operations Management

• US 20080208610A1
• Filed: 02/28/2008
• Published: 08/28/2008
• Est. Priority Date: 02/28/2007
• Status: Abandoned Application

• Current Assignee: In2m Corp.
• Original Assignee: In2m Corp.
• Inventors: Park, Tyler Kevin, Thomas, Nicholas Arthur
• Application Number:
  US12/039,481
• Publication Number:
  US 20080208610A1
• Time in Patent Office: Days
• US Class Current: 705/1
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising

Abstract

Systems and methods for detecting, reporting and repairing of damaged scripts used to obtain financial account information from financial institutions are described, along with systems and methods for improved communications to users of financial software of the status of repair efforts. The systems and methods provide for improved speed in repairing script errors. In some embodiments, the script errors may be detected and repaired before a user even notices and/or reports the script error. In addition, the systems and methods provide for automatic detection and prioritization of script errors in conjunction with enhanced response times to script errors reported by users of financial software. Benefits are provided to the user experience, as well as to the efficiency of and resources required of service providers to repair broken scripts.

Claims

1. A method for improving script operations management comprising:

providing a financial software application to a first user;

receiving a selection of a link to request repair of a damaged script from the first user through the financial software application;

automatically generating a script repair ticket corresponding to the selection of the link to request repair of the damaged script;

providing an estimated repair time to the first user of the financial software application;

repairing the damaged script; and

notifying the first user that the script has been repaired.

2. A method as recited in claim 1, further comprising:

linking accounts of additional users of the financial software that have an error associated with the damaged script to the script repair ticket;

providing the estimated repair time to any of the additional users who access the financial software application before the damaged script is repaired.

3. A method as recited in claim 2, further comprising:

receiving a request from a subset of the additional users to be notified when the script has been repaired; and

notifying the subset of the additional users that the script has been repaired.

4. A method as recited in claim 1, wherein notifying the first user that the script has been repaired comprises changing the status of one of a notification flag and a notification message in the financial software application.

5. A method as recited in claim 1, wherein notifying the first user that the script has been repaired comprises an action selected from the group of:

sending an e-mail to the first user;

sending a text message to the first user;

contacting the first user by telephone; and

providing an alert to the first user within the financial software application.

6. A method as recited in claim 1, wherein repairing the damaged script further comprises:

determining that additional action by the first user is required to restore full functionality to the damaged script;

reporting to the first user that the additional action is required; and

completing repair of the damaged script for the first user after the first user performs the additional action.

7. A method as recited in claim 6, wherein repairing the damaged script further comprises:

determining that additional action by the additional users is required to restore full functionality to the damaged script;

reporting to the additional users that the additional action is required; and

completing repair of the damaged script for the additional users after the additional users perform the additional action.

8. A method as recited in claim 1, further comprising providing the first user with an updated estimated repair time through the financial software application.

9. A method as recited in claim 1, further comprising updating a status identifier of the financial software application and for an account of the first user associated with the damaged script to a status indicating that repairs are in progress when the script repair ticket is generated.

10. A method as recited in claim 1, further comprising merging the script repair ticket with additional script repair tickets received from additional users.

11. A method for improving script operations management comprising:

detecting a script failure at a financial institution web page that prevents an automatic aggregation of a first customer'"'"'s account information by a financial service provider;

automatically generating a request to repair the script failure;

determining whether aggregation of additional customers'"'"' account information is also affected by the script failure and if the script failure affects aggregation of the additional customers'"'"' account information, joining the affected additional customers'"'"' accounts to the request to repair the script failure;

prioritizing the request to repair the script failure with any other requests on a proactive script repair queue; and

repairing any scripts affected by the script failure.

12. A method as recited in claim 11, further comprising removing the request to repair the script failure from the proactive queue.

13. A method as recited in claim 11, further comprising providing the first customer with an estimate of the time to repair the script failure.

14. A method as recited in claim 13, further comprising providing the additional customers whose account information is also affected by the script failure with the estimate of the time to repair the script failure.

15. A method as recited in claim 11, further comprising notifying the first customer that the script failure has been repaired.

16. A method as recited in claim 11, wherein prioritizing the request to repair the script failure comprises prioritization of requests based on at least one of:

a number of accounts affected by the script failure;

an estimated difficulty of repair of the script failure;

a first-in-first-out prioritization scheme;

a total length of time since the script failure was detected; and

a maximum-time-to-repair commitment.

17. The method of claim 11, further comprising:

receiving a request from a second customer to repair the script failure;

generating and prioritizing a reactive request to repair the script failure on a reactive queue; and

associating the automatically-generated request to repair the script failure on the reactive queue with the reactive request to repair the script failure on the reactive queue.

18. A computer-readable medium storing a computer program product for implementing a method for improving script operations management, the computer program product comprising computer program code means for:

providing a financial software application to a first user through a global computer network;

receiving a selection of a link to request repair of a damaged script from the first user through the financial software application and the global computer network;

automatically generating a script repair ticket corresponding to the selection of the link to request repair of the damaged script;

providing an estimated repair time to the first user of the financial software application;

repairing the damaged script; and

notifying the first user that the script has been repaired.

19. A computer-readable medium as recited in claim 18, wherein the computer program product further comprises computer program code means for:

linking accounts of additional users of the financial software that have an error associated with the damaged script to the script repair ticket;

providing the estimated repair time to any of the additional users who access the financial software application before the damaged script is repaired.

20. A computer-readable medium as recited in claim 19, wherein the computer program product further comprises computer program code means for:

receiving a request from a subset of the additional users to be notified when the script has been repaired; and

notifying the subset of the additional users that the script has been repaired.