Back to all articlesAudience segmentation

Choose whether audience eligibility belongs to a person or an account

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A business buys a product. The purchase is recorded against its account. A segment then selects every contact attached to that account—including a purchaser, a technical user, and someone at a branch that does not use the product. The account fact is accurate; the audience is not.

The practical answer to account-level versus contact-level segmentation is to separate the unit that qualifies from the person who receives a message. An account purchase can qualify the business for customer reporting or establish context for a contact. It does not, by itself, establish that each contact purchased, uses, needs, or wants information about that product.

Start with the intended action, define the evidence required for the recipient, and allow only named account facts to support that decision. The filled hypothetical worksheet below shows how to do this without discarding useful account context.

1. Choose the unit by asking what the segment will do

Before building a filter, finish this sentence: This segment exists so that we can… The answer determines whether the qualifying unit should be an account or a person.

  • Count customer businesses: qualify accounts. A business-level purchase is sufficient evidence that the account bought the product.
  • Review adoption across customer businesses: qualify accounts for investigation. Do not interpret that account list as a ready-to-message contact list.
  • Send procurement information: qualify people whose purchasing responsibility is supported by evidence.
  • Invite users to technical onboarding: qualify people whose use of, or responsibility for, the product is supported by evidence.

An account-level segment can be the first stage of a contact-level audience. The second stage must still select appropriate recipients. Otherwise, a useful business filter becomes an unsupported claim about everyone associated with the business.

Write separate labels for these stages. For example, “accounts with an active purchase” describes the business population, while “confirmed technical users at those accounts” describes potential recipients. Avoid a label such as “product customers” when the team cannot tell whether it means businesses, buyers, or users.

2. Separate shared context from personal evidence

Account facts and contact facts answer different questions. An account fact may establish that a business has purchased a product, that a contract covers a particular branch, or that an order remains active. A person-specific fact may establish that someone placed the order, confirmed technical responsibility, or asked for help with a particular task.

Use three categories when deciding whether information may influence contact eligibility:

  • Shared context: a true statement about the associated account. It can narrow the pool without describing the individual.
  • Scoped applicability: an account fact that applies only to a named branch, project, department, or contract scope. It supports a contact decision only when the contact's relevant connection to that scope is established.
  • Person-specific evidence: a statement about the individual's role, activity, request, or expressed need. This must not be inferred merely from account membership.

Prefer “associated account purchased the product” over copying “purchased the product: yes” onto every contact. The first preserves what the evidence actually says. The second can make an unrelated person look like the buyer.

Likewise, an account's implementation issue can justify investigating who is affected. It cannot establish that every contact has that issue. Keep the account condition and the individual's need as separate facts, even when they eventually support the same decision.

3. Filled hypothetical account-to-contact worksheet

Fictional worked example: All names, products, dates, and outcomes in this worksheet are hypothetical. They illustrate a recommended operating design, not customer results or a claim about available software controls.

Account: Cedar Works. Its order record shows an active purchase of a hypothetical equipment-monitoring product, Signal Kit. The order covers the North workshop only. The South branch is not included. A North workshop project note says that setup is incomplete; it does not identify every affected person.

Audience being prepared: invitations to a North workshop technical setup session. A separate procurement update may be prepared for the purchasing contact. These are different purposes and should not share an undifferentiated recipient list.

Worksheet entry: Maya, purchaser

  • Recorded relationship: Maya is listed as the purchaser on the North workshop order. Her order correspondence says she handles procurement and identifies Leon as the technical user.
  • Account context she may inherit: her associated account has an active Signal Kit purchase. The relevant order covers the North workshop.
  • Scoped fact she may use: the North workshop setup is incomplete, as project context for a procurement conversation—not as proof that Maya personally needs technical help.
  • Facts requiring person-specific evidence: whether Maya operates the product, needs setup training, or wants technical-session invitations.
  • Procurement audience decision: include on relevance grounds because the order identifies her purchasing responsibility.
  • Technical-session decision: hold out. Her purchasing role does not establish technical use, and her correspondence points to Leon.
  • Next evidence needed: a direct request or confirmation that she also has a technical responsibility.

Worksheet entry: Leon, technical user

  • Recorded relationship: Leon's project correspondence confirms that he operates Signal Kit at the North workshop and asks for help completing setup.
  • Account context he may inherit: his associated account has an active Signal Kit purchase.
  • Scoped fact he may use: the purchased product and incomplete setup concern the North workshop, where his confirmed technical responsibility sits.
  • Person-specific evidence already present: his own correspondence establishes product use and a setup-help request.
  • Technical-session decision: include on relevance grounds. The account facts establish the applicable purchase; his own evidence establishes the need.
  • Procurement audience decision: hold out unless there is separate evidence of purchasing responsibility.
  • Next evidence needed: check whether the setup request remains unresolved before including him in a later session.

Worksheet entry: Priya, unrelated branch contact

  • Recorded relationship: Priya works at the South branch. Her recorded enquiry concerns a different service, with no stated North workshop responsibility.
  • Account context she may inherit: her associated business has purchased Signal Kit. This remains business context, not a personal customer need.
  • Scoped facts she may not inherit: North workshop coverage, North workshop product use, or the North workshop setup problem as a condition affecting her.
  • Facts requiring person-specific evidence: any responsibility for Signal Kit, involvement in the North project, or interest in technical training.
  • Technical-session decision: exclude from this audience. Neither applicable scope nor personal relevance is established.
  • Procurement audience decision: exclude from this audience. Sharing an account with Maya does not establish purchasing responsibility.
  • Next evidence needed: none for this campaign. Reassess only if relevant new information arrives.

The worksheet retains the same true account purchase for all three contacts while reaching different recipient decisions. It also avoids turning “not established” into “never relevant.” Maya could later become a technical participant; Priya could later join the North project. Those changes would require new evidence, not broader inheritance.

4. Turn the worksheet into an explicit eligibility rule

For the hypothetical technical session, use a rule with distinct gates:

  1. Account context: the associated account has an active Signal Kit purchase.
  2. Applicable scope: the purchase covers the North workshop, and the person's relevant responsibility connects them to that workshop.
  3. Personal relevance: current evidence establishes technical use or technical responsibility and an unresolved setup need.
  4. Communication eligibility: the proposed channel and message meet the recipient's applicable permission and suppression requirements.

These gates answer different questions. Passing the purchase gate cannot compensate for failing the scope gate. A job title cannot replace evidence of a current need when the audience promises need-specific help. Permission to receive messages cannot make an irrelevant person relevant.

Store or document a reason for each decision. A useful reason reads “confirmed North workshop user; setup request unresolved,” rather than simply “matched segment.” For a hold, record the missing condition, such as “purchasing role confirmed; technical responsibility unknown.” This makes review possible without reconstructing the entire decision.

If your current tools cannot express the distinction reliably, prepare a reviewed recipient list rather than weakening the rule to include all account contacts. Check your workspace and current plan before relying on any proposed segmentation or review capability.

5. Decide how much uncertainty the audience can tolerate

Requiring person-specific evidence creates a trade-off: a smaller, better-supported audience may miss someone who is genuinely relevant but poorly documented. Broad inheritance creates the opposite problem: it reaches more people while asserting relevance the records do not support.

Choose according to the message's claim. A narrowly framed technical session for people with an unresolved setup problem needs stronger evidence than a broad account update. But even an account update needs an appropriate recipient selection rule; it should not default to every associated contact.

Use three decision states:

  • Include: the required conditions are supported.
  • Hold for evidence: a plausible relationship exists, but a required fact is missing or unclear.
  • Exclude from this audience: known scope or relevance does not match the purpose.

Do not send a promotional message merely to resolve uncertainty about whether someone belongs in its audience. Review existing correspondence or obtain clarification through an appropriate, permitted interaction. A hold is a valid outcome; it need not become a new outreach campaign.

Evidence should also remain tied to its purpose. Maya's procurement role supports procurement communication. It should not become a permanent shortcut for every future product campaign.

6. Keep relevance separate from permission and sending

The worksheet determines who has a supported reason to receive a particular message. It does not establish permission to use a communication channel, and it does not mean the message has been sent.

For WhatsApp, recipient permission matters and opt-outs must be honoured. Approved templates are used to initiate Platform conversations and outside the 24-hour customer-service window, which opens or resets with a user message. Consult the current WhatsApp Business Messaging Policy for precise requirements.

Keep audience preparation, template review, and actual delivery as separate states. Template approval does not guarantee delivery. If an authorised automated workflow is used, provide a clear route to a human for questions or unresolved issues.

In the hypothetical worksheet, Leon's relevance decision therefore means “supported candidate for this technical-session message,” not “permission confirmed,” “template approved,” or “delivered.” Those checks must remain visible rather than being hidden inside a single eligible flag.

7. Repair an audience that already inherited too much

If an existing segment selects all contacts at purchasing accounts, start by pausing further use of that audience for the affected purpose. Preserve the old rule so the team can identify why people qualified.

  1. Separate the facts: distinguish genuine account purchases from contact fields that were populated solely through inheritance.
  2. Reassess recipients: apply the new scope and personal-evidence gates. Do not treat prior inclusion as evidence of relevance.
  3. Review pending work: inspect prepared lists and queued messages before further authorised sending.
  4. Correct the interpretation: retain the valid account purchase, but remove or qualify unsupported claims that individuals bought, used, or needed the product.
  5. Handle responses accurately: record corrections such as “not involved in this project” and honour opt-outs. Do not send a blanket explanation to unrelated contacts merely because they were previously selected.

A common repair failure is to rename the segment without changing its logic. Another is to replace one broad assumption with another—for example, treating every technical job title as proof of involvement in the purchased product. Test the evidence, not just the label.

8. Run a bounded review before the next audience is used

For the next campaign, create one worksheet entry per candidate contact using these headings: associated account fact, applicable scope, person-specific evidence, decision, missing evidence, and review trigger. Keep the campaign purpose at the top so reviewers judge relevance against the same task.

Compare the old account-only selection with the evidence-based selection. Record:

  • How many contacts qualify solely because of account membership.
  • How many have documented personal relevance.
  • How many fail the applicable branch or project scope.
  • How many are held because evidence is missing or outdated.
  • How many included contacts have a readable reason tied to the intended message.

In the hypothetical example, an account-only rule selects all three contacts. The technical-session rule supports Leon, holds Maya for missing technical evidence, and excludes Priya because the relevant scope is not established. This difference measures the effect of the rule; it is not a forecast of response or sales.

The next action is concrete: take one planned audience, complete the worksheet, and require a supported inclusion reason for each proposed recipient before authorising sending. The account can explain why the business matters. The person's evidence must explain why this message belongs with them.

Audience segmentationCRMContact eligibilityAccount data

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications