> ## Documentation Index
> Fetch the complete documentation index at: https://docs.servicebooked.ca/llms.txt
> Use this file to discover all available pages before exploring further.

# Tags

> Free-form labels you can stick on any contact to organize, filter, and target campaigns.

Tags are the lightweight way to slice your CRM. Stick `vip`, `commercial`, `seasonal`, `repeat`, or anything else on contacts, then filter and target campaigns based on those labels.

## How tags work

* Tags are **strings** — anything you can type. Lowercase by convention but we don't enforce.
* A contact can have **any number** of tags.
* Tags are **org-wide** — you build a tag library at **Settings → Tags**; every team member sees the same options.

## Apply tags to a contact

Three ways:

### From the contact detail

Open a contact, click the **Tags** field, type or pick from existing. Press Enter or comma to commit each tag.

### From the contacts list (bulk)

Select multiple contacts via checkboxes, click **Apply tag**, pick or type the tag, confirm. All selected get the tag added (existing tags preserved).

### Auto-applied by forms

Forms can be configured to automatically apply tags on every submission — e.g., every "quote request" form submission gets the `quote-request` tag. Configure in **Forms → \[your form] → Pipeline integration → Auto-tags**.

## Filter by tag

In the contacts list, the **Tag filter** dropdown shows all tags in your org. Pick one to filter the list. Pick multiple to AND them.

## Target campaigns by tag

[Reactivation campaigns](/reactivation/audiences) use tags as one of their primary audience filters. Build an audience like "everyone tagged `commercial` who hasn't booked in 6 months" — exactly the kind of segment you'd want to re-engage.

## Tag library

**Settings → Tags** shows every tag in your org with usage counts. From here you can:

* **Rename** a tag (renames everywhere it's applied)
* **Delete** a tag (removes from all contacts; the contacts themselves stay)
* **Merge** two tags (e.g., consolidate `commercial` and `comm` into one)

## Naming conventions

Tags are forgiving but a few rules of thumb:

* **Use kebab-case or snake\_case** — `quote-request` or `quote_request` rather than `Quote Request`. Easier to type, no caps inconsistency.
* **Avoid duplicates by typo** — `vip`, `VIP`, and `v-i-p` would all be different tags. Pick one and stick with it.
* **Group related tags with a prefix** — `service:commercial` and `service:residential` means you can filter by prefix later.
* **Keep them short** — single words or 2–3 words. Long tag strings clutter the UI.

## When to use tags vs statuses vs custom fields

* **Status** — exclusive (a contact has exactly one) — what stage are they at? Lead, Booked, Customer, Cancelled.
* **Tags** — many — what's true about them? VIP, commercial, repeat, seasonal.
* **Notes** — free-form text — anything else.

So use a status for "where they are in your pipeline" and tags for everything else you want to know about them.

## Next

<Card title="Statuses" icon="circle-dot" href="/contacts/statuses">
  The pipeline stages each contact moves through.
</Card>
