June 1, 2026 · 7 min read
Tags just grew up. What started as quick color-coded labels for leads and properties now spans your whole operation — clients, invoices, jobs, and users included. The little notes you’ve always kept in your head (“this one’s a VIP,” “watch the dog at this address,” “that invoice is a warranty job”) finally live on the record, where everyone can see them, filter by them, and act on them.
Let’s be clear about what this is: tags are a first-class part of Dispatch Scout, not a sticker you slap on top of a record. They’re built into the data model itself — with their own permissions, their own settings, their own automation rules, and a guaranteed place in every API response and webhook payload. You’ll find the full library under Account Settings > Tags, and you’ll find tags themselves woven through the records, lists, and integrations you already use every day.
Every service business runs on context that never quite makes it onto the record. The dispatcher knows which account is a headache. The lead tech remembers which address has the gate code and the territorial dog. The bookkeeper knows which invoice is really a warranty job. That knowledge lives in people’s heads — and walks out the door when they take a day off.
Tags are short, color-coded labels that sit right between Status (where a record is in its lifecycle) and Notes (your free-form scratchpad). That placement is deliberate — tags aren’t a comment tacked onto the bottom of a record, they’re a structured field that lives next to the most important data you track. They’re searchable, filterable, automatable, and exportable — the structured middle ground between a rigid status field and a paragraph nobody reads. And now they cover more of your business than ever.
You could already tag leads and properties. Now you can also tag:
VIP account or a Net 30 payer at a glance.Warranty job or a Recall so billing knows the story.Pet on Site, Gate Code, or Two-Tech before the truck rolls.On-Call tech or who’s certified for Ductless.Everything you already rely on is still here: 1–4 letter short codes, Standard vs. High importance, optional “show on dispatch board” chips, account-wide or per-location scope, and Auto-Tag Rules that apply tags automatically when a record matches a pattern. The tag picker is also smoother and faster, so creating and applying tags just feels cleaner.
A label is only useful if you can pull up everything that wears it. Index pages like Leads and Users now let you filter by tag, and you can show or hide a tags column from the column-density menu — so your lists stay as tidy or as detailed as you want.
The Tags settings page got the same treatment: search plus filter chips for All, Active, On dispatch, System, and Archived. Need every Pet on Site job before tomorrow’s routes go out? Two clicks. Want every client carrying your VIP tag? Filter and go.
Tag libraries get messy. Someone types VIP, someone else types V.I.P., and now your filters miss half the accounts you meant to catch. Admins can now merge one tag into another to consolidate those duplicates.
Here’s how it works, plainly:
One heads-up: a merge fires a tag change on every affected record, which can briefly flood any automations you’ve connected. If you’re consolidating a heavily used tag, run the merge outside business hours to keep things calm.
Tags now have their own permissions, so you can let everyone use them without letting everyone rewrite your tag library. You’ll find them under user permissions in the Tags group (look for the tags icon).
apply_tags lets staff stick existing tags on records — dispatchers, techs, and CSRs can flag a Recall or Pet on Site without touching the library.tags_view, tags_create, tags_update, tags_delete control the library itself, and the management permissions default off — they have to be granted.The result is a clean division of labor: admins curate the official tag list, and everyone applies. No more accidental sprawl of one-off tags that nobody else recognizes.
Tags don’t stop at the screen — they now flow into your integrations. Tags are included in API responses and in outgoing webhook and Zapier event payloads for clients, invoices, jobs, and leads.
That means your automations can finally react to tags. A new client tagged VIP? Fire a Slack alert to the owner. A job tagged Recall? Kick off a Zapier zap that loops in the warranty team. An invoice tagged Net 30? Route it down a different reminder path. The labels your team applies become triggers your business runs on.
Organization isn’t busywork — it’s how a growing team keeps acting like a small one that knows every customer by name. When the context lives on the record instead of in someone’s memory, the new dispatcher books the two-tech job correctly, the covering CSR treats the VIP like a VIP, and the bookkeeper sends the warranty invoice down the right path — without anyone having to ask around.
That’s the difference between a bolt-on labeling widget and a first-class feature. A bolt-on lets you scribble a note on one screen. A first-class system gives tags a home in your settings, a permission model around them, automation rules to apply them, filters on every list to find them, merges to keep them clean, and a place in every API response and webhook so the rest of your stack can act on them too. Tags in Dispatch Scout are the second kind — designed in, not stapled on, and treated like the core data they’ve become. Want the full picture of how tagging fits the rest of the platform? See the Tags & Auto-Tag Rules feature page.
Clients, invoices, jobs, and users — in addition to the leads and properties you could already tag. Tags sit between Status and Notes on each record, so the context you used to keep in your head finally lives where everyone can see it, filter by it, and act on it.
Auto-Tag Rules apply a tag automatically whenever a record matches a pattern you define, so staff don’t have to remember to label things by hand. They work alongside short codes, importance levels, dispatch-board chips, and account-wide or per-location scope to keep your tagging consistent.
Yes. Index pages like Leads and Users let you filter by tag, and you can show or hide a tags column from the column-density menu. The Tags settings page adds search plus filter chips for All, Active, On dispatch, System, and Archived — so pulling up every record that wears a given tag is two clicks.
Merging re-points every record from the source tag to the target tag, then archives the source. You can restore an archived tag, but the record reassignments are permanent. A high-usage merge — source tag on 100 or more records — asks you to type MERGE to confirm. Because a merge fires a tag change on every affected record, consolidate heavily used tags outside business hours.
Yes. Tags are included in API responses and in outgoing webhook and Zapier event payloads for clients, invoices, jobs, and leads — so your automations can react to them.
The apply_tags permission lets dispatchers, techs, and CSRs stick existing tags on records. The management permissions — tags_view, tags_create, tags_update, and tags_delete — control the library itself and default off, so admins curate the official list while everyone else just applies.
Tags everywhere are available now on every Dispatch Scout account. Head to Account Settings > Tags to build out your library, set up Auto-Tag Rules, and try a merge to clean house. Grant the apply_tags permission broadly, keep the management permissions with your admins, and start labeling the context your team has been carrying in its head.
Tag once. Filter, automate, and act everywhere.
Tag clients, invoices, jobs, and users in Dispatch Scout — then filter, merge, and automate on every label your team applies.
Start Free TrialDispatch Scout is field service management software built for growing service businesses. From scheduling and dispatch to invoicing, payments, service plans, fleet management, and call tracking — it’s everything your operation needs in one platform.