Audit trail

Request consent evidence packets.

Need documentation proving a workflow, campaign, invoice, or notification was authorized? This guide explains exactly what to submit, what we return, and how long delivery takes.

When to request a consent packet

Consent packets bundle approvals, metadata, and related delivery evidence tied to a defined event scope. Common use cases include:

  • Audits and certifications: SOC 2, ISO, vendor diligence, or customer review requiring approval traceability.
  • Billing disputes: Verification that a seat upgrade, add-on, or invoice-linked change was explicitly authorized.
  • Regulatory or legal inquiries: Responses for privacy, consumer protection, or telecom compliance requests.
  • Internal investigations: Confirmation of who approved, changed, or launched a workflow or campaign.
  • Provider escalations: Carrier or platform inquiries involving opt-in, opt-out, and communication authorization history.

Required information at submission

Complete input reduces turnaround time and avoids rework.

  • Workspace identifier: Account email and/or workspace slug, plus the approving admin name if known.
  • Scope target: Workflow ID, campaign ID, invoice number, document link, or event reference tied to the consent record.
  • Date range: Approximate approval window in UTC (or local timezone with offset).
  • Packet format: Signed PDF summary, JSON bundle, CSV extract, or a combined package.
  • Request purpose: Audit, dispute, regulator response, or internal investigation.
  • Urgency level: Standard or urgent, with justification for expedited handling.

Submission channels

You can submit requests through:

  • Account dashboard: Preferred for authenticated owners/admins.
  • Email: Send to [email protected] with subject line "Consent Packet".
  • Operator escalation: For active managed engagements, your operator can initiate a tracked request on your behalf.

Each accepted request receives a tracking ID for status checks and future reference.

Processing workflow

All requests follow a standardized process to ensure consistency:

  1. Identity verification. We verify requester authority using account auth plus a secondary method for high-risk scopes.
  2. Scope confirmation. We validate workspace, event targets, date range, and output format requirements.
  3. Evidence collection. We gather approval events, consent records, auth logs, and workflow/campaign metadata tied to the scope.
  4. Quality review and redaction. We validate completeness and apply legally required redactions.
  5. Packaging and signing. We deliver a digitally signed packet in the requested formats.

What the packet can include

Depending on scope, packet contents may include:

  • Approval timestamps and actor identity
  • Approval channel (dashboard, email, API callback, integration event)
  • IP address and user-agent metadata where available
  • Role/permission state at time of approval
  • Workflow snapshot references and execution context
  • Billing authorization references (if requested)
  • Consent and opt-out history for communication workflows (if requested and authorized)

Timelines and service levels

Acknowledgement: Within 1 business day.

Standard delivery: Typically within 3 business days.

Complex delivery: Multi-workspace, regulator-bound, or broad historical pulls may take up to 7 business days or longer with status updates.

Urgent requests: Prioritized where feasible based on risk and legal deadlines.

Limitations and rejection scenarios

  • Insufficient authority: We cannot release consent evidence without verified ownership or documented authorization.
  • Overbroad requests: We may require narrower scope to process safely and accurately.
  • Legal restrictions: Some records may be partially withheld or redacted where disclosure is limited by law.
  • Retention boundaries: Records outside retention windows may no longer be recoverable except for preserved legal-hold datasets.

Follow-up and escalation

For status updates, reply to your request thread and reference the tracking ID. For escalations, include deadline context and business impact so we can triage appropriately.

Related governance documents: Proof of Consent, Data Retention, Privacy Policy, and Terms of Service.

Contact

Need a rush turnaround or clarification on a delivered packet? Email [email protected] with subject line "Consent Packet Request" and include workspace email, scope target, and tracking ID (if available).