Skip to content
English
More support Sign in
Go to patchretention.com
  • There are no suggestions because the search field is empty.

Waiver Signed Trigger Block

The Waiver Signed trigger starts an automation when a contact completes a waiver. This is ideal for pre-visit instructions, safety messaging, access details, and post-waiver follow-ups.

What’s in This Article

 

 

What This Trigger Does

The Waiver Signed trigger fires when:

  1. A contact signs/completes a waiver

  2. Patch records the waiver completion

  3. Patch sends the waiver event + contact information into the automation

In simple terms:
“Run this automation when someone signs a waiver.”

 

 

When to Use This Trigger

Use Waiver Signed when you want to:

  • Send a waiver confirmation + what to do next

  • Share arrival instructions (what to bring, when to arrive)

  • Send safety guidelines or rules (laser tag, trampoline, adventure sports)

  • Route special waivers (minors, group events, VIP)

  • Start a post-visit follow-up flow if waiver completion signals intent

 

 

When Not to Use This Trigger

Don’t use this trigger if your workflow should start from the visit or purchase itself:

  • Check-In Finished → the visit happened

  • Order Finished → payment/revenue happened

  • Calendar Event → scheduled appointment reminders

  • Form Finished → lead capture workflows

 

 

Block Settings Explained

Details (Info Panel)

This section explains how the block is triggered. It’s informational only.

Add Conditions

Use Add Conditions to limit which waiver events trigger the automation.

Common filters:

  • Waiver (specific waiver template/type)

  • Kiosk Device (where the waiver was signed)

  • Kiosk Flow (which kiosk flow was used)

  • Time (day/time rules)

  • Contact Fields for segmentation
Tips

  • If you use multiple waiver types (example: “General” vs “Membership” vs “Party”), filter by Waiver so messaging matches.

Configure Trigger Frequency

This section controls how often the Waiver Signed trigger can start the automation for the same contact.

Run this trigger…

Choose how often the automation should run after counting waiver completions that match your conditions.

Common options include:

  • One time at a certain number of waivers
    Use this when you only want the automation to run once (example: only the first time someone signs a waiver).

  • Every X waivers
    Use this when you want the automation to run repeatedly (example: every waiver signed, or every 2nd waiver).

Number of waivers

How many waiver completions must happen before the trigger runs.

  • Example: 1 = run every time a waiver is signed

  • Example: 2 = run on every 2nd waiver signed

Starting with waiver

Controls which waiver number starts the counting.

  • Example: Starting with 1 means the first waiver counts immediately

  • Example: Starting with 2 skips the first waiver and starts triggering after that point

Tip

For most businesses, the safest default is:

  • Every X waivers

  • Number of waivers = 1

  • Starting with waiver # = 1

Then use Add Conditions (Waiver / Kiosk Device / Kiosk Flow) to make sure the right waiver triggers the right follow-up.

 

 

Common Use Cases

  • “Waiver complete—here’s how check-in works”

  • “Thanks! Please arrive 15 minutes early”

  • “Minor waiver signed—confirm guardian info”

  • Staff alert for large group waiver completions

  • Reminder flow if waiver is signed but no check-in occurs later

 

 

What Data This Trigger Has Access To

This trigger includes:

  • Contact data (standard + custom fields)

  • Waiver context (waiver template/type, kiosk device/flow when available)

 

 

Important Things to Know

  • Waiver signed does not always mean the visit happened—it may happen days before arrival.

  • If you want post-visit messaging, pair this with Check-In Finished or Order Finished.

 

 

Example Automations

Example 1: Waiver Signed → Arrival Instructions

  1. Trigger: Waiver Signed

  2. Condition: Waiver = “General Waiver”

  3. Send SMS: “You’re all set. Please arrive 10 minutes early.”

  4. Send email: parking + what to expect

Example 2: Waiver Signed but No Check-In

  1. Trigger: Waiver Signed

  2. Delay: 24 hours

  3. If no check-in → send reminder + booking link

 

 

Best Practices

  • Keep waiver follow-ups helpful and short.

  • Avoid sensitive/legal wording—focus on next steps and safety basics.

  • Use kiosk device/flow conditions if you have multiple locations or experiences.