Follow

ID425 D&A Form for Deliveries through Dispatching Overview & Sample

This form can be used for equipment installs that are dispatched in e-automate. Using e-automate’s dispatch console to stage and schedule your equipment deliveries/pickups is a best practice. This way you can obtain signatures upon install and submit the form to your leasing company for funding.

Before you start this automated process, it is imperative you follow the guidelines below so these delivery calls don’t damage the integrity of your field technician stats and service reports.  The best way to keep these calls from affecting stats is to exclude these delivery call types (and, where possible, CallType Category) by setting all your delivery call types to start with a fixed common character set (as shown below).

**Please note your CallType Code Description MUST contain the word 'delivery' and 'pickup' in order for this alert to capture them.

For example,  start all the call types with ‘ZZ’ so in your dispatch console you can easily include/exclude all delivery calls by using the call type filter does not / contains ‘ZZ’.  The next control set is use the next two characters to differentiate between a delivery call (‘DV’ for example) and a pickup call (‘PU’).  So following that type of logic as an example, you would have the following call types setup as below (and all are assigned the CallType category of ‘IR’):

ScreenShot.png

The call type prints at the top right-hand side of the delivery ticket in bold letters so the truck drivers understand the transaction type they are dealing with (delivery and/or pickup).  The Signature block/text for deliveries can be different than for pickups, but the logic only works if your CallType codes have either the word ‘Delivery’ or ‘Pickup’ in the call type description so the report can recognize the different type of call and print the appropriate signature verbiage block.

VariableW is where you would specify the Configuration (custom property) name assigned to the equipment records if you want to have the report print ALL those attributes. VariableX is where you can specify a list of only the attribute names you want the report to pull form the equipment record. If you chose to print all attributes (custom property values) in VariableW beware that the report could expand to two pages per call!!

The next step is to create are to create a technician record for your delivery trucks.  You could have the  actual drivers as the technician, or you could just create a technician called ‘Truck1’, or ‘Truck2’, etc. The crucial part here is the best practice to, once again, start each of these techs' "employee number" with a common couple of characters. Below are some examples of "trucks" we setup :

ScreenShot.png

You also have the option to have the delivery ticket report include all/specific custom property attributes that you might have assigned to the equipment record.  In the Event/Alert ID subscription (this process is ID425, VariableW) you may specify the Custom Property configuration name you assigned to the equipment custom properties tab.  VariableX is where you optionally put in the specific attribute names you might want to print from the equipment custom properties as well.  So, VariableW with a value and VariableX blank will print ALL the attributes assigned to the equipment that have a value.  If you specify any attributes in VariableX, then ONLY those attributes will print on the delivery ticket. 

**Note – The more attributes you use on the equipment custom properties and depending on your selections in VariableW & VariableX in the subscription, then you run the risk of the delivery ticket printing onto multiple pages!

Next, you could use call service priority codes to establish the order the truck will be delivering the equipment each day.  If you're confident in the exact start time and the length of time for each delivery call, then you could use the Dispatch Console ‘Day View’ to reorder / assign start times for each truck's calls. But we found that to create more confusion with our reps (you said you’d be there at 9:30 and it’s 11:30!!).  So we just designate the ‘Stop’ number using a service priority code as below.  These become the ‘order’ that the truck will make its stops for the day.

ZUA – Stop Unassigned

Z1 – First Stop

Z2 – Second Stop etc etc etc

Jobs

As of version 8.1, there is still no way to effectively associate a sales order to a specific service call for delivery tracking. So we use the Inventory Jobs feature of e-automate to help create a common thread between different modules.  In the case of equipment deliveries and pickups, we need to communicate to the sales rep at different stages in the process of the delivery call, so our alerts/paperwork rely on you creating all your sales reps and sales admin people as ‘Contacts’ in e-automate for your company record. Then create a ‘Job’ in e-automate for each sales rep in which you associate the rep’s contact record to the job, and also their appropriate sales admin team member (if you have distinct admin person assigned to each rep). After you have created the rep and admin person as a contact for your company e-automate customer record. from e-automate main menu bar select "Tools," then "Jobs," then click the "New" button.

Setup the job as below. Remember to add the rep/admin contact records to the Contacts tab.

 ScreenShot.png

ScreenShot.png

 

Custom Report:

1.png

Available Advanced Filter Settings under Service Call filter:

2.png

 

Sample Form:

We can format and edit verbiage for you:

(right click on images to see larger)

1.png

In order for accessories to populate on D&A, accessories must be linked and consumed under HOST.

Comments section below pulling through via Custom Property per VariableX on your ID425 subscription.

 

2.png

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk