Ticket Integration

Establishes geofenceGeographic areas marked on a map that act as destinations for driver navigation or triggers for automated behaviors in TrackIt. boundaries around all open hotspots. Based on the settings associated with a hotspot type, statusThe specific activity or task a driver is currently engaged in, typically as part of a process called a "status loop." behaviors may be triggered when equipmentAll machines used as a means of production on a construction site or at a batch plant. interacts with (i.e., enters or exits) a hotspot.

	Selected	When entering and exiting hotspots, the driver's status automatically changes in accordance with the hotspot's settings.
	Cleared/ Unchecked/ Deselected	The driver won't automatically change statuses incorrectly when entering and exiting hotspots that aren't associated with their ticket.

Associates a hotspot with a driver's ticket when their equipment interacts with the hotspot's geofence.

Voids a driver's active ticket if it has no Destination Address and replaces it with the next orderIndividual requests for specific materials that are associated with a job. Some jobs may consist of multiple orders of varying products. on the driver's tablet.

	True	Tickets without destinationThe location of a job or pour site that a driver must navigate to. addresses are voided and a new active ticket (if any exist) in the driver's queue replaces it. The ticket won't void automatically if the driver is in the At Job status or later in the status loop.
	False	Tickets without destination addresses remain active. However, no hotspot may be created if Auto-create Hotspots is enabled.

Each time TrackIt receives a ticket, the destination location may be used to create a hotspot centered on the address. Use of this option is ideal for hotspot types using enter and exit status behaviors to streamline driver status changes.

Controls ticket statuses when received in TrackIt for as part of the dispatch process.

	True	New tickets are set to Active status.
	False	New tickets are set to Inactive status.

When a ticket doesn't automatically update statuses, then you must either manually update each ticket status as needed or create a status actionEvents that trigger upon entering or exiting a specific status. that activates a ticket with a specific status change

Forces active tickets to automatically close after a threshold period of time elapses. This setting facilitates the cleanup of tickets that may have been completed, but weren't closed by the driver.

To not enforce a time limit, leave this field blank.

Restricts how old a ticket may be without being set to Active status in minutes. If a ticket exceeds this threshold time without being activated, then the ticket won't automatically change to Active status and will be skipped in the driver's ticket queue.

Specifies the number of days that a hotspot can be unused (unassociated with any ticket) and still display on the Equipment Map. When this time elapses, the hotspot is removed.

When a hotspot is received from COMMANDseries, TrackIt uses this radius multiplier to create hotspots of the desired size on the Equipment Map. This takes the current radius size for a hotspot type and multiplies it by the number specified here.

Set the value to 1 or leave the field blank to retain the standard hotspot radius size sent by COMMANDseries.

Associates a unique ID with tickets created in TrackIt for identifying attributes needed for destination addresses.

IntegrationAllows different software solutions to exchange information without the need for manually exporting or importing data. setting required for Command Mobile Ticket features.

Integration setting required for Command Mobile Ticket features.

Integration setting required for Command Mobile Ticket features.

Integration setting required for Command Mobile Ticket features.

Integration setting required for Command Mobile Ticket features.

Integration setting required for Command Mobile Ticket features.

Integration setting required for Command Mobile Ticket features.

Integration setting required for Command Mobile Ticket features.

Integration setting required for Command Mobile Ticket features.

Associates equipment, plantA production plant or material storage location., or employeeUser accounts for drivers, dispatchers, and other staff to perform varying functions in TrackIt. IDs with the interface number used to integrate TrackIt with a third-party solution.

Specifies the time interval in seconds between TrackIt queries for data changes from integrated systems.

When an active ticket is received in TrackIt and assigned to a driver, the driver is sent an email containing ticket information. The details for a ticket are specified in the Ticket Message setting below.

Includes the Alt Employee Number field when sending employee data to and from the TrackIt Android app. This is useful when the values are needed for integrated systems, whereas the primary employee number is used for the company's own records.

Integration setting required for Command Mobile Ticket features on the Mobile Ticket Android app.

Integration setting required for Command Mobile Ticket features on the Mobile Ticket Android app.

Integration setting required for Command Mobile Ticket features on the Mobile Ticket Android app.

Defines the format of dates associated with ticket messagesText messages exchanged between drivers and dispatchers using TrackIt. in the TrackIt Android app.

The following options allow you to pick between standard and military times:

• 12/01 04:30 am
• 12/01 16:30
• 04:30 pm
• 16:30

Specifies the ticket information to display in a ticket messageText messages exchanged between drivers and dispatchers using TrackIt.. The available elements are found in the drop-down menu and added to the message body by clicking ADD TICKET ELEMENT. Additional static text may be added as needed in the field below to label ticket information elements.