Consent records

How Landing Zone records consent status and proof, how revocation is captured, and why your own records still matter.

Updated 2 min readMaintained by Landing Zone

When outreach is challenged, the question is rarely "did you have consent?" in the abstract — it is "can you show it?" Landing Zone keeps structured consent records on every contact so your workspace can show what was recorded, when, and from where.

Each contact's SMS and call consent is one of three statuses:

  • UNVERIFIED — no opt-in has been recorded. Imported and skip-traced contacts start here by default.
  • VERIFIED — an opt-in has been recorded, with stored proof: the source, the date, and the details.
  • REVOKED — the contact withdrew consent, also recorded with proof.
  • At import. The CSV import flow includes an opt-in acknowledgment — you confirm you have a lawful basis to contact the recipients — and captures opt-in consent as part of the import. See Import a list.
  • Before sending. Batch and campaign SMS require VERIFIED consent; UNVERIFIED contacts are excluded from SMS eligibility rather than sent to.
  • On revocation. When a contact replies STOP (or revokes in their own words), Landing Zone automatically sets consent to REVOKED, suppresses the number, sends a confirmation reply, and writes an audit entry. See Opt-outs and STOP keywords.

Why your own records also matter

Landing Zone can only witness what happens inside the platform. If consent was gathered on your website, on a signed form, or in a conversation, keep the originals: the exact consent language shown, the timestamp, and the form or document itself. Those artifacts — not a status field — are what establish what a person actually agreed to.

What these records establish

Landing Zone's consent records help you demonstrate process: that a status was recorded, on what date, from what source, and with what details. They do not by themselves establish that the underlying consent was valid for a given message under the rules that apply to you. Whether an opt-in was informed, specific, and sufficient for a particular channel and audience is a judgment the records support but cannot make — see Consent and contact permissions and User responsibilities.