Q1Short answer · Required
What’s your first name?
Gives the completed response a useful personal reference.
Inbound routingMulti-path inbound
Multi-path inbound routing
Give every inbound request the right front door.
Identify the inquiry, collect only the context its path needs, and show sales, support, partnership, careers, and general visitors one controlled next step.
Best for: Teams that receive sales, support, partnership, careers, and general inquiries through one front door.
Available on Free. Replace the example questions, policy, outcomes, and destinations before publishing.
Starting routing policy
Inquiry type → relevant context → five deterministic destinations
- Captures
- Contact context, inquiry type, request details, and sales timing when relevant
- Qualifies
- Request type, defined respondent outcome, and sales context
- Routes
- Sales discovery calendar, support request page, partnership confirmation, careers page, or general confirmation
What this flow decides
Which respondent-facing next step should this inbound inquiry receive?
The flow identifies the request before asking for path-specific context, so people see the right destination or confirmation without completing irrelevant questions.
Captures
Contact context, inquiry type, request details, and sales timing when relevant
Qualifies
Request type, defined respondent outcome, and sales context
Routes
Sales discovery calendar, support request page, partnership confirmation, careers page, or general confirmation
Routing policy
Make the routing policy yours before the flow goes live.
This template uses explicit inquiry-type routes. Sales or project inquiries continue through budget and timing questions, while other requests take a shorter path to their defined destination.
- 1
The inquiry type selects the path.
- 2
Every path collects request details before routing.
- 3
Only sales or project inquiries receive budget and timeline questions.
- 4
Each inquiry type has one explicit external destination or confirmation ending.
Questions
See every question and the job it does.
Audit the complete starting blueprint before you copy it. Each rationale explains why the field exists and what decision it supports.
Contact context
Q2Email · Required
What’s the best email for a reply?
Provides a reliable reply channel for every inquiry path.
Q3Short answer · Optional
What company or organization are you with?
Adds business context without deciding the route by itself.
Request route
Q4Single choice · Required
What are you contacting us about?
Selects the deterministic path and prevents irrelevant follow-up questions.
Starting choices: Sales or project inquiry, Existing customer support, Partnership or media, Careers, Something else
Q5Long answer · Required
What should the right team know?
Collects the context needed for later follow-up from the response stored in Qualyo.
Sales context when relevant
Q6Single choice · Required
What budget range are you working with?
Adds a practical project constraint only on the sales or project path.
Starting choices: Under $5k, $5k–$15k, $15k–$50k, $50k+, Not sure yet
Q7Single choice · Required
When would you like to move forward?
Adds timing context only when the inquiry is about a potential engagement.
Starting choices: As soon as possible, Within 30 days, In 1–3 months, Later, Just exploring
Logic, outcomes, and destinations
One front door can still produce five explicit respondent outcomes.
The inquiry-type answer controls the route. No AI interpretation is needed, non-sales visitors skip sales questions, and every path ends with a named destination that you replace before publishing.
Deterministic inquiry route
The saved inquiry type controls which questions and destination follow
Where the flow branches
Question path
Contact → inquiry type → request details → budget and timing on the sales path
Deterministic inquiry route
The saved inquiry type controls which questions and destination follow
Five defined destinations
Sales discovery calendar, support request page, partnership review confirmation, careers page, or general review confirmation
Outcome destinations
Sales or project inquiry
Continue to the sales discovery calendar
Collect budget and timing context before opening the external sales calendar.
Existing customer support
Continue to the support request page
Show the external support request page without asking sales questions.
Partnership or media
Complete with the partnership or media review confirmation
Show a tailored confirmation ending while the completed response remains available in Qualyo.
Careers
Continue to the careers page
Show candidates the external careers page.
Other inquiry
Complete with the general review confirmation
Show a general review confirmation and keep the completed response available in Qualyo.
Local deterministic route
Try the route without sending a submission.
This local preview demonstrates the five deterministic destinations in the starting flow. It runs entirely on this page, sends no request, and stores no answer.
Local deterministic route
What kind of inquiry is this?
Choose a request type to preview its deterministic destination. Nothing is submitted or stored.
Explicit route choice
Sales or project inquiry
Continue to the sales discovery calendar
Sales discovery calendar
The full flow asks for budget and target timing before opening the external calendar.
No submission sent. No lead created. No answer stored. No AI used.
Customization
Replace the example policy with the way your team works.
The route is complete, but its labels, external resources, sales questions, confirmation endings, and form-level delivery settings must match how your team actually handles inbound work.
- Step 1
Name the real request types
Keep only the inbound categories your organization can recognize and own.
- Step 2
Define every outcome
Choose an external resource or calendar, or write a tailored confirmation ending. Configure notifications and webhooks separately at the form level when completed submissions need delivery.
- Step 3
Keep questions path-specific
Ask budget and timing only where they change the sales or project route.
- Step 4
Test every destination
Run all five paths and replace every placeholder before publishing the flow.
Use it for the right job
Use this when one generic contact route creates manual triage.
Good fit
- Agencies and service businesses receiving several kinds of inbound requests.
- Teams that need one public entry point with explicit respondent outcomes.
- Businesses that want sales questions to appear only on a sales path.
Choose another workflow
- A single-purpose qualification flow where every respondent follows the same path.
- A support desk, applicant tracking system, CRM, or shared team inbox replacement.
- A workflow whose destinations, confirmation copy, and response handling have not been agreed internally.
Multi-path inbound routing FAQ
Questions before you use the flow
What is an inbound routing flow?
An inbound routing flow identifies the kind of request, gathers the context its path needs, and presents a defined next step such as a calendar, resource, or tailored review confirmation.
Does every visitor answer all seven questions?
No. Every path uses the five shared contact and request questions. Only sales or project inquiries continue through the budget and target-timeline questions.
Does this template use AI to choose the route?
No. The inquiry-type choice controls the route through deterministic logic. Use AI only in a different flow where open context genuinely needs judgment.
Can I change the inquiry types and destinations?
Yes. Replace every option, path-specific question, external resource, calendar, review confirmation, and ending before publishing. Configure any submission notifications or webhooks separately at the form level.
Can support and careers requests skip sales questions?
Yes. The saved graph takes those request types through shorter paths, so budget and sales timing never appear.
Is the preview above a live public form?
No. It is a local, deterministic demonstration of the route destinations. It does not send a request, save an answer, or consume an AI conversation.
Start with five explicit inbound routes.
Copy the shared questions and deterministic branches, then connect every request type to the respondent outcome your team maintains.