Tag every record. Automate the rest.
Color-coded tags on Clients, Jobs, Invoices, Leads, Properties, and Users — combined with Auto-Tag Rules that classify records the moment they're created, Slack alerts the second something important lands, and dispatch-board chips your techs can read at a glance. This isn't a sticky note. It's an operations layer.
Every record. Every list. Every export.
Tags aren't tucked into one corner. They're a primitive that shows up on every primary record, every index, every saved view, every export, every integration. The missing organization layer between Status (lifecycle) and Notes (free-form context) — searchable, filterable, automatable.
Filter anywhere
Every index has a Tags filter with Any / All match modes. Stack with status, date, location, and Custom Fields — then save as a one-click Saved View.
Dispatch chips
Mark a tag Show on dispatch board and it becomes a colored chip on every appointment card. High-importance tags sort to the front.
Bulk tag 500 at a time
Check the rows you want, hit Add tags from the bulk-actions bar, apply up to 10 tags to 500 records in a single action.
Promote from parent
Open a new job for a VIP, Gated client and both tags are sitting right there in the picker — one click each. No retyping. No hunting.
Configure once. Run forever.
This is where tags become a force multiplier. An Auto-Tag Rule watches a record type for an event — created, updated, status_changed, or tag_added — and applies a tag the instant a record matches a pattern you define. Lead source, job total, ZIP code, email domain, contains-this-substring — combine them with AND logic and let the system do the classification work.
@acmecorp.comRecallYelp, Google LSA, Referral55401, 55402, 55403$5,000Chains are protected by two invisible guardrails: a maximum depth of 5, and short-circuit detection so any tag already applied in the chain won't be re-applied. Misconfigured rules can't run away.
The moment something important lands, the right people know
Configure any tag to post to a Slack channel or email up to five recipients the second it's applied — manually, by an Auto-Tag Rule, or by an integration. Built-in once-per-hour de-duplication on each (tag, record) combo means dispatchers can't accidentally spam the channel by adding-and-removing while testing.
A tag that pings too often becomes noise. Reserve alerts for the tags that genuinely require human action — Hot Lead, Damage Reported, VIP, After-Hours. The rest stay silent and still do their organizing work.
Tagged data flows everywhere your team works
Tags are a column on the Jobs, Clients, and Invoices lists — up to three chips per row inline, with a +N pill for the rest. Every CSV export gets a pipe-delimited Tags column that drops cleanly into Excel, Google Sheets, or your downstream BI tool. Custom Fields keep their own column-per-field layout in the same file.
Job ID,Customer,Status,Total,Tags,Custom: Filter Size,Custom: PO # 4128,Porter Residence,Completed,$842,"VIP | Recall | Pet on Site",16x25x1,— 4129,Maple Ct.,Open,$1,420,"Gated | High Value",20x25x4,PO-8821 4130,Janet H.,Open,$0,"Google LSA | Hot Lead",—,— 4131,Adams Property Mgmt,Completed,$5,280,"VIP | Tenant Occupied | High Value",—,PO-8830
Filter the index to just the records you care about, hit Export, and every chip travels with the row.
Saved Views
"Open VIP invoices past due" or "Recall jobs in Sam's coverage area" — save the tag + status + date combination once and it's a single click forever after.
Source-of-revenue reporting
With Auto-Tag Rules feeding lead source onto every job and invoice, you can finally answer "what's our LSA ROI this month?" in two clicks.
First-class events in webhooks, Zapier, and MCP
Tag changes aren't bolted on top of generic update events — they fire their own dedicated events with the tag's id, name, short code, and color in the payload so subscribers don't have to do a lookup. Connect once, automate forever.
Webhooks
Dedicated events for every record type. Filter your subscription to just the tag events you care about.
client.tag_added
job.tag_added
invoice.tag_added
lead.tag_added
property.tag_added
user.tag_added
Zapier
Built-in triggers and actions on day one — kick off a Zap when a tag lands, or apply a tag from any Zap step.
Trigger: Tag added
Action: Add tag
Action: Remove tag
System-managed tags
Integration-applied tags (like the locked Google LSA tag on LSA-sourced leads) are protected from accidental edits but fully filterable, alertable, and chainable into your own rules.
AI & MCP
Ask Claude or ChatGPT: "How many jobs got the Recall tag this month?" Tags are first-class in the MCP toolset alongside jobs, clients, and invoices.
A few things teams do on day one
Common patterns we see in the wild — and the dispatch / sales / ops payoff each one delivers.
| Tag | Applied by | What it unlocks |
|---|---|---|
| VIP | Auto-rule on Acme email domain | Office sees it on the dispatch chip, routes to senior tech, posts to #vip-customers. |
| Pet on Site | Manual on the property | Promotes from Client to every new Job. Tech knows before they pull up to the door. |
| Gated | Manual on the property | Dispatch chip pulls the eye to property notes for the gate code. |
| Recall | Auto-rule when job type = Recall | Service manager gets alerted, recall jobs reportable, accountability for original work. |
| Google LSA | System-managed by integration | Track LSA-sourced revenue end-to-end. Chains into Hot Lead. |
| High Value | Auto-rule when invoice total > $5,000 | Owner gets eyes on every big-ticket invoice for approval review. |
| North Region | Auto-rule on ZIP code | Auto-segments properties by service area. Saved Views per region. |
| Damage Reported | Manual on the job | Owner email + #owners Slack the second it's applied. Insurance follow-up never slips. |
Powerful where it matters. Safe where it counts.
Tags get the polish of a feature people use every minute of the workday — and the guardrails of a feature that automates production data.
Hotkey-fast
Press T on any record to open the picker. Type to filter. Click to apply. The chip appears immediately.
Archive, don't delete
Retiring a tag preserves history on every record it ever touched. Restore from the Archived filter in one click.
Merge duplicates
Office accidentally created "VIP" and "V.I.P."? Merge in one action — every record reassigns, source archives, integrations stay in sync.
Role-aware
Admins create & edit. Dispatchers and CSRs apply. Locked system-managed tags can't be removed by accident.
Location scoping
Leave a tag account-wide or scope it to a single shop. Multi-location ops get their own pickers without cross-contamination.
Edit-storm protection
Slack & email alerts de-duplicate the same (tag, record) combo to once per hour. Test loops never spam the channel.
Stop hunting. Start tagging.
Color-coded, automatable, alert-ready tags on every record — included with every Dispatch Scout account.
Tags & Auto-Tag Rules FAQ
(tag, record) combo only alerts once per hour, so test loops never spam the channel.client.tag_added / job.tag_added / etc. events with the tag's id, name, short code, and color in the payload. Zapier ships built-in triggers and actions for every record type.