Consent
Explicit affirmative consent statement including message examples, expected frequency, and carrier or message/data rate disclosure where required. The consent must be easily understood and presented before capturing opt-in.
Use a Marketing SMS Line Form to document express consent, reduce TCPA exposure, and standardize campaign settings across channels. A clear, executed form helps auditors verify consent, supports compliant opt-out handling, and creates a record that satisfies ESIGN/UETA requirements for electronic execution.
Marketers, CRM teams, compliance officers, and messaging vendors use the Marketing SMS Line Form to capture consent and technical details for campaigns.
Use role-based ownership to ensure the form is completed, stored, and reviewed before any SMS campaign activation.
Explicit affirmative consent statement including message examples, expected frequency, and carrier or message/data rate disclosure where required. The consent must be easily understood and presented before capturing opt-in.
Technical line information such as number type (short code, long code, toll-free), provider, campaign ID, and provisioning windows. These details help carriers and internal ops manage throughput and routing.
Clear, simple opt-out instructions and handling procedures; include suppression list processes and timelines. Documenting opt-out mechanics reduces carrier disputes and legal exposure and aids audits.
Identify who has authority to sign on behalf of the sender, include title and contact information, and require signatory affirmation of compliance with TCPA and company policies.
Record timestamps, IP addresses, authentication method, and evidence of consent. Maintain an exportable audit trail suitable for regulatory or carrier review and include user-agent and device metadata.
State retention period for forms and associated logs, reference regulatory bases, and explain procedures for secure archiving and disposal after retention ends and legal hold processes if litigation occurs.
| Field | Configuration settings and implementation notes |
|---|---|
| Authentication | Email verification, SMS code, or knowledge-based authentication (KBA) methods. |
| Signature Method | Allow guest typed signature, drawn mobile signature, or PKI digital certificate. |
| File Format | Accept PDF/A, standard PDF, and DOCX uploads for auditability. |
| Integrations | Map submission to CRM, ESP, or carrier portals for automation and logging. |
| Retention Flag | Mark documents with retention policy, legal hold, and export schedule. |