# Patent

## Title
Tow claims system for secondary tow and salvage management

## Abstract

A method and system for unified secondary management of tow claims and salvage tow data, and specifically for simplifying the workflow of attending insurers, towers, and a manager (operator of an application service provider). The system is implemented in software form and includes an Insurance Company Module for allowing Clients to initiate tow dispatch orders into the system, a Tow Company Module for allowing towing vendors to view, execute and track tow dispatches assigned to them through the dispatch system, and a Management Module for allowing a third party Manager to manage the system, and to dispatch tow orders, track orders, approve completed orders for payment, and provide Client and Vendor account management, reports and performance tracking. Data extracted from all three modules is stored in a relational database and can readily be accessed by any of the three participants in real time, and may be edited and/or analyzed for reporting.

## Background
CROSS-REFERENCE TO RELATED APPLICATION(S)
The present application derives priority from U.S. Provisional Patent Application No. 60/649,511, filed Feb. 4, 2005.


BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention relates to systems and methods for managing towing and salvage claims and, more specifically, to a unified web-implemented tow claims system specifically adapted for secondary tow and salvage management.
2. Description of the Background
There are a number of existing software solutions for the towing and vehicle salvage industry. For example, ProTow 7.0 is a shrink-wrap software package for towing companies that manages dispatching, tow truck monitoring, ticket status, vehicle release status, etc. However, this and like systems require a tower to purchase computer hardware with sufficient storage capacity for all the necessary records.
There are also a few internet-based towing packages offered by application service providers (“ASPs”). Dispatch Anywhere! by Beacon Software also offers a tow management solution to towing companies for dispatching, tow truck monitoring, ticket status, etc. This program is made available to subscriber towing companies by web portal.
There are even a few known solutions for third party management of towing services. These are necessary when a third party provider or referral service takes tow claims and distributes them to independent towing companies. AAA® is perhaps the best-known third party provider, and Service Stations Computer Systems, Inc. and other software vendors offer subscriber AAA clubs a Digital Dispatch web-based product that manages call taking, dispatching, two-way text messaging, storage lot inventory, driver scheduling and a bookkeeping interface that produces driver/mechanic commissions, inventory control, repair orders, customer follow-up, A/R, A/P and Profit & Loss, all via the Internet. All of the data is housed on Digital Dispatch's servers, and the AAA agents need only a personal computer meeting minimal technical requirements.
Similarly, U.S. Patent Application 20020065703 by Garg published May 30, 2002 discloses an ASP-based software method for managing tow tracking and dispatch. This system allows a tower with a computer connection to use the computer connection to access a database that is maintained by an ASP. The system is also capable of integrating with other dispatch and tracking systems if, for example, an insurance company desires to inspect a vehicle it had towed for hidden damage or track storage costs. While it is not clear how the system integrates, it presumably allows export of database information into the insurance company's own system. This presumes that an insurer has a tow management system A Primary or Initial tow includes services provided as the result of an initial call, often from Police after accidents, incidents, disabled vehicles, and impound requests, all for a particular vehicle. A “Secondary tow” means towing services from an operator's storage facility or place of business, after a primary tow, to another location designated by the owner/agent of a vehicle that was initially towed as a result of call from the Police. A “Salvage tow” means towing services to move a total loss vehicle.
Today, insurance companies spend approximately$1.2 billion per year in towing-related expenses during the claims process, and these costs are higher than necessary. Secondary and salvage towing costs (those absorbed by an insurer) historically have been left unmanaged by insurance companies. This is due to the fact that secondary tows are typically arranged/ordered through various towing companies without negotiated or preferred pricing, nor service management. Accountability for these costs scarcely exists since there are no formal record keeping/tracking systems on the insurer side. The Garg patent does not disclose any management functions for the insurer, and hence fails to provide an integrated system designed to coordinate the efforts of the third party software application service provider (ASP), tow operator and insurer, allowing all three parties to manage their own towing needs and costs.
It would be greatly advantageous to provide a web-based software solution that gives a single order point for secondary and salvage tows for the insurance industry to: 1) enable insurance company “Clients” (and their agents) to manage secondary tow costs through pre-negotiated pricing, geographic based dispatching, and accountability of tow vendors; 2) provide tow company “Vendors” (actual tow truck companies) to view, execute and track tow dispatches which have been assigned to them through the tow claims dispatch system; and 3) provide a third party ASP or “Manager” with management capability to implement and manage the unified tow claims system via a web portal, inclusive of dispatching tow orders, tracking orders, approving completed orders for payment, and generating account management, reports, performance tracking and other reports. A unified ASP-implemented three-party-participant system would simplify the workflow of attending insurance agents, tow operators, and other providers.
SUMMARY OF THE INVENTION
It is therefore an object of the present invention to provide a unified tow management system for entry and management of tow claims, and specifically for simplifying and coordinating the workflow of tow company “Vendors”, insurance company “Clients” and a third party ASP “Manager”.
It is another object to provide a tow claims system specifically adapted for secondary and salvage tow management by the insurance industry, e.g., to enable the insurance company “Clients” (and their agents) to manage secondary tow costs through pre-negotiated pricing, geographic based dispatching, and accountability of tow vendors, and to provide them with real time data entry, claims initiation and deployment, and cost tracking and management reports through a web based interface.
It is still another object to provide a unified tow management system as described above that allows tow company “Vendors” (actual tow truck companies) to view, execute and track tow dispatches which have been assigned to them through the tow claims dispatch system.
It is yet another object to provide a unified tow management system as described above that allows a third party application service provider or “Manager” to implement and manage the tow claims system via a web portal, thereby dispatching tow orders, tracking orders, approving completed orders for payment, and providing Client and Vendor account management, reports, and performance tracking.
In accordance with the foregoing objects, the present invention is a unified tow claims management system specifically adapted for secondary tow management by the insurance industry for entry and management of tow claims data, and specifically for simplifying the workflow of the three participating user groups: insurance company “Clients”; tow company “Vendors”, and a third party application service provider or “Manager”. The present system accomplishes the foregoing with a web-implemented software solution comprising three modules: 1) An Insurance Company Module for allowing Clients to initiate tow dispatch orders into the system; 2) a Tow Company Module for allowing “Vendors” to view, execute and track tow dispatches which have been assigned to them through the tow claims dispatch system; and 3) a Management Module for allowing a “Manager” to implement and manage the tow claims system, and to dispatch tow orders, track orders, approve completed orders for payment, and provide Client and Vendor account management, reports and performance tracking.
The three modules are constructed atop a foundation comprising a specific relational database design, each module including a simple user interface that allow direct data entry and forms generation based on the database contents. The database stores the data extracted from the Management Module, Vendor Module, and Client Modules, inclusive of dispatch order information, tow authorization information, tow charges, vehicle information, vehicle location, and tow-to location. All this information can readily be accessed by any of the three participants in real time, and edited or analyzed for reporting.



BRIEF DESCRIPTION OF THE DRAWINGS
Other objects, features, and advantages of the present invention will become more apparent from the following detailed description of the preferred embodiment and certain modifications thereof when taken together with the accompanying drawings in which:
FIG. 1 is a block diagram illustrating the communications and workflow among the three participants.
FIG. 2 is a more detailed diagram illustrating the internal work flow method of the present system.
FIG. 3 is a block diagram illustrating the Management Module that allows the Manager 30 to implement and manage the tow claims method via a web portal.
FIG. 4 is a screen print of the Management module consolidated screen listing for tracking tow orders.
FIG. 5 is a block diagram illustrating the Client Module that allows the Clients 10 to implement and manage the tow claims method via a web portal.
FIG. 6 is a screen print of the Dispatch Order entry screen for allowing Clients 10 to enter and/or edit Dispatch Orders.
FIG. 7 is a screen print of the Closed Tow Request review screen for allowing Clients 10 to review closed Dispatch Orders.
FIG. 8 is a screen print of a closed tow detail screen.
FIG. 9 is a screen print of the Track Status Screen for allowing Clients 10 to review all open and closed Dispatch Orders.
FIG. 10 is a screen print of the Invoice Detail Screen for allowing Clients 10 to review any given Invoice listed in FIG. 9.
FIG. 11 is a screen print of the Claims Manager Report Order Screen.
FIG. 12 is an exemplary Manager-level Client 10 Report generated from the screen of FIG. 11, sorted by date interval.
FIG. 13 is an exemplary Manager-level Client 10 Report generated from the screen of FIG. 11, sorted by Handler ID and filtered by date interval.
FIG. 14 is a screen print of the Dispatch Order Screen.
FIG. 15 is a screen print of a Dispatch Order detail screen.
FIGS. 16 (A-N) is collectively is a table printout of all database tables listing all fields within each table of the present database.



DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
The present invention is a tow claims system specifically adapted for secondary tow and salvage management by the insurance industry, e.g., to enable the insurance companies (and their agents) to manage secondary towing and salvage costs through pre-negotiated pricing, geographic based dispatching, and accountability of tow vendors. Additionally, the tow claims system provides real time data entry, claims initiation and deployment, and cost tracking and management reports through its web based interfaces. This simplifies the workflow of attending insurance agents, tow operators, and other providers.
FIG. 1 is a block diagram illustrating the communications and workflow among the three primary participants. The participants include one or more subscribing insurance companies “Clients” 10, one or more subscribing towing companies “Vendors” 20, and a third party application service provider or “Manager” 30. All electronic communications are bi-directional, implemented via one or more back-end web-enabled servers maintained at the ASP Manager 30 site and communicating over the Internet 30. The back-end ASP Manager 30 server(s) may run on a web-enabled Microsoft platform, such as Windows 2000 Advanced Server edition and MS SQL Server 2000. Data extracted from the three modules (to be described) populates an SQL database with the information. The Vendors 20 and Clients 10 can use any remote computer equipped with a conventional web browser. In general operation, all of the Vendors 20, Clients 10, and Manager 30 may log on to the Internet and access their dedicated customized web pages located on the ASP web server, using their respective web browsers.
FIG. 2 is a more detailed diagram illustrating the internal work flow process of the present system.
Initially, at step 45, a tow assignment is forwarded by a customer (“vehicle owner”). Tow assignments may be forwarded by computer email, fax, or telephone, and are most typically called in.
At step 50, the tow assignment is received by Client 10 who is then responsible for getting the customer's vehicle towed. Client 10 enters the assignment into the present system using their respective web browser.
In accordance with the present invention, entry of the assignment triggers a 48 Hour clock at step 60 within which “owner consent” must be obtained. Typically, the vehicle will be impounded or at a savage yard, and cannot be moved without obtaining the owner's consent along with payment for the primary tow, storage fees, and any miscellaneous charges that must be paid to get the vehicle released from the impound lot. In accordance with the present method, the Client 10 determines the amount of the “Payout” (the payment due for the primary tow, storage fees, and any miscellaneous charges) by calling the operator of the impound lot where the vehicle is located. Then the Client 10 contacts the owner directly. An important customer service aspect of the present method is that the Client 10 or their agent will solicit the vehicle release/authorization directly when communicating with the claimant. Thus, the authorization for the tow is obtained directly by the Client 10 or their agent at the outset, saving considerable time and impound costs.
At step 70, the customer releases the vehicle by either: 1) Going to the Client 10 location with proof of ownership; 2) faxing a letterhead release to the Client 10 with proof of ownership; 3) by email; or 4) by 3-Way call.
At this point, the tow assignment, details of the tow authorization, and Payout amount are entered into the Client's user interface, and at step 80 a 24-hour clocks starts within which the secondary tow must be completed.
At step 90, the assignment and vehicle release authorization are communicated to the Manager 30 at the dispatch office. The Manager 30 calculates the location of the vehicle (such as, for example, using Map Quest® or other mapping service, calculates the towing charge, and identifies the closest subscribing Vendor 20 as well as miles to and from. The selected Vendor 20 is electronically notified of the assignment and proceeds to the site of the primary tow for his secondary tow.
There are two payment steps involved in a secondary tow under the present system. The first payment occurs when the tow Vendor 20 picks up the vehicle at the tow yard or impound lot. The Vendor 20 will pay the “Payout” to the impound lot operator to get the vehicle released. An important “checks and balances” aspect of the present system is that the Payout has typically been an area where costs have been unmanaged. Under the present system the Client 10 or Client agent has already determined the Payout prior to the Tow Vendor 20 picking up the vehicle, so that when the Vendor 20 arrives this information is reflected on the assignment and there is a double verification of fees for the Primary Tow.
At step 100, Manager 30 then charges payment for the Payout to the Client 10 electronically. At step 110, Manager 30 forwards Payout details to the selected Vendor 20 along with the assignment and a mileage chart, and damage report sheet.
At step 120, the Vendor 20 pays the Payout and forwards confirmation to Manager 30 that the Payout cost has been paid by the Vendor 20 with list of charges and breakdown. Differences in the amount of Payout quoted to the Client 10 and what the Tow Vendor 20 actually pays must be substantiated and explained. Once the Manager 30 is satisfied he reimburses the tow company Vendor 20 in like manner.
The Vendor then executes the tow, and at step 130 the Manager 30 monitors the job progress to completion.
At step 140, when the tow job is complete, the tower inputs a “job complete notification” into the system. At step 160, a fax and/or email notification is transmitted back to the Manager 30, who then submits electronic payment for the secondary tow to the Vendor 20 at step 150 and sends an electronic invoice to the Client 10. Finally, at step 170, the Manager compiles monthly reports for forwarding to both Clients 10 and Vendors 20.
Additionally, at step 85 the Client 10 can review closed claims at any time and view the complete order, mileage calculation (via MapquestTM), an Adobe .PDF copy of the original tow receipt, and all details related to the tow. This data is essential because it allows for auditing by the insurance company Client 10.
The foregoing workflow is implemented in software form that includes three website modules directed to serving three different user groups: 1) An Insurance Company Module for allowing Insurance Company “Clients” to initiate tow dispatch orders into the system; 2) A Tow Company Module for allowing tow company “Vendors” (actual tow truck companies) to view, execute and track tow dispatches which have been assigned to them through the tow claims dispatch system; and 3) a Management Module for allowing a third party application service provider or “Manager” to implement and manage the tow claims system via a web portal. Managers in this group dispatch tow orders, track orders, and approve completed orders for payment. Additional tasks by Managers include Client and Vendor account management, reports, and performance tracking.
The three web modules provide simple user interfaces for each of the three participants that allow direct data entry and forms generation, all three modules deriving data from an underlying web-enabled database with a specific database design. The functionality of the present tow claims system is detailed below.
FIG. 3 is a block diagram illustrating the Management Module that allows the Manager 30 to implement and manage the tow claims method via a web portal. This user group manages the system, generates dispatch orders, track orders, approve completed orders for payment, and forward Client 10 and Vendor 20 account management, reports, and performance tracking.
At step 200 the Manager 30 logs into the system using a secure ID and password. At step 210 the Manager 30 is presented with a consolidated screen listing that logs new tow orders and allows management of old (previously-entered) ones.
FIG. 4 is a screen print of the Management module consolidated screen listing for tracking tow orders. The screen listing is framed in a standard Windows® rectangle, and generally includes a header section 60, a tree-index section 70 at left, and a search section 80 at right. Header section 60 displays the Client 30 logo, login information (at right) including the login name, company and login status. Header section 60 also displays a user menu including four available commands: Dispatch Orders, Reports, Tools, Sign-Off.
By selecting Dispatch Orders from the user menu, the Manager 30 is presented with the display as shown, the tree-index section 70 at left illustrating a hierarchical tree-index of all Client-entered Dispatch Orders for that particular Manager 30, with branches (sub-indexes) for each order status inclusive of “New”, “In-Process”, and “Closed.” The User/Manager 30 can access any particular order by following this index down to it. The search section 80 is a simple SQL search interface for allowing access to desired Dispatch Orders by typing in search strings. Searches may be specified by “Type”, and a drop down list of search types is provided such as by claim number. After selecting the search type, boolean text search commands are typed into the “For” box. The user then presses either the Claims Grid or Database buttons to execute the search on either the field names or on the entire database contents (field contents). All matching results are listed directly below.
By accessing an order through either tree-index section 70 or search section 80, the User/Manager 30 can view more detailed information in that Dispatch Order.
Referring back to FIG. 3, at step 230, the Manager receives a Dispatch Order from the Client 10 (who has solicited tow authorization from the vehicle owner). At this point at step 240, the Manager 30 electronically dispatches the Tow Order to the tower Vendor 20, starting the 24-hour time clock. Upon starting the clock the status of the job is changed to “In-Progress”. The Manager 30 may at step 240 view all tow orders in process, or alternatively, at step 260 may monitor tow progress of a single tow order. At step 270 when the tow job is completed the job status is changed to “Complete”, and at step 280 an Email Notification is automatically generated to the Client 10 notifying them of the Job Status Complete indication. At step 280 the Manager 30 electronically invoices client 10 and collects the funds, whereupon an electronic funds transfer is sent to the Vendor 20. All completed Orders may be viewed by the Manager 30 at step 250, or by the Client 10.
FIG. 5 is a block diagram illustrating the Client Module that allows the Clients 10 to implement and manage the tow claims method via a web portal. Currently, there are two user levels for clients—Claims Adjuster and Manager. The user level is determined at step 300 at login, depending on the user ID entered. The Claims Adjuster login can initiate dispatch orders, track tow dispatch status and view closed claims. The Manager level has all of the capabilities of the Claims Adjuster but also has the ability to view various management reports which track utilization and costs, as will be described.
At step 310, the Client 10 creates a new Order. This is done through the Client 10 module which includes a Dispatch Order entry screen just as shown in FIG. 5 for allowing Clients 10 to enter and/or edit Dispatch Orders. The Dispatch Order entry screen solicits all the foregoing categorical information (with specific fields as described). Only the Client 10 user group may initiate the tow dispatch orders into the system once they have obtained the vehicle release from the vehicle owner.
FIG. 6 is a screen print of the Dispatch Order entry screen for allowing Clients 10 to enter and/or edit Dispatch Orders. The Dispatch Order entry screen is a form that solicits the following categorical information (with specific fields also shown):
DISPATCH ORDER INFO
Claim No.?
AUTHORIZATION INFO
Handler (Tower) Alias, Date Tow was Authorized
TOW CHARGES
Tow Facility Contact
Date Storage Charges Begin
Tow Charge
Daily Storage Rate
Miscellaneous Charges
Comments
VEHICLE INFORMATION
Owners Name (Last, First)
Owner Phone
Last 6 digits of VIN
Year
Make
Model
Color
Damage Area

    
    
        Front
        Rear
        Rollover
        Left Front (Use the CTRL key to select more than one area of damage).
    
    


Damage Comments
VEHICLE LOCATION
Tow Lot/Vehicle Location
Street Address:
City
State
Zip Code:
Hours of Operation:
Phone Number:
Location of keys
TOW TO LOCATION
Facility Name
Street Address
City:
State
Zip
Phone Number
Upon completing or editing the illustrated information, the Clients 10 simply hits Submit (or Reset to clear the form).
Once completed, at step 320, the new Order is faxed and/or emailed to the Manager 30. At step 330, the Client 10 can view Orders in process by selecting “Status”>>“In Process” from the navigation menu (top). This brings up a screen that lists In Process Tow Requests including Claim No., Assigned Date/Time, Tow To Location and Current Vehicle Location. At step 340, the Client can view Completed/Processed Dispatch Orders by selecting “Status”>>“Closed” from the navigation menu (top). Additionally, the Client 10 can review closed claims at any time and view the complete order, mileage calculation (via MapquestTM), an Adobe .PDF copy of the original tow receipt, and all details related to the tow. This is essential for auditing by the insurance company Client 10. The same format of information is displayed for closed Dispatch orders.
FIG. 7 is a screen print of the Closed Tow Request review screen for allowing Clients 10 to review closed Dispatch Orders. The Closed Tow Request review screen present a listing of closed tow requests by Claim No., Authorization date/time, Tow To Location, and Vehicle Location (Impound Lot Location). The Client 10 can review the detail for any closed claim listed in FIG. 7 by clicking on the closed tow request Claim No.
FIG. 8 is a screen print of a closed tow detail screen, which displays a full complement of Dispatch Order details inclusive of Vehicle Information, Payout Fees Due, Vehicle Location and Tow Destination.
FIG. 9 is a screen print of the Track Status Screen for allowing Clients 10 to review all open and closed Dispatch Orders. The Track Status Screen presents a listing of all open and closed tow requests by Claim No., allows access to a detailed Invoice Screen, and presents assignment date/time and completion date/time, selected Vendor 20, accident or incident reports, and vehicle tow authorization sign-off. The Client 10 can review the detail for any claim listed in FIG. 9 by clicking on the tow request Claim No., and can similarly review the associated Invoice.
FIG. 10 is a screen print of the Invoice Detail Screen for allowing Clients 10 to review any given Invoice listed in FIG. 9. The Invoice Screen presents a formatted printer-ready Invoice for presentment to the Client 10.
If a Client 10 agent is logged in at the Manager level, they additionally have the ability to view various management reports which track utilization and costs.
FIG. 11 is a screen print of the Claims Manager Report Order Screen, which allows a Manager-level Client 10 to search and format reports filtered by Claim Number, Claims Agent (Handler) ID, Begin Date and End Date. The Manager-level Client 10 simply enters the requisite report filters in the text boxes shown (or drop down lists) and presses GO! to display a screen print of the report.
FIG. 12 is an exemplary Manager-level Client 10 Report generated from the screen of FIG. 11, sorted by date interval, which lists Order Date, Claims Number, Handler ID, Primary Tow Costs, Secondary Tow Costs, Total Cost, Turnaround Time, Tow Mileage, Days in Storage, and Reasons for Increased Secondary Tow Costs. This is specifically the information needed to properly manage secondary tow costs presented in one easily accessible format.
FIG. 13 is an exemplary Manager-level Client 10 Report generated from the screen of FIG. 11, filtered by Handler ID and date interval, which as above lists Order Date, Claims Number, Handler ID, Primary Tow Costs, Secondary Tow Costs, Total Cost, Turnaround Time, Tow Mileage, Days in Storage, and Reasons for Increased Secondary Tow Costs. This information is sorted by Handler ID and gives the information needed to properly manage secondary tow Handlers in one easily accessible format.
Finally, the Tow Company “Vendors” are the actual tow truck companies, and their login allows each tow company to view tow dispatches which have been assigned to them through the TowClaims.com dispatch system. Once the tow dispatch has been completed by the Vendor, they again use their login to complete the tow by entering information such as payout data and time of completion. The Vendor Module allows the Vendors 20 to implement and manage their assigned tow claims via their own web portal. The Vendor 20 can input and track tow dispatch status and view closed claims.
FIG. 14 is a screen print of the Dispatch Order screen for allowing Vendors 20 to service open Dispatch Orders. The In Process Tow screen present a listing of open tow assignments by Claim No., Assignment date/time, Tow To Location, and Vehicle Location (Impound Lot Location). The Client 10 can review the detail for any closed claim listed in FIG. 14 by clicking on the open Claim No.
FIG. 15 is a screen print of a Dispatch Order detail screen, which displays a full complement of Dispatch Order details inclusive of Vehicle Information, Payout Fees Due, Vehicle Location and Tow Destination.
Database Layout
The present database is arranged in thirteen tables each with a plurality of formatted records as shown in FIGS. 16 (A-N), which collectively is a table printout of all database tables listing all fields within each table.
It should now be apparent that the above-described system is a unified secondary tow claims management workflow system for entry, management and use of dispatch data, and specifically for simplifying the workflow of three user groups, towers, insurers and system ASP managers. The simplified data entry and forms generation features along save hours per day and avoids mistakes.
Having now fully set forth the preferred embodiments and certain modifications of the concept underlying the present invention, various other embodiments as well as certain variations and modifications thereto may obviously occur to those skilled in the art upon becoming familiar with the underlying concept. It is to be understood, therefore, that the invention may be practiced otherwise than as specifically set forth herein.

## Claims

1. A computer-implemented workflow system for simplifying the workflow of attending insurers and towing companies in administering to secondary tow and salvage claims, comprising:
at least one web-enabled server maintained by an application service provider (ASP manager) that houses software comprising an ASP manager workflow management module, a client/insurer workflow management module, and a vendor/tower workflow management module, and a relational database that stores data extracted from said ASP manager workflow management module, said client/insurer workflow management module, and said vendor/tower workflow management module,
wherein said ASP manager workflow management module comprises a graphical user interface configured to
enter, manipulate, and output, by the ASP manager, information for tow and salvage dispatch orders;
electronically transmit tow assignments to proximate subscribing vendors;
track tow and salvage dispatch orders; and
manage reports;

said client/insurer workflow management module comprises a graphical user interface configured to
enter, manipulate, and output, by a client/insurer, tow assignment information, payout amount due, and vehicle release authorization details in said relational database for tow and salvage dispatch orders;
electronically transmit tow assignments to said ASP manager;
track a first time within which vehicle release authorization must be obtained from vehicle owner by triggering a first timer once tow assignment data is entered; and
track a second time within in which a secondary tow must be completed by an assigned vendor by triggering a second timer once vehicle release authorization is obtained from a remote client/insurer computer; and

said vendor/tower workflow management module comprises a graphical user interface configured to
enter, manipulate, and output, by a vendor/tower, information in said relational database; and
electronically transmit job completion notification to said ASP manager from a remote vendor/tower computer.

2. The computer-implemented workflow system according to claim 1, wherein said ASP manager workflow management module includes a display of consolidated dispatch orders comprising a tree-index section illustrating a hierarchical tree-index of all dispatch orders by each client/insurer having sub-indices of order status inclusive of “New”, “In-Process”, and “Closed”.

3. The computer-implemented workflow system according to claim 2, wherein said ASP manager workflow management module includes a Structured Query Language (SQL) search interface for allowing access to desired dispatch orders by typing in a text search string, whereby an ASP manager can access information for a dispatch order either via said tree-index section or search section to view more detailed information on that dispatch order.

4. The computer-implemented workflow system according to claim 1, wherein said client/insurer workflow management module comprises two permission levels including claims adjuster and ASP manager, determined at a login, said ASP manager level having all capabilities of said claims adjuster plus an ability to view management reports that track utilization and costs.

5. The computer-implemented workflow system according to claim 1, wherein said client/insurer workflow management module comprises a dispatch order entry screen that allows said client/insurers to initiate dispatch orders, including claim number assignment and entry of vehicle owner authorization information, primary tow charges, vehicle information, vehicle location, and tow-to location.

6. A method for managing secondary tow and salvage claims amongst participating clients (insurers), vendors (towers) and a third party manager, comprising the steps of:
providing each participating client, vendor and manager access to a computerized workflow management system comprising at least one web-enabled server that houses software and a relational database, and at least one remote computer for said client, said vendor, and said manager, said software provides a dedicated graphical user interface for each participant to use from the participants' remote computers;
receiving a tow assignment by said client, entering assignment data into said client user interface from said at least one client remote computer of said workflow management system, and storing said assignment data in said relational database;
triggering, by said workflow management system, a first timer once assignment data is entered for tracking a first time within which vehicle release authorization for said tow assignment must be obtained;
said client determining a payout amount due to the impound lot operator for any primary tow, storage fees, and other charges and entering said payout amount into said client user interface from said at least one client remote computer of said workflow management system for associated storage in said relational database in relation to the assignment data;
said client contacting the vehicle owner directly and obtaining a vehicle release authorization and proof of ownership of the vehicle;
stopping said first timer when vehicle release authorization is obtained;
said client entering details of the vehicle release authorization into said client user interface from said at least one client remote computer of said workflow management system for storage in said relational database;
triggering, by said workflow management system, a second timer once the vehicle release authorization is obtained for tracking a second time within which a secondary tow must be completed by the assigned vendor;
electronically transmitting, by said workflow management system, said tow assignment, vehicle release authorization and proof of ownership to said manager;
facilitating a secondary tow by the substeps of,
mapping, by said manager, a location of the vehicle,
identifying, by said manager, a proximate subscribing tow vendor,
calculating, by said manager, secondary tow or salvage charges;
obtaining, by said manager, electronic payment for the payout amount from the client;
electronically transmitting, by said workflow management system, the tow assignment to the identified vendor;
electronically transmitting, by said manager, the payout amount to said identified vendor;

executing the secondary tow by the following substeps,
proceeding, by said vendor, to the vehicle location,
paying, by said vendor, the payout amount to said impound lot operator to have the vehicle released,
transmitting, by said vendor, confirmation to said manager that the payout amount has been paid, together with an itemized list of payout charges,
towing, by said vendor, the vehicle,
stopping said second timer when the towing substep is completed,
inputting job completion data into said vendor interface from said at least one remote vendor computer of said workflow management system,
transmitting, by said workflow management system, a job completion notification to said manager;

whereby said manager submits electronic payment for the secondary tow to the vendor and sends an electronic invoice for same to the client.

7. The method for managing secondary tow and salvage claims amongst participating clients, vendors and a third party manager according to claim 6, wherein said first time is 48 hours.

8. The method for managing secondary tow and salvage claims amongst participating clients, vendors and a third party manager according to claim 7, wherein said second time is 24 hours.

9. The method for managing secondary tow and salvage claims amongst participating clients, vendors and a third party manager according to claim 6, wherein in response to said step of the client contacting the vehicle owner directly, said vehicle owner may provide said release authorization and proof of ownership of the vehicle by one of: 1) physically going to the location of said client; 2) facsimile; 3) email; and 4) 3-way teleconference call between said client, vehicle owner and an impound lot operator.

10. The method for managing secondary tow and salvage claims amongst participating clients, vendors and a third party manager according to claim 6, wherein said vendor must substantiate to said manager any variation in the actual payout amount versus the payout amount transmitted to said vendor in the tow assignment.

11. The method for managing secondary tow and salvage claims amongst participating clients, vendors and a third party manager according to claim 6, further comprising the step of said manager compiling monthly reports and forwarding said reports to said clients and vendors.