# Route Hub {% hint style="info" %} Route Hub is available on Growth and Enterprise plans. {% endhint %} Route Hub helps you deliver the right demos, resources, and next steps to each viewer automatically. Instead of sending one generic link to everyone, you can collect viewer information, understand what they care about, route them to the right experience, and track the full journey. This guide walks through how to create, customize, publish, and share a Route Hub. {% @supademo/embed demoId="cmlvedwad4tiud2ntaef14tbn" url="" %} ### Before you start A Route Hub is built using a visual workflow builder. In most cases, your setup will include: * A **Form** or **Interest Screen** to collect viewer input * A **Route** node to branch viewers based on their responses * One or more **Showcases** as the destination for each path * An optional **Integrations** node to sync lead and activity data to your CRM ### 1. Create a new Route Hub
Start by creating a new Route Hub and giving it a clear name. When you create it, choose one of the suggested intents (1) **Collect leads,** (2) **Qualify buyers,** (3) **Collect leads + qualify.** Your selected intent creates a default workflow to help you get started faster. ### 2. Open the draft workflow
After creating your Route Hub, you’ll be taken into a draft workflow in the visual editor. From here, you can build and customize your journey by: * Dragging and dropping nodes * Connecting nodes together or deleting linkages * Reordering the flow * Editing the settings for each step This is where you define how viewers move from entry to destination. ### 3. Start with a Form or Interest Screen Every Route Hub starts with either a **Form** or an **Interest Screen**. You can use just one of these, or chain them together in sequence depending on how much information you want to collect before routing. A common setup looks like this: {% hint style="info" %} **Form → Interest Screen → Route → Showcase** {% endhint %} ### 4. Customize your Form
Use the **Form** node to capture lead details and qualification data. Inside the Form, you can adjust: * Form fields * Submit button text * Cover screen and branding * Logo * Header text * Subtext * Email recipients The values collected in the form can later be used in your routing logic. For example, you might route viewers differently based on company size, role, or another field you add. Once your form is ready, save your changes. ### 5. Customize your Interest Screen
Use the **Interest Screen** node to learn what the viewer wants to see. Inside the edit page of the Interest Screen, you can adjust the same design options available on the form screen. In addition, you can customize the table of topics shown to viewers Each row in the table lets the viewer indicate one of three preference levels for that topic. These responses can then be used as conditions in your routing step. This is especially useful when you want to personalize the next step based on product interests, use cases, or buying priorities. ### 6. Connect your inputs to a Route Once your Form and/or Interest Screen is set up, connect those nodes to a **Route** node. The Route node is where you define branching logic. You can create multiple rules based on: * Form field values * Interest Screen responses * A combination of both
This lets you mix and match qualification and intent signals to decide what each viewer should see next. For example, you might: * Send enterprise viewers to a more advanced Showcase * Send viewers interested in a specific feature to a tailored demo collection * Send lower-intent viewers to educational resources instead of a sales-focused destination Each rule can point to a different next step in the workflow. ### 7. Build Showcases for each route A **Showcase** is the destination viewers land on after being routed. Inside a Showcase, you can create a collection of assets such as: * Interactive demos * Internal videos * External videos (i.e. YouTube, Loom) * PDFs * External links * Embeds like Calendly or HubSpot forms
Each Showcase can include its own: * Assets * Sections * Layout and design choices You can easily import an existing Showcase, create a new one from scratch, or duplicate a Showcase to create variations for different audience segments. This makes it easy to serve different content experiences for different viewer routes without rebuilding everything manually. ### 8. Preview in Draft mode and publish when ready Route Hub changes are made in **Draft** mode by default. This means you can safely make edits and preview your updates before pushing them live. When you’re ready, click **Publish** to make the latest version live. You can also preview both **Draft** and **Published** versions from the top-right corner of the screen. This makes it easy to test changes before updating the live experience. ### 9. Share or embed your Route Hub Once published, you can distribute your Route Hub in two ways. 1. **Share as a link** (email, Slack, Microsoft Teams, outbound, demo leave-behinds) 2. **Share as embed** (websites, book a demo forms, onboarding pages, university) ### 10. Connect integrations and track analytics
All viewer activity inside a Route Hub is tracked in analytics. You can monitor metrics such as: * Total views * Unique viewers * Engagement rate * Leads captured * Lead activity * Lead scoring If you connect an **Integrations** node in your workflow, this data can also be sent directly to your CRM of choice. This helps you keep lead data, engagement signals, and activity history connected to your existing systems. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.supademo.com/share/route-hub.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.