Describe a useful audience
Write the audience in terms of the notice people expect: for example, members who requested updates about a weekly workshop. Avoid vague labels such as “all contacts” or “everyone in the database.” A broad label conceals different relationships, permissions and preferences. The planning brief should make clear who is included, why the message is relevant and who should remain outside the proposed send.
Separate known from unresolved
Use three aggregate numbers: potentially relevant contacts, confirmed eligible recipients and unresolved records. Only the second belongs in a ready-to-send assumption. Do not convert an unknown category into zero just to make a budget look tidy. A high unresolved count is an implementation task, not evidence that the product needs a larger plan. This website does not accept contact lists or verify anyone’s permission.
Watch overlapping groups
A person may belong to more than one community group. Adding each group’s count can overstate unique recipients or result in duplicate notices if the eventual system is not configured carefully. Record whether a campaign targets a single group, a deduplicated union or separate notices with different purposes. Confirm the merchant’s actual grouping and duplicate-handling behavior before relying on it.
Use a bounded example
A fictional center has 240 records, but only 160 have a confirmed current basis for the proposed workshop updates; 50 are unrelated and 30 need review. The initial planning audience is 160, not 240. If two eligible groups overlap by an unknown amount, leave the combined count unresolved until it is reconciled. That discipline avoids pretending a neat spreadsheet is a valid messaging audience.
Make the unknown actionable
For an unresolved aggregate count, write the role that can reconcile it and the evidence needed. A note such as “membership owner to review workshop preferences” is more useful than a guessed number. Do not put names, telephone numbers or consent records into this website’s local brief; the planning artifact is a list of decisions, not a contact database.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- TXT180 pricing — Merchant documentation · txt180.com · Merchant-controlled · checked 2026-10-02
- TXT180 feature documentation — Merchant documentation · txt180.com · Merchant-controlled · checked 2026-10-02