| Table of Contents | ||
|---|---|---|
|
Required driver input allows an X Dispatch input allows an Operations App user to add specific driver prompts to an order or route stop.
Example
A driver is picking up/delivering to a lab that needs to pick up from the lockbox and check the refrigerator. These prompts can be added to the driver's Nextstop Driver App workflow from X Dispatchthe Operations App.
Where Can I Add Required Driver Inputs?
Order entry form in the 'Drivers' tab. The required input(s) are for the driver of this order only.
Div 
Customer record in the 'Required Input' tab. This is useful if your customer requires an input at each pickup / delivery or arrived / competed.
Div 
Order types form in the 'Required Input' tab. This is useful if all the orders using this order type require an input at each pickup or delivery.
Div 
Contract stops form in the 'Required Input' tabs. This is useful if all the route stops posted from this contract stop require an input at arrived or completed.
div
| Note |
|---|
Do not add duplicate required inputs. If you have required inputs on the customer record and the order type, all of them will display in the order they were entered. |
| Excerpt |
|---|
Add Workflow PromptThis form displays when adding a new required input.
For X Dispatch 21.1 or newer, you can select to display the prompt for specific route stops when adding the required driver input from a customer record.
|
How Does Required Driver Input Work in
...
the Driver App?
Before a driver can complete a stop, a screen asking for the required input(s) will display. If the driver tries to complete the stop before filling out all the required information, the required fields will be underlined red. The stop can be completed once the driver inputs the required information.
Related articles
| Filter by label (Content by label) | ||||||
|---|---|---|---|---|---|---|
|
...
| Page Properties | ||
|---|---|---|
| ||
|
...