Waivers

Beta

Collect signed liability releases and agreements from prospects before their conversations begin.


Overview

Waivers let you require prospects to sign a liability release or agreement before chatting with an advocate. This is useful for communities that coordinate in-person activities — like test rides, demos, or tours — where a signed release is needed before participation.

Each waiver template includes customizable content, optional fields for collecting additional information (like emergency contacts or driver’s license numbers), and merge variables for personalization. Signed waivers are stored as immutable legal records with audit trail details including IP address, timestamp, and the exact agreement the prospect saw.


Creating a Waiver Template

  1. Go to Settings > Waivers
  2. Click Add Waiver Template
  3. Fill in the fields:
    • Title — A descriptive name (e.g., “Liability Waiver”, “Activity Release Form”)
    • Description — Optional introductory text shown to the prospect before they fill in the form
    • Agreement — The full waiver text. Supports merge variables for personalization.
  4. Add any custom fields you need (see below)
  5. Click Create

New templates start in Draft status. You’ll need to publish them before prospects can sign.


Custom Fields

Waiver templates can include custom fields to collect additional information from the prospect before signing. Each field becomes part of the signed record.

To add a field, click Add Field on the template edit page and configure:

  • Label — The field name shown to the prospect (e.g., “Driver’s License Number”)
  • Field Type — Choose from:
    • Short Text — Single-line text input
    • Long Text — Multi-line textarea
    • Select — Dropdown with predefined options
  • Required — Whether the prospect must fill in this field before signing
  • Helper Text — Optional guidance shown below the field
  • Placeholder Text — Optional hint shown inside the field

Field values are automatically available as merge variables in the agreement text using the pattern {{ waiver_field_<identifier> }}. For example, a field labeled “Emergency Contact Phone” with identifier emergency_contact_phone would use {{ waiver_field_emergency_contact_phone }}.


Merge Variables

Use double curly braces to insert dynamic content into the waiver agreement. These are replaced with real values when the prospect reviews the agreement before signing.

Variable Description
{{ prospect_first_name }} Prospect’s first name
{{ prospect_public_name }} Prospect’s public display name
{{ advocate_first_name }} Advocate’s first name
{{ advocate_profile_display_name }} Advocate’s display name
{{ community_name }} Community name
{{ community_brand_name }} Community brand name
{{ waiver_field_<identifier> }} Value of a custom field

Wrap merge variable examples in your agreement text with Liquid raw tags if you’re referencing them literally. In normal use, just type the variable and it will be resolved automatically.


Publishing & Versioning

Waiver templates follow a Draft → Active lifecycle:

  1. Draft — New or edited templates start here. Drafts are not visible to prospects.
  2. Active — Published templates are sent to prospects for signing.
  3. Archived — Replaced templates are archived when a new version is published.

To publish a draft, click Publish on the template page. If there’s already an active version, it will be archived automatically and the new version takes its place.

Signed waivers are tied to the exact template version the prospect saw. Editing and republishing a waiver creates a new version — existing signatures remain attached to the version that was signed.

Admin Preview

Before publishing, you can preview how the waiver will look to prospects. Click Preview on the template page to walk through the signing experience with sample data.


The Prospect Signing Experience

When a prospect starts a conversation with a community that requires waivers, they receive a signing link. The signing process has two steps:

Step 1: Provide Information

The prospect fills in:

  • Legal Name (required) — used as their typed signature
  • Email Address (optional)
  • Any custom fields defined on the template

Step 2: Review & Sign

The prospect sees the fully rendered waiver agreement with all merge variables and field values filled in. They must:

  1. Review the complete agreement
  2. Check the certification box confirming they’ve read and agree to the terms
  3. Confirm their typed signature
  4. Click Sign Agreement

Once signed, the waiver is locked as an immutable legal record. A confirmation message is automatically posted to the conversation.


Automatic Conversation Activation

When a community has active waivers, pending conversations wait for all required waivers to be signed before activating. The signing link is included in the conversation flow, so prospects receive it automatically.

Once all required waivers are signed, the conversation activates and both parties are notified.


Limits

The number of waiver templates available depends on your community’s plan:

Plan Waiver Templates
Basic Not available
Pro 1
Enterprise 5

© 2025-2026 Stoked — Real conversations. Real trust.