Decide what to do when audience eligibility data is missing
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A contact has no product ownership value. One audience includes them because they are not recorded as an owner; another excludes them because ownership is unconfirmed. Both rules look plausible, but they make opposite assumptions about the same blank.
The fix is to separate evidence from action. Evaluate each eligibility condition as true, false, or unknown, then explicitly decide what unknown means for that audience: exclude from the target, route to review, or consider a separately defined fallback. Never let a blank silently become yes or no.
This does not require filling every missing field before work can continue. It requires knowing which claims need evidence, what action uncertainty permits, and what would change membership.
1. Define the claim before interpreting the blank
Start with a statement that evidence could support or contradict. “Product field is populated” is a data-quality check. “Contact owns Product A” is an eligibility claim. They are not interchangeable.
For each condition, document the claim, accepted evidence, and when that evidence needs reconsideration. Use these states:
- True: accepted evidence supports the claim.
- False: accepted evidence contradicts the claim.
- Unknown: evidence is missing, ambiguous, conflicting, or insufficiently current for this decision.
False must mean more than “we could not find a yes.” A populated field is not automatically reliable evidence either. A value copied from an unrelated record may leave the claim unknown.
Negation deserves special care. If “owns Product A” is unknown, “does not own Product A” is also unknown. A filter such as “ownership is not yes” may capture both confirmed non-owners and unrecorded ownership. That is different from an audience of confirmed non-owners.
Choose evidence standards according to the communication. Owner-specific instructions may require confirmed ownership; a requested general resource may not. The latter still needs its own relevance criterion.
2. Separate the evidence state from the membership decision
A condition’s state describes what is known. A membership decision describes what the team will do about it. Document these separately so the reason for inclusion does not disappear inside a filter.
A useful working record contains the condition, its state, supporting evidence and date, membership result, and reason. Where review is required, add an owner and next action. These are recommended operating fields, not claims about available product controls.
For required conditions joined by AND, apply this logic:
- All conditions true: the eligibility test is true.
- Any condition false: the eligibility test is false.
- No condition false, but at least one unknown: the eligibility test is unknown.
For genuine alternatives joined by OR, one true condition makes the test true. All false makes it false. Otherwise, the result is unknown. Do not introduce an OR simply to rescue contacts with missing data; each alternative must independently justify membership.
Apply routing only after evaluating eligibility. A contact with unknown ownership can be excluded from the owner audience and assigned to ownership review simultaneously. Review is a work queue, not evidence of eligibility or authorisation to send.
3. Use a filled decision table to make unknown outcomes explicit
Fictional worked example: A business is preparing owner guidance for Product A, a location-restricted service offer, and guidance for a specified service need. It also has a general service guide for people who explicitly requested that resource. All records, rules, and outcomes below are hypothetical.
For the three target decisions, assume other required conditions have passed solely to isolate the missing-data question. The fallback decision is different: it explicitly requires its own recorded request. Channel permission and suppression checks remain separate.
Copy this filled artifact into an operating document and replace the hypothetical evidence standards with your own:
Rule version | Hypothetical version 1 Scope | Audience membership only; not permission to send Case | Unknown product ownership Claim | Contact owns Product A Accepted evidence | Current confirmed ownership record Observed evidence | Ownership field is blank State | Unknown Target result | Exclude from Product A owner audience Other result | Assign to ownership review Reason | Owner guidance requires confirmed ownership Evidence for true | Current accepted record confirms ownership Evidence for false | Current accepted record confirms non-ownership Unresolved at checkpoint | Remain outside owner audience Case | Missing service location Claim | Service address is inside the supported area Accepted evidence | Confirmed service address checked against coverage Observed evidence | Phone number present; service address absent State | Unknown Target result | Exclude from location-restricted offer Other result | Hold outside this campaign; no fallback offer Reason | This audience requires a confirmed service address Evidence for true | Confirmed service address matches coverage Evidence for false | Confirmed service address is outside coverage Unresolved at checkpoint | Remain outside restricted offer Case | Absent need evidence Claim | Contact has the specified service need Accepted evidence | Current explicit statement of that need Observed evidence | No accepted evidence of the specified need State | Unknown Target result | Exclude from need-specific audience Fallback claim | Contact explicitly requested the general service guide Fallback evidence | Recorded request for that guide Fallback result | Include only if that request is confirmed and active No fallback evidence | Stay outside both audiences Reason | A recorded guide request independently establishes relevance Evidence for target true | Current explicit statement confirms need Evidence for target false | Current explicit statement contradicts need Unresolved at checkpoint | Target stays excluded; fallback checked separately
The outcomes differ because the required evidence differs. Ownership review is useful if an accepted record can resolve the question. For service location, this hypothetical workflow requires a confirmed service address; a phone number alone does not satisfy that rule.
The fallback is not justified by the absence of need evidence. It is justified by a separate, recorded request for the general guide. That guide must remain general: it cannot present the recipient as having the specified need or qualifying for the restricted offer.
4. Apply fallback eligibility, exit, and overlap rules
A fallback audience needs a complete membership rule, not just a softer name. In the hypothetical example, entry requires an active recorded request for the general service guide, plus the separate channel checks needed before communication.
Define how membership changes as evidence arrives:
- Need becomes true: evaluate the need-specific audience and apply the overlap rule.
- Need becomes false: exclude from the need-specific audience; retain fallback eligibility only if the general-guide request remains valid.
- Guide request is withdrawn: remove fallback membership regardless of whether need remains unknown.
- No guide request exists: keep the contact outside the fallback, rather than interpreting silence as interest.
For this hypothetical campaign, the overlap rule is one communication per preparation cycle: eligible need-specific guidance takes priority over the general guide. That is a chosen operating rule, not a universal requirement. Record the selected audience and reason so priority does not depend on processing order.
Audience relevance is not channel permission. 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. Template approval does not guarantee delivery. Check the current WhatsApp Business Messaging Policy for precise requirements, and maintain a clear human escalation path when using automation.
5. Make review a resolvable task
Review helps when someone can inspect accepted evidence and change the decision. It is less useful when the team has no source to inspect or no action that would resolve uncertainty.
For each review reason, name a responsible role, evidence source, and possible outcomes. In the hypothetical ownership case, a designated reviewer inspects the accepted ownership record. They return true, false, or unknown with a reason. “Reviewed” alone is not an eligibility result.
Distinguish missing evidence from conflicting evidence. A blank ownership field and incompatible ownership records both produce unknown, but require different investigation. Filling a blank may resolve the first; choosing the most convenient conflicting value does not resolve the second.
Set a checkpoint tied to campaign preparation. If uncertainty remains, apply the documented unknown rule. For the ownership example, the contact stays outside the owner audience. A pending task should not quietly become an exception.
Prioritise cases where resolution could change membership and reliable evidence is available. A smaller queue with clear outcomes is more actionable than a large bucket of records nobody can resolve.
6. Test individual records, not just audience totals
Before using a rule, create fictional test records for confirmed positive, confirmed negative, blank, outdated evidence, conflicting evidence, and a value that looks relevant but does not establish the claim.
The last case might be product interest without ownership evidence, or a phone number without the required service address. Check three outputs for every record: condition state, audience assignment, and reason. Correct totals can hide incorrect individual decisions when errors offset one another.
Hypothetical worked run: Contact R has no ownership value, no service address, no evidence of the specified need, and a recorded request for the general guide. Ownership is unknown, so R enters ownership review but not the owner audience. Service-area eligibility is unknown, so R stays outside the restricted offer. Need is unknown, so R stays outside need-specific guidance. The confirmed guide request makes R eligible for the fallback, subject to separate communication checks.
Now remove only the guide request. R remains unknown on the same target conditions, but no longer qualifies for the fallback. This single-change test exposes the central error: missing target evidence must not itself create fallback eligibility.
Also test negative filters, required false conditions, overlap priority, and evidence updates. Confirm that working lists preserve unknown states and reasons. If an implementation accepts only two values, use a separate status or explicit list rather than encoding unknown as false. Check the workspace and current plan before relying on any particular implementation option.
7. Recover from a faulty blank-handling rule
If unknown records were included as confirmed matches, pause use of the affected audience. Preserve the rule version and preparation list where available so the team can identify the affected decisions.
Separate incorrectly included contacts from genuinely eligible ones. Correct the logic, reevaluate membership, and inspect changed records. Check related audiences: the same negative filter may have been copied elsewhere.
Distinguish campaign preparation, template review, and actual delivery. A prepared list or approved template does not show that a recipient received a message. Review available activity records before deciding whether follow-up is appropriate; do not automatically resend to the corrected audience or send everyone a correction.
For the reverse error—unknown contacts incorrectly excluded—apply the revised review or fallback rules individually. Restoring all excluded records would replace an overly restrictive rule with an overly permissive one.
8. Measure whether the written rules produce consistent decisions
Start with one audience where blanks currently change membership unpredictably. Document its claims, accepted evidence, unknown routing, and any independent fallback criteria.
As a hypothetical first check, have two reviewers independently assess 20 records spanning true, false, and unknown states. Compare condition states, membership outcomes, and reasons. A disagreement about evidence calls for a clearer evidence standard; agreement on evidence but disagreement on routing calls for a clearer action rule.
Track unknown share by condition, review outcomes, reviewer disagreements, and unexplained membership changes. These distinguish missing evidence from an ineffective queue or ambiguous instructions; they do not demonstrate campaign performance.
Begin with one sentence: “When this claim is unknown, the contact goes here, because this decision requires this evidence.” If there is a fallback, add its independent entry criterion. Test both statements against a blank record and a conflicting record before using the audience.
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