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

# Tags, lists, and exclusions

> Labeling companies, grouping them into lists, and permanently blocking domains Swan should never touch.

## Tags

Tags are free-form labels applied to **companies** — contacts aren't tagged directly. A tag is org-wide: its name is unique per organization, not per user, so everyone sees the same tag set, and tagging a company is visible to anyone in the org (on the company's page and in Desk filters).

Where: add or remove a tag on a specific company from that company's page (`https://agent.getswan.com/companies/{companyId}`). The org-wide tag list — create or delete a tag outright, and see how many companies carry it — is managed at [agent.getswan.com/settings/tags](https://agent.getswan.com/settings/tags). Filter the Accounts page by tag from the Tags filter on [agent.getswan.com/companies](https://agent.getswan.com/companies), or filter Desk by tag via its `companyTagIds` filter.

Tags exist for two purposes: organizing your company list, and acting as a filter or source for other parts of Swan — most notably, a [business event trigger](../triggers/business-events) can use a tag as its company source, so "any company tagged Enterprise" can drive an automation.

The agent can add tags to a company when instructed to, but there's no per-company tag removal — the only way to remove a tag from a company is to delete the tag itself, which removes it from every company at once. Deleting a tag is therefore an org-wide, irreversible action:

* It's stripped from every company that had it.
* Any trigger configured to use that tag as a filter gets that tag removed from its filters automatically.
* If the tag was a trigger's *only* company source, the trigger has nothing left to run on — Swan disables it and posts a Slack warning naming the affected triggers, so it doesn't silently stop working without anyone noticing.

Swan doesn't currently support saved views or ad-hoc saved filters on the companies or contacts pages — filters you apply are session-only. Tags (and CRM lists, if you have an integration) are the closest substitute for a persistent, reusable segment of companies.

## Lists

Lists group companies together, separately from ICP segments. A list can be:

* **Manual** — you (or the agent) add companies to it directly, for example by uploading a batch of domains.
* **HubSpot-list-backed** — tied to a list that already exists in your HubSpot account.

Note that this list model lives in Swan's data layer but has no dedicated lists-browsing screen in the app today. In practice you encounter lists indirectly — most visibly as HubSpot lists you pick as a source or exclusion on a trigger (see [Swan vs your CRM](swan-vs-your-crm)) — rather than as a standalone lists page you open and manage.

## Excluded companies

The excluded-companies list is a per-organization blocklist of domains Swan should never touch — competitors, existing customers you don't want prospected again, or anything else you want permanently off-limits. There's no screen for it in the app — you manage it through Swan itself: ask it in chat to add or remove domains from the exclusion list.

Excluding a company also blocks Swan from acting on it elsewhere: when the agent tries to create that company or start outreach against a contact who works there, the action is refused. (Under the hood, excluding a company in chat soft-deletes it, and Swan's create-company, search, and sequence-enrollment paths all skip soft-deleted companies.)

Separately, in the website-visitor identification pipeline, a visitor whose company domain is on your blocklist — or on a small global blocklist Swan maintains across all customers — is skipped before Swan spends anything identifying or qualifying the visit.

## Common questions

**If I delete a tag, does it also delete the companies that had it?**
No — only the tag and its association with those companies is removed. The companies themselves are untouched.

**Can two people in my org have differently-named tags for the same idea?**
Tag names are unique per organization, so once a tag exists, everyone reuses that same one rather than creating near-duplicates — Swan will suggest the closest existing tag if you try to add something similar.

**Will disabling a trigger because its tag was deleted lose its configuration?**
No — the trigger is disabled, not deleted. Update its company source (add a tag, a list, or another source) and re-enable it.

**Can I bulk-remove a tag from just some companies, not all of them?**
Not currently — tag removal is all-or-nothing at the tag level, not selectable per company.

**Does adding a domain to the excluded list retroactively stop an in-progress sequence?**
No. Excluding a company stops Swan from *starting* new outreach against its contacts, but it isn't a kill-switch for sequences already running — an already-enrolled contact keeps receiving their remaining steps, because sends check the contact's own status, not their company's exclusion. To stop an in-flight sequence, stop it on the contact directly.