A line-by-line diff — the audience's name, roles, and one line per rule, with removed and added lines marked.

Readable rule labels — brand, tag, and team names rather than raw IDs.

A live match count — “Matches N people” for a new audience, or the current and new size for a change, so a jump from 40 to 400,000 people is obvious before you approve.

An out-of-date warning — if someone edited the audience after Operator built the proposal. You can refresh, or apply anyway.

A warning banner — on a delete proposal when something still uses the audience.

Roles — An audience can apply to users, leads, visitors, or any combination. If you don't say, Operator applies it to all three and tells you so. Say “logged-in users only” to restrict it.

An audience with no rules is valid — “Everyone who is a logged-in user” is a role-only audience and a normal, correct result.

A match count of 0 is treated as a likely mistake — Operator offers a correction instead of asking you to approve it.

Nothing uses it — Operator proposes the deletion and says nothing references it.

Something uses it — Operator does not propose the deletion. It lists every object that uses the audience, by name and type, and tells you the deletion is blocked until those references are removed.

Operator can detach it for you — from articles, snippets, internal articles, Fin procedures, and Guidance rules. It offers once; say yes and it creates the detach proposals.

Some references you change yourself — workflows, Messenger settings, and file settings. Operator names them and tells you where to go.

If detaching leaves an item with no audience, that item applies to everyone again. Operator says so rather than picking a replacement.

“Which articles use VIP Customers?” — a content question. Operator searches your content filtered by that audience, can combine it with content type, state, and topic filters, and pages through long lists so you get the complete set.

“What uses VIP Customers?” — a whole-workspace question. Operator lists every referencing object of every type: articles, snippets, internal articles, workflows, procedures, Guidance rules, and more.

Audiences combine with OR — No audience on a content item means it applies to everyone. Attaching a second audience widens reach; it never narrows it. “Only X” means removing every other attached audience.

A content audience is not help center visibility — It decides whose conversations Fin and Copilot use the content in. It does not decide who can view an article on your help center, and it is not the same as switching content on or off for Fin.

Internal articles — The audience only decides whose conversations Fin and Copilot use them in. It never hides the article from teammates.

Guidance — A Guidance rule with no audience applies to every customer. The same OR rules apply.

“Hide this from X” is not “attach X” — Attaching X would use the content only for X. Hiding needs an audience that matches everyone except X. Operator builds it with negative rules (“is not”, “is none of”, “does not contain”) or “is not in audience X”, and attaches it as the only audience. A new audience must be approved before it can be attached, so Operator proposes the audience first.

Article audiences are per language version.

It builds rules only from attributes your workspace can target, and never invents an attribute. If your wording doesn't obviously match one, it picks the plausible one and tells you which and why.

It looks up conversation tags, the Team assigned attribute, and subscription types by name. If several match, it asks.

It refuses archived tags. An archived tag still matches conversations that already carry it, so an audience built on one looks healthy while it quietly stops growing.

It refuses new rules that point at a deleted tag, team, subscription type, or audience. A deleted brand value shows as a warning.

It only uses comparisons the Audiences editor offers, so every proposal can be edited later in your settings. It doesn't use “not” groups.

For audits, counts, and clean-ups it reads the full list of audiences, so it never presents a partial list as complete.

Approval is always required — There is no “just do it” mode for audiences.

Workflows, Messenger, and file settings — Operator can't remove an audience from these yet. It names them and says where to change them.

External content and files — Operator can't attach audiences to external (synced) content or files. Change those in their own settings.

No workspace-wide “content with no audience” count — Operator can list content per audience, but can't yet count all content that applies to everyone.

Match counts are point-in-time — Correct when read, and they drift as people change.

A new audience must be approved before it can be attached — Operator proposes the audience first and attaches it after approval.

Releases — If a content change is saved to a Release, the audience part is applied at once for new content and left out for live content, because audiences are not versioned in Releases.

Raw codes in previews — Occasionally a rule value shows as a code (for example the language code es instead of “Spanish”). The proposal is still correct.

Teammate assignees — Only the Team assigned attribute is resolved by name; individual teammate assignee values are not.