About Tickets in Texada Web and Texada Mobile

Describes the purpose of and main scenarios for the use of tickets in Texada Web and Texada Mobile.

Type

Conceptual

Audience

All

Products

Texada Web and Texada Mobile, SRM

In this Article

Body

Tickets are documents in Texada Web and Texada Mobile that indicate that an asset is being moved from one location to another. They are typically a “child” document of a contract that communicates to a driver what needs to move where.

For example, this movement could be at the beginning of a rental transaction, where your customer rents a piece of equipment they cannot move such as a boom lift. Instead, the customer pays you to transport the lift from your yard to their worksite. Your Texada Web counter or SRM (Systematic Rental Management) application user creates a delivery ticket and associates it with the rental contract for the boom. 

The Texada Web counter worker or logistics manager then sees the ticket in the Texada Web and assigns it to a driver. The driver loads the boom into the delivery vehicle, drives it to the site, unloads it, and takes pictures of the asset using Texada Mobile. The driver then has the customer sign for the delivery using the mobile application and marks the ticket as complete. The SRM user closes the ticket and your customer is billed for the delivery. 

Ticket Types

There are three types of tickets used in Texada Web and Texada Mobile. Use the following table to understand more about each type:

Ticket Type

Created/Closed In

Description

Pickup

FLWATicketsAbout2-1

  • SRM
  • Texada Web

An item is moved from your customer’s site to your yard

Delivery

FLWATicketsAbout1-May-04-2021-06-17-49-33-PM

  • SRM
  • Texada Web

An item is moved from your yard to your customer’s site

Task

FLWATicketsAbout3-1

  • Texada Web

An item is moved between one of your customer’s sites to another of their sites or involves a minor task, such as picking up a small item left behind at a site.

Note: Task tickets are not billable and therefore do not appear in SRM.

 

Ticket Numbers

Each ticket has a unique ticket number. Tickets are numbered using the following numbering scheme:

111-111

The first half of the number contains the contract number, while the actual ticket number related to that contract is in the second half.  

For example, a ticket number of 626-001 refers to the first ticket (001) on contract 626. 

Notes:

  • You can associate multiple tickets with a single contract in SRM. 
  • For example, if you have multiple items in a contract that require separate transports or different items that are sent out at different times requiring different delivery times, each item would have its own delivery ticket for that contract. 

Ticket Workflow

Similar to work orders, tickets use SRM and Texada Web and Texada Mobile to draw out the Texada platform’s full potential. The use of all the applications creates an unbroken workflow from the time the ticket is created until it is closed and the customer is billed. The following diagram outlines the workflow:

WATicketsAbout4

  1. Delivery and pickup tickets are created in SRM or Texada Web by the administrator, counter person, or logistics manager. 
  2. In Texada Web, the logistics manager sees the ticket and assigns it to a driver.
  3. If this is a delivery ticket, the driver loads the equipment onto the delivery truck.  
  4. The driver travels to the required location and loads the item if this is a pickup ticket, or unloads the item if it is a delivery ticket. They use Texada Mobile to document their process. 
  5. The driver uses Texada Mobile to obtain a signature from the customer.
  6. If this is a delivery ticket, the driver marks the ticket as complete. 
  7. If this is a pickup ticket, then the driver returns to the yard with the equipment and unloads it.  
  8. If this is a pickup ticket, the driver marks the ticket as completed.
  9. In SRM or Texada Web, the application logistics manager or counter person closes the ticket, resulting in the customer being billed for the ticket if necessary. 

 

Note: Task tickets are the exception to this workflow as they are closed in Texada Web, not SRM and are not billable. 

Ticket workflows in Texada Mobile

The ticket workflow is composed of seven distinct phases, each with a specific status indicator.  See: “About Ticket Statuses in Texada” for more information about each status. 

The workflow is designed to ensure that drivers follow the same sequence of steps for each delivery or pickup they carry out, and that the process is thoroughly documented at all points along the way. 

Texada Mobile is closely involved with five out of the seven phases, as indicated below:

Assigned

When a ticket is assigned to a driver, they can log into Texada Mobile to view the details of the ticket.  In addition, they can add a comment, or flag the ticket for review if there is incorrect or missing information that would prevent the ticket from being carried out, such as an out-of-date address. 

FLMATicketsAbout1

Loading

The driver taps the Load Assets button in the mobile application to begin the Loading phase and move the ticket into the Loading status.  As before, the driver can add a comment or flag the ticket for review. Otherwise, they load the individual assets in the application, select the loading status, take photos to establish the pickup/pre-delivery status of the asset.  The driver then taps complete to complete the loading and then taps load complete. This moves the ticket into In Progress status. 

FLMATicketsAbout2

Pickup tickets only

The driver hands their mobile device to the customer if they are available. If the customer is available, they agree to the terms and conditions and then digitally sign for the pickup.  If the customer is unavailable, the driver agrees to the terms and conditions and taps Continue without signature.  

In Progress

While the asset is in transit, the ticket is in the In Progress phase.  At any time during this phase, the driver can add comments or flag the ticket for review. 

FLMATicketsAbout3

Unloading

The driver arrives at the delivery or pickup site and taps the Unload Assets button to begin the Unloading phase and move the ticket into the Unloading status.  As with the Loading phase, the driver can add comments, or flag the ticket. When the driver is ready to proceed, they tap the individual assets to unload them and select the unloading status.  The driver then has the ability to take post-delivery photos of the asset to establish the delivery condition. The driver taps Ticket Complete.  

FLMATicketsAbout4

Delivery tickets only

The driver hands their mobile device to the customer if they are available. If the customer is available, they agree to the terms and conditions and then digitally sign for the delivery.  If the customer is unavailable, the driver agrees to the terms and conditions and taps Continue without signature.  

Completed

The driver taps Complete to move the ticket into the Completed Status, and the workflow in Texada Mobile concludes.  

FLMATicketsAbout5

Ticket Priority Levels

You can indicate the priority level of a ticket and view it in both Texada Web and Texada Mobile. The priority level of a ticket serves as a visual cue as to the relative importance of a ticket in Texada but does not have any further effect in the application than that.  

Use the following table to understand each priority level and how it appears in each application:

Status

Description

Texada Web

Texada Mobile

Critical

The highest priority. It is vitally important that this ticket be completed quickly

Moderate

It is important that this ticket be completed relatively quickly

Low

This ticket can be completed as per usual

No indicator

Flagged tickets

At most points along the mobile workflow, you have the ability to flag a ticket for review.  You can do this when something unexpected has arisen while carrying out the tickets. For example, if a piece of equipment turned out to be critically damaged when you picked it up, or the customer was uncooperative and delayed your delivery, you can flag the ticket for review.  When a ticket is flagged for review, a flag icon appears next to the ticket in Texada Web, indicating to the counter, or logistics manager that they must have a close look at the ticket. 

It is important to note that flagged tickets cannot be moved to the closed status in Texada Web, and must be manually closed in your company’s SRM (Systematic Rental Management) application by an administrator.

Related Articles

  • About Texada Web and Texada Mobile
  • About Ticket Statuses in Texada Web and Texada Mobile
  • Create a Task Ticket in Texada Web and Texada Mobile
  • Search for a Ticket in Texada Web and Texada Mobile
  • Use the Map to Search for Work Orders, Tickets, and Drivers in Texada Web and Texada Mobile
  • Edit the Details of a Ticket in Texada Web and Texada Mobile
  • Assign a Ticket to a Driver in Texada Web and Texada Mobile
  • Schedule a Ticket in Texada Web and Texada Mobile
  • Close or Cancel a Task Ticket in Texada Web and Texada Mobile
  • Close or Cancel a Pickup or Delivery Ticket in Texada Web and Texada Mobile