Conditional Thank You Pages

Conditional Thank You pages let you show different messages, redirects, and conversion events to different respondents — based on what they said or how the AI scores them.

Instead of one generic "Thanks!" for everyone, you can show a high‑intent lead a booking link, send a price‑shopper to a comparison page, and redirect support tickets to a status tracker — all automatically.

---

Why Use This?

Every respondent is different. A one‑size‑fits‑all Thank You page wastes your highest‑value moment — the instant someone completes your form.

Without Conditional TY	With Conditional TY
Everyone sees the same page	Each respondent gets a tailored experience
One redirect URL for all	Hot leads → booking page, cold leads → resources page
Single conversion event	Different pixel events per lead quality
No post‑submit intelligence	AI evaluates responses in real time

:::tip The conversion moment
The Thank You page is the highest-intent moment in your entire funnel. The respondent just invested time completing your form — conditional routing lets you capitalize on that intent while it's fresh.
:::

---

How It Works — The Big Picture

 ┌──────────────────────────────────────────────────────────────┐
 │ CONDITIONAL THANK YOU FLOW │
 └──────────────────────────────────────────────────────────────┘

 ① SUBMIT ② AI SCORES ③ EVALUATE
 ┌──────────────┐ ┌──────────────┐ ┌──────────────┐
 │ Respondent │────────│ Quick AI │────────│ Check each │
 │ completes │ │ analyzes │ │ outcome's │
 │ the form │ │ answers │ │ conditions │
 │ │ │ (<1 second) │ │ top to │
 │ │ │ │ │ bottom │
 └──────────────┘ └──────────────┘ └──────┬───────┘
 │
 ┌───────────────┼──────────────┐
 │ │ │
 Match found Match found No match
 │ │ │
 ▼ ▼ ▼
 ┌────────────┐ ┌────────────┐ ┌───────────┐
 │ Outcome 1 │ │ Outcome 2 │ │ Default │
 │ "Book a │ │ "Download │ │ Thank │
 │ Call" page│ │ Guide" │ │ You page │
 │ │ │ page │ │ │
 └─────┬──────┘ └─────┬──────┘ └─────┬─────┘
 │ │ │
 ▼ ▼ ▼
 ┌─────────────────────────────────────────┐
 │ Fire analytics: Meta Pixel + GA4 │
 │ Fire outcome webhook (if configured) │
 └─────────────────────────────────────────┘

The key insight: first match wins. Outcomes are checked in priority order (top to bottom), and the first one whose conditions pass is shown to the respondent. If nothing matches, your Default Thank You page is used as the fallback.

---

Step 1: Enable Conditional Mode

1. Open your form in the Form Builder
2. Go to the Settings tab → Thank You Page section
3. Scroll down to Conditional Routing
4. Toggle Conditional Thank You to ON

You'll see a visual pipeline indicator:

 ┌─────────────────────────────────────────────────┐
 │ 1 Submission → 2 Check conditions → │
 │ 3 Match? Show outcome │ No match → Default │
 └─────────────────────────────────────────────────┘

:::note Default page is your safety net
Your Default Thank You page (configured above the conditional section) is always the fallback. It appears whenever no conditional outcomes match — so every respondent always sees something meaningful.
:::

---

Step 2: Create Outcomes

Click + Add Conditional Outcome to create a new outcome. Each outcome has three parts:

Conditions — When to Show This

Conditions determine which respondents see this outcome. You can combine conditions using ALL (every condition must pass) or ANY (at least one must pass).

Each condition has three parts:

Part	What it does	Example
Field	What to check	Buyer Intent (AI) or budget (Answer)
Operator	How to compare	Equals, Greater Than, Contains
Value	What to match against	Ready to Buy, 50000

Two Types of Fields

AI Metrics — These are scored by Sayify's AI in real time (<1 second) when the form is submitted. The available metrics depend on your form's use case:

Use Case	Available AI Metrics
Lead Qualification	ICP Fit, Buyer Intent, Budget Status, Urgency Level, Qualification Status, Follow‑Up Priority
Client Intake	Request Type, Service Category, Client Readiness, Fit Status, Attention Priority
Support Triage	Ticket Type, Severity, Business Impact, Churn Risk, SLA Priority
General	Action Needed, Priority, Clarity Status	Form Answers — These are the raw values respondents entered in your form fields. Any question with a field_key appears here. For example, if you have a question with field key budget, it shows as budget (Answer).

Available Operators

Operator	Meaning	Best for
Equals	Exact match	Enum/dropdown values
Not Equals	Doesn't match	Excluding specific values
Contains	Substring match	Free‑text answers
Greater Than	Numeric comparison	Scores, budgets
≥	Greater than or equal	Threshold checks
Less Than	Numeric comparison	Budget caps
≤	Less than or equal	Score ceilings
In List	Matches any in a list	Multiple acceptable values
Not Empty	Field has a value	Ensuring something was answered

Thank You Page Content — What They See

For each outcome, you configure a custom Thank You page:

Setting	What it controls
Title	The heading shown to the respondent (e.g. "You're a Great Fit!")
Message	The subtitle text below the heading
Icon Emoji	A custom icon displayed above the title
Icon Color	The background colour of the icon circle
Confetti	Whether celebratory particles animate on screen
Template	Choose from a gallery of pre-designed page styles

Redirect URL — Where They Go Next

Optionally redirect respondents to a specific URL after a delay:

Setting	What it does	Example
Redirect URL	Where to send them	https://calendly.com/sales/30min
Redirect Delay	Seconds before redirecting (1–30)	5 seconds

This is perfect for sending qualified leads to a booking page, or directing support tickets to a status tracker.

---

Step 3: Set Up Analytics Events

Each outcome can fire separate conversion events for Meta Pixel and Google Analytics 4. This means you can track different conversion values for different lead qualities.

Setting	What it fires	Example
Meta Pixel Event	fbq('trackCustom', 'YourEvent')	Lead, SubmitApplication, CompleteRegistration
GA4 Event	gtag('event', 'your_event')	generate_lead, sign_up, purchase

:::tip Separate tracking per lead quality
Set your "Hot Lead" outcome to fire Lead (Meta) + generate_lead (GA4), and your "Cold Lead" outcome to fire ViewContent (Meta). This lets you optimise ad spend toward your highest‑value conversions.
:::

---

Step 4: Priority & Ordering

Outcomes are evaluated top to bottom in the order shown in the builder. The first outcome whose conditions match wins — all others are skipped.

 ┌─────────────────────────────────────────────────────┐
 │ PRIORITY EVALUATION ORDER │
 ├─────────────────────────────────────────────────────┤
 │ │
 │ #1 "Hot Lead" │
 │ IF buyer_intent = "Ready to Buy" │
 │ AND budget_status = "Has Budget" │
 │ → Show booking page FIRST MATCH WINS │
 │ │
 │ #2 "Warm Lead" │
 │ IF buyer_intent = "Evaluating" │
 │ → Show comparison page (skipped if #1 matched)│
 │ │
 │ #3 "Cold Lead" (catch-all) │
 │ IF (no conditions — always matches) │
 │ → Show resources page │
 │ │
 │ FALLBACK Default Thank You page │
 │ (shown if no outcomes exist or all are broken) │
 └─────────────────────────────────────────────────────┘

You can drag outcomes up and down using the arrow buttons to change their priority.

:::warning Put specific conditions first
Always place your most specific conditions at the top. A catch-all outcome (no conditions) should go last — otherwise it will match everyone and your other outcomes will never trigger.
:::

---

Real‑World Examples

Lead Qualification Form

Outcome	Conditions	Thank You Page	Redirect
Hot Lead	Buyer Intent = "Ready to Buy" AND Budget = "Has Budget"	"Great news! Let's book a call."	calendly.com/sales/demo
Warm Lead	Buyer Intent = "Evaluating"	"Thanks! Here's our comparison guide."	your-site.com/guide
Nurture	(no conditions — catch‑all)	"We'll be in touch soon!"	(none)

Support Triage Form

Outcome	Conditions	Thank You Page	Redirect
Critical	Severity = "Critical" AND Business Impact = "Blocked"	"We're on it — a support engineer will reach out within 1 hour."	(none)
Normal	(no conditions)	"Thanks for reporting! We'll review within 24 hours."	support.your-site.com/status

Client Intake Form

Outcome	Conditions	Thank You Page	Redirect
Ready to Go	Client Readiness = "Ready to Proceed" AND Fit Status = "Good Fit"	"Excellent! We'll send a proposal within 24 hours."	(none)
Needs Discussion	Client Readiness = "Has Questions"	"Great start — let's schedule a call to discuss details."	calendly.com/intake/30min
General	(catch-all)	"Thanks for reaching out! We'll review and respond shortly."	(none)

---

How the AI Scoring Works

When conditional mode is enabled, Sayify runs a Quick Score at submit time — an ultra‑fast AI evaluation that takes less than 1 second. Here's what makes it efficient:

 ┌──────────────────────────────────────────────────────────┐
 │ QUICK SCORE — UNDER THE HOOD │
 └──────────────────────────────────────────────────────────┘

 ① SCAN ② BUILD ③ CALL
 ┌──────────────┐ ┌──────────────┐ ┌──────────────┐
 │ Look at │────────│ Build tiny │────────│ Gemini │
 │ your │ │ prompt with │ │ Flash AI │
 │ outcome │ │ ONLY the │ │ returns │
 │ conditions │ │ fields you │ │ scores in │
 │ │ │ referenced │ │ <1 second │
 └──────────────┘ └──────────────┘ └──────────────┘

Condition-driven efficiency: The AI only evaluates fields that your conditions actually reference. If you only check buyer_intent, the AI only scores buyer_intent — no wasted tokens on fields you never look at.

Fail-open design: If the AI call fails for any reason, submission still succeeds and your Default Thank You page shows. AI errors never block the respondent.

---

Per‑Outcome Webhooks

Each outcome can optionally fire a webhook to an external URL when matched. This lets you trigger different automations based on which outcome a respondent hits — for example, adding hot leads to a different CRM pipeline than cold leads.

The webhook fires asynchronously (15 second delay) to ensure the InboxCase record is fully created before external systems try to look it up.

---

Tips for Best Results

• Start with 2–3 outcomes — Don't over-engineer on day one. Start with "Hot" and "Everyone Else", then refine based on real data.

• Use a catch-all outcome — Add one outcome at the bottom with no conditions. This acts as a safety net — even better than the Default page because you can customise its analytics events.

• Use AI metrics for complex scoring — For conditions like "lead quality" that require understanding context across multiple answers, use AI metrics. For simple field checks (e.g. "did they select Enterprise?"), use Form Answer fields directly.

• Set up analytics from day one — Even if you only have one outcome, configure the Meta Pixel and GA4 events. This gives you conversion data in your ad dashboards immediately.

• Test with real submissions — Preview your form, fill it out with different answers, and verify that the correct outcome shows. The live preview in the builder gives you a visual preview of each outcome, but real submissions are the ultimate test.

• Combine ALL and ANY logic — Use "ALL" when every condition must be true (e.g. "high budget AND ready to buy"). Use "ANY" when any single condition is sufficient (e.g. "urgent OR critical severity").

---

Frequently Asked Questions

How fast is the AI scoring?
Under 1 second. The Quick Score uses Gemini Flash with a minimal prompt — it only evaluates the specific fields your conditions reference, keeping the response time sub-second.

What happens if the AI fails?
The submission still succeeds and the respondent sees your Default Thank You page. The system is designed to fail-open — AI errors never block or break the form experience.

Can I use both AI metrics and form answers in the same outcome?
Yes! You can mix and match. For example: buyer_intent (AI) = "Ready to Buy" AND budget (Answer) > 10000.

Do conditional outcomes work with embedded forms?
Yes. The conditional resolution happens server-side, so it works regardless of whether the form is shared via link or embedded on your website.

Can I have different analytics events per outcome?
Yes — that's one of the main benefits. Each outcome has independent Meta Pixel and GA4 event fields, so you can fire different conversion signals based on lead quality.

How many outcomes can I create?
There's no hard limit, but we recommend keeping it under 10 for maintainability. Remember: outcomes are evaluated top-to-bottom, so more outcomes means more complexity to manage.

What's the difference between Redirect URL on the Default page vs. outcomes?
Each outcome has its own independent redirect URL and delay. If Outcome #1 matches, its redirect is used — the default redirect is ignored. The default redirect only kicks in when no conditional outcome matches.

---

What's Next?

• Intake Page — Customise what respondents see before submitting.
• Inbox — Review all submitted responses and AI insights.
• Destinations — Route approved data to CRMs and spreadsheets.
• Webhooks — Set up external integrations for real-time notifications.
• Key Concepts — Review all platform building blocks.