A Consent Field Needs Provenance, Not Just a Yes Value
Review the source, scope, wording, and history behind consent fields before lead records enter downstream outreach.
A column named consent=true looks precise until someone asks what was agreed to, when, and for which sender. For operations teams, the real design job is provenance: preserve the source and scope of a choice while the record moves between intake, CRM, and reporting.
Model the choice as an event
Consider fields for the entry point, displayed wording or script version, event time, channel, purpose, and the customer’s answer. Record later opt-outs as new events rather than silently overwriting history. Keep access to the underlying evidence appropriately limited; a dashboard flag alone is not the evidence.
Test downstream meanings
Ask each team what it means when a field is blank, unknown, opted out, or limited to a requested service reply. Map those states explicitly before export. A data pipeline that collapses unknown into yes creates a decision the customer never made.
Work through one case
Illustrative: An import contains sms_allowed=yes but no sender, wording, source, or event time. Preserve the imported value as source data, flag permission for review, and keep it out of an approved promotional audience until the basis is established. A later stop event should update the usable status while preserving the relevant history.
This is a proposed evidence model, not a statutory field list or retention schedule. Consent and contact preferences can have different legal meanings; keep them distinguishable and set access and retention rules for the actual program.
Apply the questions to this example
Illustrative worked example: These sample notes extend the case above. Roles and record locations are proposed for the example, not descriptions of a customer or this brand’s configured service. Adapt them to your own process.
| Step | Question | Sample evidence, owner, and next action |
|---|---|---|
| 1 | What exact choice was presented? | Import says sms_allowed=yes, but the original question is missing; data owner flags the basis as unestablished. |
| 2 | Where is the source event retained? | Original import row retained as source data; evidence owner seeks the missing wording and event record. |
| 3 | Which destination can change or suppress the status? | Audience owner: exclude the unresolved record from approved promotional sends and verify later stop events reach downstream lists. |
Put the next step in writing
Use the field-mapping handoff questions to assign an owner for each value and its meaning. Design the record for review, not just for filling a schema.
These fields describe a proposed evidence model, not a legally complete schema. Set retention, access, and sending rules for the real program rather than treating a populated record as legal approval.
Further reading: FCC call and text guidance · FTC telemarketing resources.
Contact Lead Data Warehouse to discuss the inbound workflow described on this site.