Tags in ServiceTitan touch almost everything. They show up on your dispatch board, on customer profiles, on job records, in reports, and on the technician's mobile app. They're one of the most flexible tools in the platform. And that flexibility is exactly why most companies get them wrong.
The typical pattern looks like this: someone creates a few tags during onboarding, then other people add more over the next year, and eventually you've got 80 tags with inconsistent names, half of them unused, and nobody remembers what they're for. Your dispatch board is cluttered, your reporting is unreliable, and your CSRs are guessing which tags to apply. Here's how to fix that.
What Tags Actually Do in ServiceTitan
Before you start creating tags, you need to understand where they show up and who sees them. Tags appear on the dispatch board job bubbles, in the jobs tray columns, on customer and location profiles, on individual job records, and in reports. Dispatchers, CSRs, technicians, and managers all interact with them at different points.
Tags are essentially labels you attach to customers, locations, or jobs. Some get applied manually by CSRs during call booking. Some get applied automatically based on job type, form answers, or equipment age. The key thing to understand is that tags are a communication tool. They tell the next person in the workflow something important about this customer or this job. If you're creating tags that nobody acts on, you're just adding noise.
Creating and Organizing Tag Types
You create tags under Settings > Operations > Tag Types. Each tag gets a name and a code. The code is a short string of two to four characters that shows up on the dispatch board, so keep it recognizable. "MEMB" for member, "URG" for urgent, "LDRQ" for ladder required. You get the idea.
Each tag also gets an importance level: Low, Medium, or High. High importance tags get a visual callout on the dispatch board. Here's the mistake most companies make: they mark too many tags as High. If everything is important, nothing is. The default is Medium and most of your tags should stay there. Reserve High for things a dispatcher absolutely cannot miss, like a safety concern or a VIP customer. One or two High tags is fine. Ten is a problem.
The other thing to think about is naming conventions. If three different people can create tags, you'll end up with "Ladder Required," "LADDER," and "Needs Ladder" as three separate tags that mean the same thing. Pick a format and stick with it. I'd recommend short, plain names in title case. No abbreviations in the name itself since that's what the code is for.
Default Tags on Job Types
One of the most underused tag features is default tags on job types. When you edit a job type, there's a Tags field where you can assign tags that automatically get applied to every job of that type. This saves your CSRs from having to remember to add them manually.
Here's a practical example. Let's say you have a "No Cool on Roof" job type for HVAC companies where the unit is on the roof. You'd put "Ladder Required" as a default tag on that job type. Now every time a CSR books that job, the tag is already there. The dispatcher sees it on the board and knows to assign a tech with a ladder. The technician sees it on their mobile app and knows to bring one.
This is better than relying on CSRs to manually tag every job because it removes human error from the equation. Think through your job types and ask: is there anything a dispatcher or technician should always know about this type of work? If so, that's a default tag.
Conditional Tags from Forms
This is where tags get really powerful. ServiceTitan forms support conditional logic that can automatically apply tags based on how a question gets answered. You set this up inside the form builder under the conditional logic rules.
Let me give you a real example. You create a form with the question "Does this customer have a dog?" with a Yes/No answer. You add a conditional logic rule that says: if the answer is Yes, apply a "Dog" tag to the location. Now the next technician who goes to that address sees the Dog tag on their mobile app before they even knock on the door. Maybe they bring dog treats. Maybe they know to be careful opening the gate. Either way, they have information they wouldn't have had otherwise.
Here's an even more useful one for HVAC companies. You put a question on your maintenance form: "What's the customer's filter size?" Then you create matching tags for the common sizes, like "16x25x1" and "20x25x1." You set up conditional logic so that whatever size the tech enters, the matching tag gets applied to the location. Next time you send someone out there, the technician already knows what filter to bring into the house without having to go up to the unit first, come back to the truck, and then go back inside. That's a real time saver on a busy day.
The important thing to understand here is that without conditional tags, form answers just sit on the form. They don't go anywhere. The next technician doesn't see them unless they go digging through old job records. Conditional tags take that information and surface it where people actually look.
Equipment Replacement Tags
ServiceTitan has a built-in feature where equipment can automatically generate tags based on age. Here's how it works. Under your equipment types in the pricebook, you set a replacement age. For an AC condenser, maybe that's 10 years. For a water heater, maybe 8.
When a piece of equipment at a customer's location crosses that age threshold, ServiceTitan automatically applies a "Replacement Opportunity" tag to the customer, the location, and any future jobs booked at that address. You don't have to do anything. It just happens.
This is a big deal for sales. Your technician shows up for a routine maintenance call and sees that Replacement Opportunity tag on the job. They know before they even get to the house that there's aging equipment worth talking about. And it pairs well with Marketing Pro since you can build audiences based on equipment age and send targeted campaigns to customers with old systems.
For this to work, your technicians need to actually log equipment when they're out in the field. Even equipment they didn't install. If they see a water heater and there's a serial number on it, they should enter it. The serial number tells you the manufacture year, and that's good enough for tracking age. You don't need the exact install date. Just use January 1st of whatever year is in the serial number and you're close enough.
Tags on the Dispatch Board
Dispatchers are probably the biggest consumers of tag information, so it's worth setting up the dispatch board to show tags properly. There are two places tags appear: on the job bubbles themselves and in the jobs tray columns.
For job bubbles, there's a setting under Dispatcher Preferences called "Display Tags." Make sure that's turned on. If your dispatchers are in compact mode, they won't see much detail on the bubbles regardless, but in expanded mode the tags are visible right on the bubble.
In the jobs tray, you can control the column order and which columns are visible. I'd recommend having the Tags column reasonably high up in the list so dispatchers don't have to scroll to find it. There's also a truncation setting that controls how many tags show before it cuts off with a "+X" indicator. The default is five, which works for most companies. If you tend to have a lot of tags on jobs, you might bump it up. But if a job regularly has more than five or six tags, that's probably a sign you have too many tags in general.
Common Tag Mistakes (And How to Avoid Them)
The biggest mistake is creating tags without a plan. Tags accumulate fast, and once they're in use across hundreds of jobs, they're hard to clean up. Before you create a new tag, ask yourself: who's going to see this, and what are they going to do differently because of it? If you can't answer that, you don't need the tag.
Another common issue is duplicate tags. This happens when multiple people can create tags and there's no naming convention. You end up with "Member," "Membership," and "Active Member" all meaning the same thing. Pick one name and stick with it. Run a periodic audit of your tag list to merge or deactivate duplicates.
Don't bother with conversion tags outside of two specific use cases: equipment replacement age tracking and membership conversions. Conversion tags are an old legacy feature from the early days of ServiceTitan. They tie into some legacy reports that are, frankly, not worth using anymore. The custom reporting tools are far more powerful now. If you're trying to track things for reporting purposes, you're better off using custom fields, cross-sale groups, or just the built-in report filters. Save conversion tags for the two places where ServiceTitan still requires them, and skip them everywhere else.
Finally, watch out for tag bloat. If your CSRs have to scroll through 60 tags to find the right one during call booking, that's too many. A good rule of thumb: if you can't explain every active tag in your system in under two minutes, you need to trim the list.
Make Tags Work For You
Tags are simple in concept but they touch a lot of moving parts in your operation. The companies that get the most out of them are the ones that think about tags as a communication system, not just a labeling exercise. Set up default tags on your job types. Use conditional logic on forms to capture information automatically. Make sure equipment replacement tags are configured. And keep your tag list lean and well-organized so the information actually gets used by the people who need it.
If this was useful, the Blue Collar Nerd guide goes much deeper. Searchable video lessons covering tags, forms, dispatch configuration, pricebook setup, and every other part of ServiceTitan, built for every role on your team. Check it out here.