---
title: "Creating Completion Flows for Conditional Routing"
nav_title: "Completion Flows"
description: "Route participants to the right destination after a conversation based on what they shared."
date: "2026-03-30"
tags:
  [
    "completion flows",
    "conditional routing",
    "automated next steps",
    "lead routing",
  ]
nav_order: 11
nav_display: true
---

# Creating Completion Flows for Conditional Routing

Completion Flows route participants to different destinations at the end of a conversation based on what they shared. Instead of sending everyone to the same thank-you page, you can send qualified leads to sales, urgent issues to support, eligible participants to incentive instructions, and everyone else to the right next step. Redirect steps run automatically by default, or show a button when auto-redirect is disabled.

<div style="padding:62.28% 0 0 0;position:relative;"><iframe src="https://player.vimeo.com/video/1144653128?badge=0&amp;autopause=0&amp;player_id=0&amp;app_id=58479" frameborder="0" allow="autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share" referrerpolicy="strict-origin-when-cross-origin" style="position:absolute;top:0;left:0;width:100%;height:100%;" title="How To Create Completion Flows in Perspective AI"></iframe></div><script src="https://player.vimeo.com/api/player.js"></script>

## Use Cases

Completion Flows are ideal for:

- **Lead qualification** – Route high-value leads to sales while sending others to self-service resources
- **Support triage** – Direct urgent issues to a support-ticket form or intake page and simple questions to documentation
- **Product recommendations** – Send participants to relevant product pages based on their stated needs
- **Follow-up research** – Invite specific segments to additional studies while thanking others
- **Incentive distribution** – Provide different reward instructions based on eligibility criteria
- **Conversion optimization** – Guide qualified prospects to booking pages and others to nurture content

## How Completion Flows Work

During the interview, Perspective AI naturally gathers information about the participant. At the end of the conversation, Completion Flows evaluate this information against conditions you've defined and route participants to the appropriate destination.

**The process:**

1. Participant completes the interview
2. Perspective evaluates the information gathered against your defined conditions
3. The system determines which condition is met
4. Participant is redirected to the corresponding URL or shown a button, depending on the flow settings
5. No manual routing or follow-up required

## Setting Up Completion Flows

### Step 1: Define your routing logic

Before configuring Completion Flows, identify:

- **What criteria should determine routing?** (budget, company size, urgency, use case, etc.)
- **What are the threshold values?** (specific numbers, categories, yes/no answers)
- **Where should each segment go?** (URLs for each possible outcome)

### Step 2: Tell Perspective your conditions

Tell Perspective what should happen at the end of the conversation. Perspective adds a "Navigation Flow" section to your outline. This is the product name for completion flows.

**Example instruction:**

"Add a completion flow: if the participant's budget is more than $5,000 per month, redirect them to https://example.com/book-sales-call. If their budget is less than $5,000 per month, redirect them to https://example.com/pricing-guide."

![Dictating completion flow instructions to Perspective](/images/completion-flow-prompt.png)
_Tell Perspective your routing conditions conversationally and it will create the completion flow._

### Step 3: Review the updated outline

The research outline will update within a few seconds. Your new Navigation Flow section will appear in the outline structure with your conditional routing logic.

![Research outline showing completion flow section](/images/completion-flows-prompt-gif.gif "animated")
_Perspective adds a Navigation Flow section to your outline based on your instructions._

Your completion flow is now configured. Test it before inviting participants.

### Step 4: Test your flow

Before inviting participants:

1. Take the interview yourself
2. Provide responses that would trigger each condition
3. Verify you're redirected to the correct destination
4. Test edge cases (missing information, ambiguous responses)

### Step 5: Launch your research

Once you've confirmed the flow works correctly, invite participants. Each person will be routed to the appropriate destination based on their responses.

## Example Scenarios

### Scenario 1: Enterprise Lead Qualification

**Goal:** Route qualified leads to sales while providing self-service resources to others

**Instruction to Perspective:**

"Add a completion flow: if monthly budget is greater than $5,000 and company size is greater than 100 employees, redirect to https://example.com/book-enterprise-demo. Otherwise, redirect to https://example.com/self-service-plans."

**Outcome:** High-value prospects connect directly with sales while smaller prospects get immediate access to information.

### Scenario 2: Support Request Triage

**Goal:** Prioritize urgent issues while routing simple questions to documentation

**Instruction to Perspective:**

"Add a completion flow: if the issue is blocking their work and marked as urgent, redirect to https://support.example.com/create-ticket with priority set to high. For general questions or feature requests, redirect to https://docs.example.com/help-center."

**Outcome:** Critical issues get immediate attention while documentation handles routine questions.

### Scenario 3: Product Recommendation

**Goal:** Send participants to the most relevant product page based on their use case

**Instruction to Perspective:**

"Add a completion flow based on their primary use case: for team collaboration, redirect to https://example.com/products/team-workspace. For individual productivity, redirect to https://example.com/products/personal-assistant. For analytics and reporting, redirect to https://example.com/products/business-intelligence."

**Outcome:** Each participant lands on the product page that matches their needs.

### Scenario 4: Follow-Up Research Invitation

**Goal:** Invite engaged power users to deeper research while thanking others

**Instruction to Perspective:**

"Add a completion flow: if the user uses the product daily and is interested in beta features, redirect to https://example.com/join-beta-research-panel. Otherwise, redirect to https://example.com/thank-you."

**Outcome:** Target advanced research opportunities to the right segment without spamming others.

### Scenario 5: Incentive Eligibility

**Goal:** Provide different incentive instructions based on completion quality

**Instruction to Perspective:**

"Add a completion flow: if the interview was completed in full and the participant provided detailed feedback, redirect to https://rewards.example.com/claim?tier=premium. If the interview was brief or they skipped questions, redirect to https://rewards.example.com/claim?tier=standard."

**Outcome:** Reward engagement quality while still thanking all participants.

### Scenario 6: Pre-filled Booking Link

**Goal:** Send qualified participants to a scheduling page with their details already filled in so they only pick a time

**Instruction to Perspective:**

"Add a completion flow: if the participant is a good fit, redirect them to https://calendly.com/acme/intro-call?name={{participant.name}}&email={{participant.email}}. Otherwise, redirect to https://example.com/thank-you."

**Outcome:** The participant lands on the booking page with their name and email pre-filled, so booking is one click. See [Passing participant details to the destination](#passing-participant-details-to-the-destination) for every placeholder you can use.

## Refining Your Completion Flow

Like other parts of your research outline, you can refine completion flows conversationally:

**Example refinements:**

- "Update the completion flow to use a $10,000 threshold instead of $5,000"
- "Add a third condition for mid-market companies between 50-100 employees"
- "Change the redirect URL for budget-conscious users"

Each change generates an updated outline with your revised completion flow logic.

## Best Practices

**Keep conditions clear and measurable.** Use specific thresholds that Perspective can evaluate objectively: "budget over $5,000" not "seems interested in enterprise."

**Test all paths.** Ensure you've tested scenarios that trigger each possible redirect. Missing edge cases can send participants to the wrong destination.

**Provide fallback logic.** Define what happens when information is ambiguous or missing. Always have a default destination.

**Use meaningful URLs.** Ensure redirect destinations are relevant and valuable to the participant based on their responses.

**Limit complexity.** Start with 2-3 conditions. Overly complex routing logic is difficult to test and maintain.

**Make destinations mobile-friendly.** Many participants complete interviews on mobile devices. Ensure redirect pages work well on all screen sizes.

**Track outcomes.** Review the Activity tab for individual conversations, and add query parameters or downstream analytics to understand how each destination performs over time.

**Communicate next steps.** Before redirecting, Perspective should acknowledge what's happening: "Based on your needs, I'll connect you with our sales team" or "I'll send you to our pricing guide."

## Common Pitfalls & Fixes

**Ambiguous conditions** → Be specific when instructing Perspective. "High budget" is vague; "budget over $10,000 per month" is clear and actionable.

**Missing fallback** → Always define what happens if none of your conditions are met. Include an "otherwise" or "for all other cases" instruction.

**Untested edge cases** → Test scenarios where participants provide unexpected answers, skip questions, or give ambiguous responses.

**Too many conditions** → More than 5 conditions becomes difficult to manage and test. Simplify by grouping similar outcomes.

**Broken redirect URLs** → Verify all destination URLs work before launching. A 404 error creates a poor participant experience.

**Logic conflicts** → Ensure conditions don't overlap. Make your instructions clear about which condition takes precedence.

**Ignoring mobile experience** → Test redirect destinations on mobile devices. Poor mobile experiences lose engaged participants.

**Not communicating the redirect** → Participants should understand why they're being sent somewhere. Have Perspective explain the next step before redirecting.

## Passing Participant Details to the Destination

A redirect or submit URL can carry values from the conversation by using `{{...}}` placeholders. Perspective fills them in when the conversation ends, URL-encodes each value, and then sends the participant on. Ask Perspective for the URL you want, placeholders included, and it will add them to the flow.

| Placeholder             | Filled with                                                                                                                                                    |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `{{participant.name}}`  | The participant's name, from sign-in, the `name` URL parameter, a personalized invite, or the channel they joined from                                         |
| `{{participant.email}}` | The participant's email, from the same sources                                                                                                                 |
| `{{metadata.key}}`      | The participant metadata entry `key`, e.g. an incoming [URL parameter](/docs/guide/design/url-parameters) like `utm_source` or a personalized invite's context |
| `{{field_key}}`         | The [form field](/docs/guide/design/add-form-fields) with key `field_key`, extracted from the conversation                                                     |

**Example: a scheduling link that skips the contact form**

```text
https://calendly.com/acme/intro-call?name={{participant.name}}&email={{participant.email}}
```

If the participant is Ada Lovelace at ada@example.com, they arrive at:

```text
https://calendly.com/acme/intro-call?name=Ada%20Lovelace&email=ada%40example.com&interviewId=...
```

**Example: carry a campaign tag through**

```text
https://example.com/offer?src={{metadata.utm_source}}&plan={{preferred_plan}}
```

**Good to know:**

- Placeholders work in the path as well as in query parameters, and can be part of a larger value. They cannot appear in the domain or protocol.
- A value that isn't available becomes an empty string, so the URL stays valid. If the participant never gave a name, `name=` is sent with no value.
- Form field values are extracted after the conversation ends, so a URL that uses a `{{field_key}}` placeholder shows the participant a short processing state first. Participant and metadata placeholders are known immediately and redirect right away.
- Perspective always adds an `interviewId` query parameter to the final URL, so the destination can look the conversation up.
- The web experience also appends the conversation link's own non-reserved query parameters to the redirect as-is, so `?utm_source=newsletter` on the way in arrives as `utm_source=newsletter` on the way out without any placeholder. Use `{{metadata.key}}` when the destination expects a different parameter name, the value belongs in the path, the value comes from a personalized invite, or the URL is a submit step. A parameter the redirect URL already sets itself — fixed or from a placeholder — keeps its own value and is not overwritten.
- Use `{{participant.email}}` for the participant's own email rather than a form field: it comes from sign-in or the invite, so it doesn't depend on the participant spelling it out in the conversation.

## Technical Considerations

**URL validation:** Ensure all redirect URLs are properly formatted and accessible.

**Parameter passing:** You can include fixed query parameters in redirect links, and redirect URLs can use `{{participant.name}}`, `{{participant.email}}`, `{{metadata.key}}`, and `{{field_key}}` placeholders. See [Passing Participant Details to the Destination](#passing-participant-details-to-the-destination). Perspective also appends an `interviewId` query parameter. For incoming participant context, see [URL Parameters](/docs/guide/design/url-parameters).

**External systems:** Use [Automations](/docs/guide/design/automations) for webhooks, CRM updates, or other server-side data delivery.

**Timing:** Redirects happen after the interview conclusion message, giving participants a moment to understand what's happening next.

**Multiple conditions:** When multiple conditions could apply, be clear about priority in your instructions to Perspective.

## Combining Completion Flows with Other Features

**With URL Parameters:** Use [incoming URL parameters](/docs/guide/design/url-parameters) to shape the conversation, and carry them on to the destination with `{{metadata.key}}` placeholders in the redirect URL.

**With Form Fields:** Capture the same details as [form fields](/docs/guide/design/add-form-fields) for records and automations. Routing conditions should be written in natural language instead of raw output-field filters.

**With User Interviews Integration:** Use Completion Flows to redirect back to User Interviews with custom parameters based on interview outcomes. See [User Interviews Integration](/docs/guide/collect/sync-status-with-user-interviews).

## When to Use Completion Flows

Use Completion Flows when different participants should land on different next steps after the conversation.