Translate service coverage into audience eligibility
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A contact’s billing address falls inside your service area, so the contact enters a campaign for an on-site service. The problem appears later: the work site is outside coverage, or the promoted service is not offered there. The audience rule worked as written; it used the wrong facts.
Base coverage eligibility on the specific service site, the requested or promoted service, and a current coverage decision for that combination. Keep billing location separate. Use three coverage states—supported, unsupported and uncertain—and include only supported combinations in a service-specific audience. Recipient permission and other messaging requirements remain separate checks.
The essential change is the unit of decision. A business is not necessarily eligible everywhere it operates. A contact is not necessarily eligible for every service available somewhere on their account.
1. Define the offer before building the audience
Write a plain-language description of what the audience will receive. A hypothetical example is: “An invitation to request equipment installation at a confirmed site within our current installation coverage.” That sentence identifies the service, the location that matters and the evidence needed.
A rule such as “account region equals covered region” does not establish those facts. It may refer to headquarters, a billing office, an old address or a broad sales classification. Even an accurate regional value may be too coarse when coverage includes only part of that region.
Define the coverage decision first:
Coverage decision = service site + service + applicable coverage rule
Then define audience inclusion separately:
Include = supported coverage + relevant contact-to-site relationship + messaging eligibility
This prevents “we can serve this site” from becoming permission to message everyone associated with the account. It also prevents a permitted contact from being treated as serviceable simply because they can receive messages.
2. Keep billing, service and coverage facts distinct
You do not need a large data model to start, but you do need fields with clear meanings. The following is a recommended record design, not a claim that a particular product provides these controls.
- Billing address: where invoices or account correspondence belong, not a substitute for the work location.
- Service-site identifier and address: where the offered work would happen. A stable identifier distinguishes sites with similar names.
- Requested or promoted service: the service being evaluated. Keep installation and inspection distinct if their coverage differs.
- Coverage state: supported, unsupported or uncertain for that site-service combination.
- Decision basis: the coverage rule or operational confirmation supporting the result.
- Checked date and rule version: context for deciding whether the result remains current.
- Contact-to-site relationship: which sites the recipient represents for this offer.
Do not fill a missing service-site address with the billing address merely to complete the record. Leave the site unresolved until someone confirms whether those addresses are the same. Likewise, general interest in services does not identify a particular service.
Use a confirmed service-site address rather than inferring coverage from a phone number. A communication field should not become the deciding evidence for where work will occur.
If you implement this design using Alactic, keep CRM record needs separate from WhatsApp business communication needs. Check the workspace and current plan for availability rather than assuming a field, filter or review step exists across products or interfaces.
3. Work through a filled coverage decision table
Fictional worked example: All businesses, places, identifiers and rules below are hypothetical, not Alactic customer results. Suppose a provider offers installation and inspection. Under its hypothetical rule C-12, installation is supported in Northbank but not Southbank. Inspection is supported in both areas. A maintained coverage register resolves each confirmed site to the applicable area.
Harbor Foods has a Northbank billing office and operating sites on both sides of the installation boundary. Its central facilities contact represents both sites. The table is a reusable review artifact: retain its columns, replace the fictional entries with verified records, and record the applicable rule and check date alongside it.
| Row | Business / billing address | Service site | Requested service | Confirmed coverage | Audience decision |
|---|---|---|---|---|---|
| A | Harbor Foods / Northbank | H-N: Northbank depot | Installation | Supported under C-12 | Include H-N installation only |
| B | Harbor Foods / Northbank | H-S: Southbank depot | Installation | Unsupported under C-12 | Exclude H-S installation |
| C | Harbor Foods / Northbank | H-S: Southbank depot | Inspection | Supported under C-12 | Include H-S inspection only |
| D | Vale Workshop / Southbank | V-N: Northbank workshop | Installation | Supported under C-12 | Include V-N installation |
| E | Field Supply / Northbank | F-X: site not confirmed | Installation | Uncertain: missing site | Hold for site confirmation |
| F | Cedar Stores / Northbank | C-N: Northbank store | Service not specified | Uncertain: missing service | Hold for service clarification |
| G | Ridge Works / Northbank | R-E: boundary-edge yard | Installation | Uncertain: site unresolved | Hold for coverage review |
For an installation offer, rows A and D pass the coverage test. Row B fails. Row C is supported for inspection, not installation, so it does not qualify for this offer. Rows E, F and G remain on hold. Contact relationships and messaging eligibility still need checking before any recipient is included.
This exposes both billing-address errors: Harbor Foods has an unsupported installation site despite billing inside coverage, while Vale Workshop has a supported site despite billing outside it. It also shows why uncertain records need their own state rather than being permanently labelled unsupported.
4. Require a positive match on the same site-service pair
Use the table as a specification before implementing filters. A service-specific audience should require positive evidence, not merely exclude records already known to be outside coverage.
- Select the service. Evaluate installation coverage for an installation offer, not a generic account eligibility flag.
- Require a confirmed site. If several sites are possible and the intended one is unknown, hold the record.
- Check the matching decision. Require supported coverage for that same site and service under the applicable rule.
- Verify the recipient’s relationship. Confirm that the contact represents the qualifying site or has a documented central role covering it.
- Apply messaging checks separately. Do not infer permission or opt-out status from coverage.
Keep this rule description beside the implemented audience: “Include contacts representing a confirmed site with supported installation coverage under the applicable rule; exclude unsupported combinations and hold uncertain combinations.” A reviewer can then compare intent with the actual results.
Avoid “coverage is not unsupported.” Missing values and unresolved records can slip through that wording. Also avoid matching a supported location on one site with a requested service on another. Every required fact must belong to the same site-service decision.
5. Preserve site context when contacts represent several locations
Harbor Foods’ central facilities contact may qualify for the installation audience because H-N is supported. That does not make H-S installation-eligible. Preserve the qualifying site in the review record and in the context used to prepare the communication.
A hypothetical message could refer to installation availability for the Northbank depot. Saying “installation is available at all your locations” would contradict the decision. If the preparation process cannot retain site context, narrow the audience or resolve that limitation before using it.
Keeping one decision row per site-service pair makes review easier, but sending once per row could create repetitive contact. Separate the evidence from the communication choice:
- Consolidate eligible sites into one communication when their meaning can be preserved accurately.
- Identify one site clearly when the offer concerns only that site.
- Hold a record if deduplication would erase which site qualifies.
Do not solve duplication by replacing detailed decisions with “account eligible.” That removes the evidence needed to limit the offer. Review the deduplicated recipient list as well as the underlying decision rows; errors can enter after coverage filtering is complete.
6. Give uncertain records a specific next action
An uncertain state is useful only if someone can resolve it. Assign a reason and an owner. Missing site information may require confirmation from the account contact; a boundary-edge location may need review by the person maintaining the coverage register. These are recommended responsibilities, not automatic actions.
Ask the smallest question that resolves the decision. Field Supply needs to identify the installation site. Cedar Stores needs to identify the service. Ridge Works already has a site and service; it needs a coverage determination. Sending all three the same broad questionnaire would add unnecessary work.
Keep unresolved records out of audiences that imply availability. If a separate clarification communication is appropriate and permitted, frame it as information gathering rather than a supported-service offer.
Holding records reduces immediate audience size and creates review work. Including them transfers unresolved questions to the recipient and service team. Track hold reasons, ownership and resolution outcomes so caution does not become indefinite neglect. A resolved hold should return to the full inclusion check, not bypass contact or messaging checks.
7. Recheck changed facts and separate messaging states
A supported result is not permanent. Site moves, service changes and coverage revisions can invalidate it. Choose a review cadence suited to how coverage changes, and recheck affected decisions before preparing another audience. Retain enough history to explain the previous and current result.
If installation coverage changes, reassess affected installation combinations rather than overwriting inspection decisions or every site on the account. If an unsupported site enters an audience, pause further use while you identify the cause. Check for billing-address substitution, missing service details, an outdated rule or a match across different sites. Correct the rule, rebuild the audience and review affected records. A corrected filter does not change a communication already delivered.
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 campaign preparation, template review and actual delivery as separate states. Coverage qualification is not template approval, and template approval does not guarantee delivery. If automation assists the workflow, require appropriate authorisation for actions and provide a clear path to a human.
8. Pilot the rule against deliberate failure cases
Start with one service and a manageable set of records. Adapt the filled table, then compare the proposed audience with a manual review of the actual site-service evidence.
Include an in-area billing address with an unsupported site, an out-of-area billing address with a supported site, a multi-site business, a missing service and a boundary requiring review. Test the cross-site matching failure too: one site has the right location while another has the requested service. The same pair must satisfy the rule.
Record observable outcomes:
- Unsupported inclusions: entries whose relevant site-service combination is not supported.
- Uncertain inclusions: entries lacking enough evidence for a supported decision.
- Supported omissions: confirmed qualifying combinations incorrectly excluded by coverage filtering.
- Hold resolutions: missing facts supplied, decisions reached and records still awaiting review.
- Context loss: recipients whose qualifying site disappears during deduplication or preparation.
Review every included site-service combination in the pilot and resolve unsupported or uncertain inclusions before using the audience. Keep the decision table with the rule so the next reviewer can establish which site qualified, for which service, and why.
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