Consent evidence research
Are callback-consent records complete enough to support follow-up?
A documentary study of whether call records show who agreed to follow-up, through which channel, for what purpose, and for how long.
Research question
Do call records contain enough evidence to support the follow-up that staff actually make? A useful review asks whether the record identifies the person, contact channel, stated purpose, capture time, applicable duration, and any later withdrawal. It does not assume that one general permission authorizes every future campaign.
The FTC's National Do Not Call Registry guidance for businesses describes federal telemarketing responsibilities. The FCC's consumer guide to unwanted calls and texts explains consumer protections at a high level. Neither page is a substitute for legal review of a particular message, jurisdiction, or business relationship.
Documentary sample
Select a defined period of inbound records followed by an outbound callback, text, or email. For each record, code whether the person and channel match, whether the purpose was stated, whether the permission has a timestamp, and whether a withdrawal appeared before follow-up. Preserve the exact policy version that staff were expected to use.
Reviewers should use a written codebook. Categories might include complete for the observed follow-up, incomplete, conflicting, withdrawn, outside the stated purpose, and not enough evidence. A second reviewer should examine every conflict and a random sample of other classifications.
Compare record to action
A complete intake field does not prove that the later action stayed within scope. Link each permission record to the actual channel, timing, and purpose of follow-up. Conversely, a blank consent field does not by itself prove that no valid permission existed; evidence may sit in a contract or another approved system.
Report missing evidence separately from confirmed mismatches. The NIST Privacy Framework provides a structure for identifying and managing privacy risk. It does not decide whether a particular callback has legal consent.
Operational findings
Group defects by where they entered the process: script wording, assistant capture, system field, data transfer, suppression check, or later agent action. That split helps the business choose a correction. Repeating the consent script will not repair a CRM integration that drops the timestamp.
Avoid ranking individual assistants when the system itself makes a field optional or hides withdrawal information. The unit of analysis should remain the record-to-action path unless the study was designed and reviewed for individual performance assessment.
Limitations
Records can be incomplete even when the caller understood the request, and a fully populated form can misstate the conversation. Transcripts may contain recognition errors. Legal duties vary by channel, purpose, relationship, and location. Sampling only successful contacts will omit attempts stopped by suppression controls.
The study measures documentary completeness and consistency with a stated policy. It cannot determine legal compliance, caller understanding, or whether permission was freely given without separate legal and qualitative analysis.