This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
support:00_overview:02_accounts [2013/06/24 16:31] seyers |
support:00_overview:02_accounts [2016/02/26 15:07] (current) seyers |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Accounts ====== | ====== Accounts ====== | ||
| + | ===== Overview ===== | ||
| + | Like Pricing Templates, the "dispatch defaults" configured for each Account drives the information populated on the new job screen, unless the dispatcher makes changes. | ||
| + | \\ | ||
| - | Like Pricing Templates, the Accounts section is one of the main repositories (“homes”) for critical information upon which the rest of DispatchDirectTM depends. The decisions made in setting up an Account will set the initial course for how new calls for the account are processed. Accounts is the “authoritative source” for the information it conatins. Unless there is a manual over-ride, the entries in Accounts will be the basis and starting point for other processes in DispatchDirectTM. | + | This makes creating new jobs faster and easier for the dispatcher by reusing common settings for each account: |
| - | Said another way, the information in Accounts is the assumed “default” that will be used in other parts of the system. For example, when a new service request is received from an Account: | + | * Pre-populating incident location or tow destination (users enter any number of addresses accessible from a drop down menu) |
| - | + | * Assigning a pricing template based on whether job is a service call or tow, or specialized pricing | |
| - | * The call entry screens will automatically populate with contact and Destination address information from the entries in Accounts | + | * Defines the information the driver will be asked to enter, or not |
| - | * To further expedite call taking, Job Entry will automatically populate dispatch parameters based on the “defaults” set for the Account | + | * Who will ultimately pay the bill when the job is completed (e.g., police departments or private impound Accounts may place the call for the tow, but the bill is the responsibility of the vehicle owner (e.g., requires a "cash" Bill to:) |
| - | * The charges for the call will be based on the rates in the Pricing Templates that are “associated” with the Account | + | \\ |
| - | * Invoicing will use the Billing Address as entered in Accounts | + | Information drawn from account defaults will affect other areas in Ranger, such as whether mileage is based on rolling or geocoded miles, how frequently driver will be shown the Enter VIN screen, or whether remarks are shown to remind a Dispatcher or Driver to gather information or complete additional steps. |
| - | + | \\ | |
| - | + | ||
| - | Information drawn from entries in Accounts can be changed in other process steps as necessary. For example, the default information in an Account may indicate that mileage pricing should be based on “rolling miles” - using odometer inputs coming from the truck over the course of the call. The dispatcher has the flexibility to modify this “default” approach, and instead choose to make pricing charges for the call based on “calculated miles” - i.e., the turn-by-turn estimates from Google Maps. The “default” information for an Account serves to streamline needed inputs for a new call; changes require manually over-riding these initial inputs - generally by the call taker or dispatcher. | + | |
| - | + | ||
| - | The three major categories of information for an Account relate to contacts/addresses, pricing (formulas, rates), and the dispatching process. The listing of all Accounts is in a window that slides out from the right side. Associated Pricing Templates are in a window that slides up from the bottom. Each of the major categories of information are described in turn after first highlighting the role of the Cash/Call-In Account in DispatchDirectTM. | + | |
| - | + | ||
| - | **Dispatch Defaults** | + | |
| - | + | ||
| - | Dispatch defaults are provided as another tool to expedite the call taking and dispatching processes. Some fields will be automatically populated (from the Cash/Call-In Account) to streamline the entry of Account information. As noted previously, any information that is automatically populated can and should be changed to get the right information entered for the particular Account. | + | |
| - | + | ||
| - | Dispatch default destination address - provides an opportunity to enter the most common Destination/Drop location for a repeat customer. For example, police calls might typically be towed to the city impound lot, or an auto dealer may have a service facility where they want incoming vehicles to be dropped. These fields are optional entries. In cases where there is a “usual” drop location, it can be entered in these fields. When a new call is received from this Account, DispatchDirectTM will automatically populate the Destination address in Job Entry with this information. | + | |
| - | + | ||
| - | Dispatch defaults - are intended to streamline call taking by pre-defining common characteristics of new calls that are received from the Account. For example, the City and State fields will fill in the corresponding fields in the Incident address. If incorrect, the call taker can easily over-ride these fields and enter the correct information. Many of these fields are populated from the entries in the Cash/Call-In Account (in effect the Company defaults). These entries can/should be modified as appropriate. If there is no common pattern for an Account, the fields can be made “blank”, and the call taker can start “from scratch” for every new call. | + | |
| - | + | ||
| - | The “Priority” field has a special role within DispatchDirectTM (see Company Setup - Priority). The “priority” assigned to an Account will be used to populate the corresponding field in Job Entry. More importantly, this field is available on the Dispatch screen. The “Priority” on the Dispatch screen can be used as input for the dispatcher in sequencing calls. The dispatch screen can also be sorted by “Priority” so that the most urgent jobs are at the top of the dispatch list. | + | |
| - | + | ||
| - | Mileage defaults - specify the appropriate approach for determining mileage charges for the Account (see Pricing Templates - Pricing Parameters - Mileage). For pricing purposes, mileage can be determined based on odometer readings from the truck (“rolling miles”), or based on turn-by-turn directions from Google Maps (“calculated miles” - automatically calculated in DispatchDirectTM for geocoded locations). The rates for the mileage charges are set in Pricing Templates. The approach for determining the miles that are to be billed - “rolling” vs. “calculated” - is set for each Account . Setting the appropriate pricing approach for an Account requires: | + | |
| - | + | ||
| - | * Specifying whether pricing will be based on “truck odometer” inputs (“rolling miles”) or the “Geocode calculation” - for both Unloaded and Loaded miles | + | |
| - | + | ||
| - | * For companies with more than one base, choosing the appropriate starting point for the “Geocode calculation” of Unloaded miles. | + | |
| - | + | ||
| - | For example, many motor clubs expect that Unloaded mileage charges will be based on the “calculated” distance from a particular base - often the main location (home base) of the company. In other cases, an Account will expect that mileage charges are based on the “closest base” to their business location. These expectations are set in selecting the “Starting base”. | + | |
| + | The three major categories of information for an Account relate to contacts/addresses, pricing (formulas, rates), and the dispatching process. The listing of all Accounts is available from a panel that slides out from the right side. Associated Pricing Templates are in a window that slides up from the bottom panel. Each of the major categories of information are described in turn after first highlighting the role of the Cash/Call-In Account in DispatchDirectTM. | ||
| + | \\ | ||
| + | {{{{:support:00_overview:accountdetail2.png|}} | ||
| + | \\ | ||