The preference was recorded
A customer opts out of a marketing message. Weeks later, an AI-assisted campaign selects that customer for outreach. How can this happen if the organization kept the record? This is a hypothetical diagnostic scenario, not an allegation against a particular business.
One customer, many system identities
Marketing environments combine CRM, email delivery, advertising audiences, support interactions, loyalty systems and analytics. Each may represent the customer differently. A preference linked to an email address may not automatically govern another identifier, channel or campaign purpose. Legal permissions can also differ by jurisdiction and communication type.
What has to remain connected
A useful preference record needs the subject of the choice, its source, scope, effective time, later changes, applicable authority and evidence that downstream decisions used the operative state. In the GovKM topology, the customer interaction supplies Source and Evidence; consent and organizational rules establish Authority; identity, channel and purpose supply Context; audience selection is a Decision; sending or suppressing outreach is an Action; send and suppression logs form the Record.
Campaign success does not prove compliance
Open rates and conversions can be strong while recipient eligibility is uncertain. Optimizing one marketing metric does not establish that the authority chain for each communication survived system boundaries. The problem may be identity resolution or inaccessible systems rather than an AI model forgetting a conversation.
Try a continuity diagnostic
Within an approved enterprise environment, use a synthetic test identity to ask the AI to reconstruct the operative preference across relevant channels, identify changes over time and cite the records governing the next proposed outreach. Distinguish a missing preference, a missing identity relationship and an access restriction. Do not enter actual customer personal data into an unapproved AI service. An access failure is NOT TESTABLE, not automatically a continuity failure.
Design for continuity
Do not merely duplicate a yes/no field. Preserve identity mapping, provenance, scope, temporal validity, supersession and evidence connecting current permission to every consequential outreach decision. The AI should be able to explain why outreach was permitted, suppressed or held for review.
Continue with GovKM
Explore GovKM Articles and the GovKM continuity framework. The question is not only what the AI retrieved, but whether it can establish the operative relationship needed for the next decision.
Continue Exploring
The Product Was in Stock. The AI Promised the Wrong Store.
The Promotion Was Real. The AI Could Not Tell When It Ended.
