---
name: brandwell-audiences
description: "Build and manage audiences: static lists and live audiences from rules, a plain-words description or a saved ICP ('make a new audience of VPs of sales in Texas'), preview who matches, add or remove people, add enrichment columns, and send an audience to an Outreach campaign or a postcard campaign. For searching the Lead Database itself use brandwell-lead-database, for one person's record use brandwell-people-and-records."
allowed-tools: audiences_rules_from_text audiences_preview audiences_list audiences_get audiences_cell_log audiences_create audiences_update audiences_add_people audiences_remove_people audiences_add_column audiences_run_column audiences_add_to_campaign audiences_send_postcards marketpulse_list_feeds
metadata:
  title: "Audiences"
  service: records
  page: "#/marketpulse/people"
---

# Audiences

Confirm facts with this skill's tools before stating them; what the page shows is a starting point, not the answer. When no tool can confirm something, say so and offer BrandWell support. Never say BrandWell cannot do something unless a tool says so.

Read audiences_list for the same source groups, counts and saved meter as Audiences. Use audiences_get for a scoped sheet and its on-join workflow. Cell values stay on the page; use the open link. Never decode a cursor to obtain record data. Keep pagination filters unchanged.

Create a static list or a live audience over saved fields and observed signals using all/any rules. For an intent topic, read marketpulse_list_feeds first for its exact active topic; activate new topics through Topics so plan limits apply. An optional icp_id must identify a saved ICP in this project. Missing job titles do not exclude otherwise matching people. Review the requested rules explicitly; use only the documented fields, operators and signal vocabulary. Updating rules refreshes membership atomically while saved people remain retained. Saved Lead Database searches and CRM-source creation explain their current setup requirements. Do not claim an unavailable source was created.

Audience changes require a stable idempotency key and current editing permission. Replays do not create duplicate lists or columns. Adding people enforces the account saved-record limit. Adding a column returns an estimate but does not fill it. With auto_run on, a column fills new members as they join; paid cells stay inside Workflow Wallet holds and spending limits. Attaching an on-join draft with audiences_update does not activate or start it. Use the separately confirmed workflow start path when asked to run.

Use audiences_run_column to fill one saved column. The server quotes its exact missing rows and maximum charge. Respect needs_confirmation and never invent a token. An enabled account budget can approve a bounded paid fill; otherwise wait for the person. Queued is not completed. The full quote stays reserved until settled results or a safe Stop; follow the page for actual results. Keep the same arguments and request key on retries.

Use audiences_rules_from_text to draft supported signals and canonical profile criteria from the person's description. Show any unmapped-wording warning and the exact draft before saving. The icp criteria must match in addition to the all/any field and signal rules. Use audiences_preview for current membership counts, then pass the reviewed rules unchanged to audiences_create. Drafting and previews do not purchase data or change a saved ICP.

Use audiences_add_to_campaign to add existing people to an Outreach campaign by person_ids, or by audience_id with the same q and filter as the page. Every person waits in Approvals and nothing sends until a person approves. Unsubscribed people and people with no email are skipped and counted. Say that they wait for approval; never say they were emailed.

Use audiences_send_postcards to mail personalized postcards from a manual Direct Mail campaign. Each is $1.02 from the Workflow Wallet. It always returns a quote with the exact total first and needs the person to confirm; never invent a token. People with no mailing address and unsubscribed people are skipped and not charged. Queued is not mailed: follow the returned page link.


Rules:
- Go one step at a time and ask one question at a time. In the BrandWell app's chat, ask with ask_person; never put a question at the end of a reply.
- Show the price before anything that spends: a column fill, a postcard, an export or a paid lookup. Name how many exports a call uses.
- When the Workflow Wallet is short, load brandwell-wallet and give the add-funds link. Never say funds were added. Keep every request scoped to the current BrandWell project.