Exact URL Matching
Match specific pages precisely — /pricing, /contact, /demo. High-value pages get dedicated, conversion-optimised chat flows.
Page Match Module
URL-Based Chat Routing
The Page Match module reads the visitor's current URL and routes the chat workflow based on which page they're browsing. Pricing page visitors get a sales workflow. Support page visitors get a help desk flow. Product pages trigger targeted guidance. One widget, infinite contexts.
- No credit card
- 14-day free trial
- UK hosted
- Visual builder
What Is the Page Match Module?
The Page Match module evaluates the visitor's current page URL and routes the chat workflow based on matching rules you define. It checks the URL path, query parameters, or both, and sends the conversation down the branch that matches. If no rules match, a default branch catches everything else.
Context is everything in chat. A visitor on your pricing page has very different needs from one reading a support article or exploring a product feature. Without Page Match, every visitor sees the same generic greeting and the same workflow, regardless of where they are on your site. That's a missed opportunity. A pricing page visitor is likely evaluating whether to buy — they need a sales-oriented conversation with quick access to plan comparisons, discounts, or a live demo. A support page visitor already bought and needs help — they want fast access to troubleshooting, an agent, or a knowledge base.
The Page Match module lets you build a single workflow that adapts to every page on your site. You define URL patterns — exact matches like /pricing, prefix matches like /blog/*, or regex patterns for complex URLs — and each pattern maps to a branch. The module evaluates these rules top to bottom and sends the visitor down the first matching branch. This means you can have broad catch-all patterns at the bottom and specific, high-value patterns at the top for maximum control.
Wildcard & Prefix Patterns
Use patterns like /blog/* or /products/* to match entire sections of your site with a single rule. Broad coverage, minimal configuration.
Query Parameter Support
Match on URL parameters like ?utm_source=google or ?plan=enterprise. Tailor workflows based on how visitors arrived or what they've selected.
Priority-Based Rules
Rules are evaluated top to bottom. Place specific, high-value patterns first and broad defaults last for predictable, controlled routing behaviour.
How Page Match Routing Fits Into a Workflow
The Page Match module is typically placed at or near the very start of your workflow. Because the URL determines the entire conversational context, it makes sense to branch early — before sending a greeting message, before collecting data, before any other logic. Each branch then contains a fully tailored sub-workflow for that page context.
This architecture is clean and scalable. When you launch a new product page, you add a new URL rule and a new branch. When you redesign your pricing page, you update only the /pricing branch. Other branches are completely isolated. This separation of concerns is one of the biggest advantages of URL-based routing — it keeps complex, multi-page workflows maintainable even as your site grows.
Example: SaaS Website — Page-Specific Workflows
A SaaS company delivers different chat experiences on pricing, documentation, and homepage using a single workflow.
START
Page Match
URL pattern
/pricing
Human Chat
Sales team
/docs/*
AI Chat
Docs helper
Default
Step-by-Step Breakdown
- Page Match: The module reads the visitor's current URL the instant the chat widget opens. Three rules are evaluated in order.
- /pricing Branch: Visitors on the pricing page are greeted with "Thinking about upgrading?" and connected to a sales agent who can discuss plans, discounts, and enterprise options.
- /docs/* Branch: Visitors anywhere in the documentation section are routed to an AI assistant trained on the product's knowledge base, providing instant code examples and troubleshooting.
- Default Branch: All other pages show a general-purpose Button Group offering "Sales" or "Support" choices, letting the visitor self-route.
Best Practices & Tips
URL-based routing is powerful but requires careful pattern design. Follow these guidelines to avoid misroutes and maximise relevance.
Order Rules Carefully
Rules evaluate top to bottom. Place the most specific patterns first (/pricing/enterprise) and broad wildcards last (/*) to prevent early matches swallowing specific pages.
Target High-Value Pages
Focus your best workflows on pages with the highest conversion potential: pricing, demo, checkout, and product comparison. Generic pages can use a simpler default branch.
Keep URLs in Sync
When your website URLs change (redesign, new slug structure), update your Page Match rules immediately. Broken patterns silently fall through to the default branch.
A/B Test Page Flows
Create two versions of a page branch and split traffic using a Conditional node after the Page Match. Measure which conversation flow converts better.
Frequently Asked Questions
Does Page Match support wildcard patterns?
Yes. You can use wildcard patterns like /products/* to match any page under a URL path. This is ideal for matching entire sections of your site — product categories, documentation pages, or blog posts — with a single rule.
Can I match on query parameters like UTM tags?
Yes. The module can evaluate query string parameters in the URL. For example, you could route visitors arriving from a Google Ads campaign (?utm_source=google) to a sales-focused workflow while organic visitors see a general support flow.
What happens if no URL rule matches?
Unmatched URLs are routed to the default branch. We strongly recommend always defining a default branch with a useful general-purpose workflow so no visitor encounters a dead end.
Can I combine Page Match with other routing modules?
Absolutely. Page Match is often the first routing decision, followed by Language Router, Time of Day, or Conditional Logic within each branch for layered, context-rich routing.
Related Modules
Page Match works alongside these modules to create highly contextual, page-aware chat experiences.
Deliver the Right Chat on Every Page
Set up URL-based routing in minutes. Every visitor gets a contextual, relevant chat experience — from pricing to support to product pages.