Service Tags allow your team to categorize and track Work Orders across T3. Tags are created at the company level and can be applied to new or existing tickets to improve visibility and filtering.
Common examples include:
Waiting on Parts
Parts Ordered
Service Call
Repair Complete
Needs Scheduled
Tags can be used to indicate workflow status, service type, or operational priority.
Create Company-Wide Service Tags
Service Tags can be created by users with Manager, Owner, or designated permissions.
In T3, select Company from the left menu.
Open the Account tab.
Scroll to the Service Tags section.
Select Create tag.
Enter a tag name and choose a color.
Select Save.
If a tag name already exists, a warning will display.
Tags are immediately available for use across Work Orders, Inspections, and Upcoming Service.
Add Tags to a Work Order or Inspection
Tags can be added from the table or within the ticket.
Add from the Table
Tags can be added directly from the Work Orders table.
Navigate to Service.
Locate the Work Order or Inspection.
Hover over the Description column.
Select + Add Tag.
Search for and select the tag.
The tag will display immediately in the table.
Add from the Work Order or Inspection
Open the ticket by selecting the blue ID link.
Select + Add Tag from the left panel.
Search for and select the tag.
When a tag is added, the action is recorded in the Updates section of the ticket.
Add Tags When Creating a Ticket
Tags can be added to a new service or inspection ticket.
Select + Create from the Work Orders table.
In the Tags field, search and select the desired tag.
Complete the remaining fields and select Create.
The tag will display once the Work Order or Inspection is created.
Delete Company-Wide Service Tags
Service Tags can be deleted by users with appropriate permissions.
Navigate to Company.
Open the Account tab.
Scroll to the Service Tags section.
Select one or multiple tags.
Select Delete and confirm.
Deleted tags:
Cannot be assigned to new tickets.
Will remain visible on historical Work Orders where previously applied.
Best Practices for Service Tags
Keep tags workflow-focused
Use tags to represent actionable states such as Waiting on Parts or Needs Scheduled.
Avoid duplicating priority fields
Priority and Severity already exist as structured fields. Use tags for operational tracking instead.
Standardize naming across branches
Consistent naming improves filtering and preset creation.
Review tags periodically
Remove outdated tags to maintain a clean system.