Record the permission context
Bring source, notice, purpose and relevant preference information together with the customer record. Keep business hierarchy and purpose definitions understandable to the people operating the programme.
Connect preferences, purpose and communication eligibility.
24 seconds · Silent film with on-screen captions · Workflow illustration.
A customer choice should travel.
Explain the purpose → Record the choice → Carry updates forward → Review the evidence. Connect the purpose, preference and later changes to the audience or workflow that uses the record.
A customer choice should travel. Explore the infographic below the film for the full workflow.
Connect the purpose, preference and later changes to the audience or workflow that uses the record.. Connect the question, the evidence and the next useful action.
Connect the purpose, preference and later changes to the audience or workflow that uses the record.
Bring source, notice, purpose and relevant preference information together with the customer record. Keep business hierarchy and purpose definitions understandable to the people operating the programme.
Plan how preferences are collected, changed and withdrawn across the channels in scope. Define how those updates reach campaign preparation and other connected workflows.
Agree the audit evidence, legacy migration treatment, access roles and escalation responsibilities. Review the implementation with the responsible business and legal teams.
ConsentFirst should be assessed against the organisation’s actual data flows and applicable requirements. Ask for a specific walkthrough of acquisition, preferences, withdrawals, audit records and integrations. Product use alone does not establish legal compliance.
Bring a business question. Let’s connect the people, the data and the workflow.
Hi 👋 I'm Abhinav
Got a loyalty or ADSR question?