Skip to main content

Terms & Conditions Filter in Workflows

The Terms & Conditions (T&C) Filter lets workflows include or exclude contacts based on whether they accepted a Terms & Conditions checkbox at the moment of a form, survey, or quiz submission.

Updated over 3 months ago

Who This Is For / When to Use

This article is for Kyrios users building workflows that must respect user consent, compliance rules, or optional agreement logic. Use this filter when a form, survey, or quiz includes a Terms & Conditions checkbox and agreement is not always mandatory.

What the Terms & Conditions Filter Does

The Terms & Conditions Filter evaluates whether a contact agreed to the Terms & Conditions during the triggering submission event. The filter runs only at trigger time and determines whether the contact enters or continues in the workflow based on that consent value.

This filter does not retroactively evaluate existing contacts and does not read historical consent outside the triggering event.

Where the Terms & Conditions Filter Can Be Used

The Terms & Conditions Filter is available only on event-based workflow triggers where consent is collected at submission time.

Supported triggers:

  • Form Submitted

  • Survey Submitted

  • Quiz Submitted

If the trigger does not include a Terms & Conditions checkbox, the filter will not appear.

How to Add the Terms & Conditions Filter to a Workflow

Step 1: Open or Create a Workflow

  1. Go to Automations → Workflows.

  2. Open an existing workflow or click Create Workflow.

Step 2: Choose a Supported Workflow Trigger

  1. Add or edit the workflow trigger.

  2. Select Form Submitted, Survey Submitted, or Quiz Submitted.

Step 3: Add the Terms & Conditions Filter

  1. In the trigger settings, click Add filters.

  2. From Standard Fields, select Terms and Conditions.

Step 4: Configure the Filter Condition

Choose one of the following values:

  • Yes → Contact agreed to the Terms & Conditions

  • No → Contact did not agree to the Terms & Conditions

Step 5: Save and Publish

  1. Save the trigger configuration.

  2. Publish or republish the workflow.

  3. Test with a real submission to confirm correct filtering behavior.

How the Filter Is Evaluated

The Terms & Conditions Filter is event-based, not contact-based. This means:

  • The filter checks consent only at the time of submission.

  • The value is not stored as a reusable contact attribute for this filter.

  • Existing contacts already in the CRM are not evaluated unless they submit the form again.

Common Issues and Fixes

The filter does not appear in the trigger

Cause: The selected form, survey, or quiz does not include a Terms & Conditions checkbox.
Fix: Edit the form and add a Terms & Conditions field, then reselect the trigger.

All contacts pass the filter automatically

Cause: The Terms & Conditions checkbox is marked as required on the form.
Fix: This behavior is expected. If agreement is mandatory, all submissions will evaluate as Yes, making the filter unnecessary.

Existing contacts are not filtered correctly

Cause: The filter only evaluates new submission events.
Fix: Use tags, smart lists, or CRM field–based workflows for existing contact segmentation.

Example Use Cases

  • Compliance Routing: Only allow contacts who accepted updated terms to enter regulated workflows.

  • Optional Consent Paths: Send different follow-ups depending on whether consent was given.

  • Feature Access Control: Restrict access to gated actions unless T&C consent is confirmed.

  • Promotional Exclusions: Exclude users who declined optional legal agreements from campaigns.

Frequently Asked Questions

What is the purpose of the Terms & Conditions Filter?
The filter segments workflow entries based on whether a user agreed to the Terms & Conditions during a specific submission event.

Can this filter be used on all workflows?
No. It is only available on Form Submitted, Survey Submitted, and Quiz Submitted triggers that include a T&C checkbox.

What happens if Terms & Conditions are required?
All users will evaluate as “Yes,” making the filter unnecessary for gating logic.

What happens if a user never interacts with the T&C checkbox?
If the checkbox exists and is optional, the contact will evaluate as “No.”

Can this filter be used on existing contacts?
No. The filter is event-based and only evaluates new submissions.

Did this answer your question?