Back to all articlesAudience segmentation

Make customer-status audiences mutually understandable

Alactic Editorial10 min read

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

A person can be a current customer of your business, a prospect for a different product, and a returning buyer at the same time. Those labels are not necessarily wrong. They become a problem when teams treat them as answers to the same question.

To define customer-status audiences clearly, separate three things: the commercial facts that establish a relationship, the account or product being evaluated, and whether the label describes current status or purchase history. Make statuses exclusive only within a defined scope and date. Keep historical facts and buying events available alongside that status.

The practical result is not one perfect definition of customer. It is a shared decision rule that lets two colleagues classify the same record the same way—and understand why a record belongs to more than one audience.

1. Fix the unit before fixing the labels

Start every status definition with a sentence identifying what is being classified. An account, a contact, and an account’s relationship with a product are different units.

  • Account-level status: Does this commercial account have a qualifying relationship with the business?
  • Product-level status: Does this account have a qualifying relationship with this particular product?
  • Contact association: Is this person associated with an account that has that status?

A contact employed by a customer account has not necessarily purchased personally. Likewise, a billing contact and a product user may belong to the same account without having the same communication needs. Do not copy an account’s customer label onto every contact and then interpret it as evidence of individual buying activity.

Choose the account boundary explicitly. A parent business and its subsidiaries might be separate commercial accounts or one consolidated account. Neither approach is universally correct, but switching between them silently changes audience membership.

Use scope-bearing names where ambiguity is likely. account_relationship_status and product_relationship_status are clearer than two fields both called status. A product-status record also needs a product identifier; otherwise, “prospect” has no stable meaning.

2. Define the commercial facts that count

A status should be derived from agreed evidence, not from whichever team last edited a label. Define a qualifying purchase and a current relationship separately.

A qualifying purchase might be a completed, non-cancelled transaction. A current relationship might mean an active service entitlement. In a business selling occasional goods, current customer could instead mean a qualifying purchase within a stated recency period. These are design choices, not interchangeable facts.

Write down the following before building audiences:

  • Qualification event: What makes a first purchase count—payment, fulfilment, activation, or another recorded event?
  • Cancellation treatment: Does a cancelled order fail to qualify? What happens if the qualifying event was recorded before cancellation?
  • Currentness rule: Is the relationship current because of an active entitlement, a recent purchase, or another explicit condition?
  • Evaluation date: At what point in time is the status being calculated?
  • Evidence source: Which record establishes the event and its effective date?

Do not let an order-created event substitute for a completed purchase unless that is deliberately your definition. Otherwise, an abandoned or cancelled first order can create a customer history that never actually occurred.

For one-off transactions, avoid implying that “former customer” proves the person has left permanently. It may only mean they have purchased before but do not meet your chosen currentness rule. If that distinction matters, use the more literal label “past purchaser, not current.”

3. Separate current state from history and returning behaviour

A workable design uses a small exclusive relationship state plus separate historical facts. The following is a recommended starting model, not a universal taxonomy:

  • No established purchase: Reliable available evidence shows no qualifying purchase in the defined scope.
  • Current customer: The account meets the current-relationship rule in that scope.
  • Former customer: There is a qualifying purchase in that scope, but the current-relationship rule is not met.
  • Unknown: The evidence is missing, conflicting, or insufficient to apply the rule.

Keep has_ever_purchased and has_recorded_enquiry separate. A prospect audience can then mean “has an enquiry and no qualifying purchase” rather than every record that is not currently a customer. An imported contact with no commercial history should not automatically become an enquiry-based prospect.

“Returning customer” needs another decision. It can mean a repeat buyer, or it can mean someone purchasing after a period without a current relationship. Those meanings produce different audiences.

Prefer explicit definitions such as “made a subsequent qualifying purchase” and “re-established a relationship after a gap.” Specify the gap if it matters. A customer buying a second product while their first remains active is a repeat account buyer, but not necessarily a reactivated customer.

Historical facts should not disappear when current status changes. A former customer who buys again becomes current, while retaining their earlier purchase history. A current customer considering another product remains current at account level while potentially being a prospect for that product.

4. Filled hypothetical status decision table

Fictional worked example: The following accounts, products, dates, and rules are hypothetical. They illustrate a service business evaluating audiences on 30 June. A qualifying purchase requires completed activation and must not be cancelled before activation. A current customer has an active entitlement on the evaluation date. Account-level currentness requires at least one active product entitlement.

In this example, a prospect audience requires a recorded enquiry and no qualifying purchase in the relevant scope. A repeat-buyer flag becomes true after a subsequent qualifying purchase. It does not become true merely because another order was placed.

The compact decision table is followed by the evidence behind each row. “None” means no enquiry-based prospect audience under these rules, not a missing relationship state.

Account | Scope       | Relationship state       | Prospect audience | Ever bought | Repeat buyer
Alder   | Account     | No established purchase  | Yes               | No          | No
Alder   | Product A   | No established purchase  | Yes               | No          | No
Birch   | Account     | Former customer          | No                | Yes         | No
Birch   | Product A   | Former customer          | No                | Yes         | No
Cedar   | Account     | Current customer         | No                | Yes         | Yes
Cedar   | Product A   | Current customer         | No                | Yes         | No
Cedar   | Product B   | Current customer         | No                | Yes         | No
Dune    | Account     | No established purchase  | Yes               | No          | No
Dune    | Product A   | No established purchase  | Yes               | No          | No

Alder: an enquiry without a purchase

Alder enquired about Product A on 12 June. No qualifying purchase exists. Both account-level and Product A relationship states are “no established purchase,” and Alder belongs to both enquiry-based prospect audiences. Product B has no recorded enquiry, so Alder does not belong to the Product B prospect audience.

Birch: a completed past purchase

Birch activated Product A on 5 February. Its entitlement ended on 31 May, and it has no other active entitlement. Birch is a former customer at both account and Product A levels. Its purchase history remains true. Lack of an active entitlement does not turn Birch into a never-purchased prospect.

Cedar: a current customer buying another product

Cedar already has an active Product A entitlement. It enquired about Product B on 10 June and completed Product B activation on 25 June. On 24 June, Cedar was a current account customer and a Product B prospect. On 30 June, it is current at both account and Product B levels.

The Product B purchase makes Cedar a repeat buyer at account level, because an earlier qualifying account purchase exists. It is not yet a repeat buyer of either individual product. Nothing in this example establishes a return after a relationship gap.

Dune: a cancelled first order

Dune enquired about Product A and placed its first order on 18 June, then cancelled on 19 June before activation. The order does not qualify as a purchase. Dune remains in the enquiry-based prospect audience at account and Product A levels, with no purchase history. Cancellation is evidence about the order, not evidence that Dune is a former customer.

If Dune had no recorded enquiry, its relationship state would still be “no established purchase,” but it would not enter this particular prospect audience.

5. Choose exclusivity only where it answers a real question

Use exclusive states when a list or report requires one relationship answer per account, scope, and evaluation date. Under the example rules, an account cannot simultaneously be current and former at account level on the same date.

Use overlapping audiences when they describe different dimensions. “Current account customer” and “Product B prospect” can legitimately overlap. So can “current customer” and “repeat buyer.” Forcing these into one dropdown destroys useful information.

For exclusive relationship states, make the precedence explicit:

  1. Check whether the available evidence can support a classification. If not, use unknown.
  2. If the current-relationship rule is met, classify as current.
  3. Otherwise, if a qualifying purchase exists, classify as former.
  4. Otherwise, classify as no established purchase.

Campaign audiences may need a second kind of exclusivity: preventing one account from receiving conflicting messages. Keep that decision outside the relationship definition. A campaign can prioritise one eligible audience without pretending the other relationship facts are false.

This separation has a trade-off. More explicit fields require more documentation than one customer dropdown. In return, teams can explain overlap instead of repeatedly correcting it by hand.

6. Recover from missing history and contradictory records

The most dangerous shortcut is treating missing evidence as proof that something never happened. A new CRM record may represent a long-standing customer whose older purchases were not imported.

Use unknown when the classification depends on history you do not have. Record the evidence gap separately, such as an incomplete migration or an unresolved account match. Do not quietly place those records into a never-purchased audience.

When facts conflict, repair the source relationship before editing the audience label:

  • A cancelled first order shows customer status: Check whether order creation incorrectly triggered qualification. Remove the invalid qualification and recompute affected audiences.
  • A current entitlement belongs to a duplicate account: Resolve the account mapping, then recalculate account and product states from the combined evidence.
  • A purchase arrived late: Preserve its effective date separately from the date it was recorded. Rebuild the relevant status view if historical accuracy is needed.
  • A former customer is marked prospect after a new enquiry: Keep the enquiry fact, but do not erase established purchase history.

Keep a short change record for definition updates. If “current” changes from active entitlement to recent purchase, that is a new rule—not evidence that every affected customer changed behaviour overnight. Compare audiences before and after the change and explain the membership differences.

7. Keep relationship status separate from communication eligibility

Being a customer does not by itself establish permission to send a message. Maintain communication eligibility separately from customer status so that an opt-out does not rewrite commercial history, and a commercial relationship does not override an opt-out.

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. Check the current WhatsApp Business Messaging Policy for precise requirements.

Operationally, treat status membership as one input to audience selection—not the final send decision. A current-customer audience may contain records that are not eligible for a particular communication. Preserve that distinction rather than changing their customer status to make a campaign list look cleaner.

8. Test the definitions with a small, observable review

Before applying new labels broadly, ask two colleagues to classify the same sample independently using only the written rules and underlying facts. Include the four cases above, incomplete histories, multiple products, and duplicate accounts.

A practical next action is a hypothetical review of 20 records. For each record, capture the account scope, product scope, evaluation date, qualifying-purchase evidence, currentness evidence, resulting state, and unresolved question.

Measure three things:

  • Agreement: How many records receive the same classification from both reviewers?
  • Evidence gaps: How many cannot be classified without assumptions?
  • Contradictions: How many violate the intended exclusive-state rules within the same scope and date?

Resolve each disagreement by changing either the evidence or the definition, not by asking reviewers to guess the intended answer. Repeat the exercise after revisions. The useful outcome is an audience whose membership can be explained from recorded facts—including why a current account customer can still be a prospect for another product.

Audience segmentationCRMCustomer statusData quality

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