Workflow blueprint

CRM and marketing automation platforms should show why a person entered a campaign

A page-specific review aid, not a universal product or compliance claim.

Use the campaign consent review map to keep contact source, purpose, segment, campaign event, opt-out and follow-up ownership connected for a Mauritius evidence review.

TL;DR — Use the campaign consent review map to keep contact source, purpose, segment, campaign event, opt-out and follow-up ownership connected for a Mauritius evidence review.
1

Frame the case

Record contact source, purpose, preference, timestamp and owner.

2

Trace the evidence

Relate segment rule, campaign edition, trigger, exclusion and test message.

3

Review the exception

Capture send, bounce, unsubscribe, complaint and follow-up response.

4

Assign the next owner

Assign privacy, consent, security, content, sales and vendor owners.

Page-specific decision aid

Campaign consent review map

A contact source, purpose, consent or preference record, segment, campaign event, opt-out and follow-up owner.

  • A contact record is not consent proof
  • Automation keeps its purpose
  • Opt-out is an explicit event
Scope first

What Codeblix would confirm before implementation

This page is an operational blueprint. The final workflow, screens, permissions and integrations depend on your current process and agreed implementation scope.

  • Contact and source identity
  • Purpose or preference record
  • Campaign and event history
  • Privacy reviewer

Map this workflow to your operation

Tell Codeblix how work moves today. We will confirm the practical scope before proposing an implementation.

Discuss your workflow