# Qualyo Forms template knowledge Last verified: 2026-09-01 Template index: https://qualyoforms.com/templates Every template page exposes the decision it helps make, its policy, complete question blueprint, visible outcomes, customization guidance, and FAQs. 4 qualification presets include privacy-safe local policy simulations, and 3 routing presets include privacy-safe deterministic route choices. These examples create no leads or submissions and do not run form workflows, webhooks, emails, or AI. Blank intentionally displays no interactive preview and documents the available question, note, context, and routing building blocks instead. The saved visual graph remains authoritative; AI never redraws the route. ## Project inquiry Canonical page: https://qualyoforms.com/templates/project-inquiry Category: Sales qualification Included route: 10 questions → Hard rules + AI fit → Call, review, or alternative Interactive preview: a privacy-safe local policy simulation using representative response profiles. It creates no lead or submission, triggers no form workflow, webhook, or email, and makes no AI request. Start with an agency project qualification flow that captures scope, budget, timing, and fit, then routes each inquiry to a call, review, or alternative. ### Decision and qualification policy Decision: Should this project move to a strategy call, a team review, or another next step? The flow gathers the commercial and contextual signals an agency needs before it commits senior time to a discovery call. Policy: The example first routes Under $2k or Just exploring responses to the alternative ending. Responses that clear both hard gates continue to contextual fit evaluation, where uncertain or unsuitable context maps to Needs review. - Budget is not Under $2k. - Target start is not Just exploring. - The requested service and project brief fit the agency offer. - Contextual fit that does not earn calendar access goes to Needs review. Policy ownership: Your agency defines every service, threshold, fit criterion, fallback, and destination. The example policy is only a starting point. ### Exact included questions 1. **What’s your first name?** Makes the conversation personal without asking for unnecessary detail. 2. **What’s the best work email for you?** Creates a reliable follow-up channel for the project response. 3. **What company or organization is this for?** Adds the business context needed to review relevance and scale. 4. **What do you need help with?** Maps the inquiry to the services your team actually delivers. 5. **What are you trying to achieve?** Captures the outcome behind the request, not only a deliverable label. 6. **Which best describes the scope?** Separates a focused engagement from multi-phase or ongoing work. 7. **What budget range have you set aside?** Checks commercial fit using ranges that are easier to answer than an exact number. 8. **When would you like to get started?** Surfaces urgency and whether the timing matches current capacity. 9. **What role do you have in choosing a partner?** Shows whether the respondent can move the project forward or is still gathering options. 10. **Anything else we should know: links, constraints, or a current provider?** Leaves room for links, constraints, dependencies, and useful nuance without making it required. ### Route - Question path: Contact → service → outcome → scope → budget → timing → authority → context. - Qualification checkpoint: Compare the complete brief with your saved fit criteria. - Strong-fit route: Open the project-call destination. - Review or alternative: Send the brief to the team or provide another next step. ### Before publishing 1. **Replace the service menu.** Use your real offers and remove every option your team does not sell. 2. **Set honest project ranges.** Adjust budget and timing choices to match your minimum engagement and capacity. 3. **Write the fit policy.** Define what makes a project relevant, feasible, and ready for a conversation. Choose the automatic fallback used if AI is unavailable. 4. **Connect all three outcomes.** Send strong-fit projects to the calendar, place ambiguous inquiries in a needs-review queue, and give clear non-fits a respectful alternative. ### Frequently asked questions - **What is a project inquiry form?** A project inquiry form collects the contact, service, goal, scope, budget, timing, and decision context needed to review a potential project before the first call. It is more structured than a general contact form but lighter than a proposal or onboarding questionnaire. - **What questions should a project inquiry form include?** Start with contact and company details, then ask what service is needed, the desired outcome, project scope, budget range, preferred start date, decision role, and optional context. Keep a question only when its answer changes review, routing, or preparation for the next conversation. - **Is a project inquiry form the same as a client intake form?** Not necessarily. A project inquiry form usually comes before a prospect is accepted and helps assess fit. A client intake form is often used after acceptance to collect onboarding details, stakeholders, assets, systems, and working preferences. - **Can I customize the questions and qualification criteria?** Yes. The questions, options, wording, qualification criteria, visual route, branding, and endings are editable. Replace every example range and service with boundaries that reflect your own business. - **Does AI decide which question comes next?** No. The saved visual graph determines the question order and route. AI can personalize the wording of an already-selected question and evaluate the dedicated qualification checkpoint, but it does not control branching. The form owner also chooses the automatic fallback outcome. - **Can I embed this project inquiry form on my website?** Yes. A published Qualyo form can be shared by link or embedded on a website. The same questions and route remain in one form, so updates do not require rebuilding the workflow for every placement. ## Demo request Canonical page: https://qualyoforms.com/templates/demo-request Category: Sales qualification Included route: 9 questions → Hard rules + AI fit → Calendar, review, or nurture Interactive preview: a privacy-safe local policy simulation using representative response profiles. It creates no lead or submission, triggers no form workflow, webhook, or email, and makes no AI request. Start with a SaaS demo qualification flow that captures company, use-case, role, and timing, then routes each buyer to a demo, review, or self-serve path. ### Decision and qualification policy Decision: Should this buyer book a demo, enter sales review, or continue through a self-serve path? The flow turns a demo request into a buying-context record before the sales team commits time or assigns ownership. Policy: The example first routes Just researching or researching for someone else responses to the self-serve ending. Requests that clear both hard gates continue to contextual fit evaluation, where uncertain or unsuitable context maps to Needs review. - Timeline is not Just researching. - Decision role is not I’m researching for someone else. - The company and stated use case fit the product. - Contextual fit that does not earn demo access goes to Needs review. Policy ownership: Your team defines the segments, fit policy, review boundary, fallback, and destination. Company size alone never determines the result. ### Exact included questions 1. **What’s your first name?** Keeps later transitions personal while asking for only the detail the conversation needs. 2. **What’s your work email?** Provides a business follow-up channel and helps separate serious evaluations from anonymous traffic. 3. **What company do you work for?** Connects the request to an organization that the sales team can prepare for. 4. **How large is your company?** Adds useful operating scale without forcing the respondent to disclose revenue. 5. **What best describes your role?** Shows which part of the organization owns the problem and how the respondent sees it. 6. **What are you hoping to improve?** Maps the request to the outcome the buyer actually wants to improve. 7. **How do you currently handle inbound leads?** Reveals the current workflow, replacement context, and practical friction in the buyer’s own words. 8. **When are you looking to make a change?** Distinguishes an active evaluation from early research without pretending urgency alone proves fit. 9. **What role will you have in choosing a solution?** Clarifies whether the respondent decides, influences, or is collecting information for someone else. ### Route - Question path: Contact → company → role → goal → current process → timing → authority. - AI fit checkpoint: Evaluate the full request against your saved demo criteria. - Strong-fit route: Offer the product-demo calendar or a sales-owned next step. - Review or self-serve: Send the request to sales review or provide a useful non-calendar path. ### Before publishing 1. **Name the real use cases.** Replace the example goals with the outcomes and workflows your product can genuinely improve. 2. **Match your segments.** Adjust company-size and role choices to the segments your team recognizes and owns. 3. **Write the demo policy.** Define a relevant business, use case, timing, and buying role, then choose the automatic fallback route. 4. **Connect all three next steps.** Send strong-fit requests to the calendar, place ambiguous buyers in needs review, and give clear non-fits a useful self-serve path. ### Frequently asked questions - **What should a demo request form ask?** Ask for contact and company context, company size, role, primary goal, current process, evaluation timeline, and decision role. Keep only questions that change routing, ownership, or preparation for the conversation. - **Should a demo request form ask for company size?** Ask when size changes product fit, sales ownership, implementation needs, or the next step. Use ranges the respondent can answer quickly, and remove the question when it does not affect the workflow. - **Can I send qualified demo requests to a calendar?** Yes. The matching route can open an external scheduling destination. Qualyo does not advertise a native calendar integration, so the template uses a destination link that you replace. - **Does AI decide the demo-request route?** The visual graph decides the route. Optional AI can evaluate the saved qualification checkpoint, but it cannot choose the next question or redraw branching. The owner also selects an automatic fallback outcome. - **Can I customize every question and option?** Yes. Change the wording, choices, required fields, qualification criteria, presentation mode, branding, and all three outcomes before publishing. - **Can I embed the demo request form?** Yes. A published Qualyo form can be shared by hosted link or embedded on a website while keeping the same questions and route. ## Discovery call Canonical page: https://qualyoforms.com/templates/discovery-call Category: Sales qualification Included route: 9 questions → Hard rules + AI fit → Call, review, or resource Interactive preview: a privacy-safe local policy simulation using representative response profiles. It creates no lead or submission, triggers no form workflow, webhook, or email, and makes no AI request. Start with a consultant discovery qualification flow that captures need, urgency, investment, and authority, then routes each inquiry to a call, review, or preparation path. ### Decision and qualification policy Decision: Is this inquiry ready for a strategy call, a closer review, or a different next step? The flow gathers enough context to protect both sides of the calendar without asking the prospect to complete a miniature consulting engagement. Policy: The example first routes advice-only or no-authority responses to the preparation ending. Inquiries that clear both hard gates continue to contextual engagement-fit evaluation, where uncertain or unsuitable context maps to Needs review. - Investment readiness is not No, just looking for advice. - Decision role is not I’m not involved in the decision. - The challenge and desired outcome fit the consulting offer. - Contextual fit that does not earn call access goes to Needs review. Policy ownership: Your practice defines readiness, fit, exclusions, fallback, and every destination. The example is not a universal definition of a qualified consulting lead. ### Exact included questions 1. **What’s your first name?** Creates a human opening without adding unnecessary identity fields. 2. **What’s your work email?** Provides a reliable channel for the application outcome and any follow-up. 3. **What company or business are you building?** Places the challenge inside a real operating context. 4. **What best describes your role?** Clarifies the respondent’s responsibility and perspective on the work. 5. **What would make this engagement successful?** Defines what a successful engagement would need to change or produce. 6. **What is getting in the way today?** Surfaces the obstacle that makes outside help relevant now. 7. **When do you want to start working on this?** Separates active priorities from open-ended exploration. 8. **If there is a fit, are you prepared to invest in expert support?** Tests whether paid expert support is a plausible next step without asking for an exact budget. 9. **Who will decide whether to move forward?** Shows whether the respondent can authorize an engagement or needs other stakeholders involved. ### Route - Question path: Contact → business → role → outcome → challenge → urgency → investment → authority. - AI fit checkpoint: Evaluate the full application against your saved engagement criteria. - Suitable route: Offer the strategy-call calendar or another consultant-owned step. - Review or preparation: Send the inquiry to the consultant or share a useful preparation path. ### Before publishing 1. **Name the engagement.** Replace generic strategy language with the problem and outcome your consulting offer is built to address. 2. **Set readiness signals.** Adjust urgency and investment language so it reflects how your clients actually buy expert support. 3. **Write the fit policy.** Define relevant challenges, required authority, timing, and exclusions, then choose the automatic fallback. 4. **Design the alternative.** Give early or unsuitable applicants a useful resource, later path, or clear review message instead of a dead end. ### Frequently asked questions - **What is a discovery call form?** A discovery call form collects the business context, desired outcome, current obstacle, urgency, readiness, and decision ownership needed to decide whether a live conversation is useful. - **What questions should I ask before a strategy call?** Ask what the respondent is building, what success looks like, what is blocking progress, when they want to act, whether paid support is realistic, and who decides. Remove any question that does not change fit or preparation. - **Should I ask for budget before a discovery call?** Ask about investment readiness or a relevant range when it materially affects fit. Use plain language, explain the reason through the flow, and avoid collecting a precise number when a range is sufficient. - **Can the form route suitable applicants to my calendar?** Yes. Connect the suitable route to an external scheduling destination and replace the placeholder URL before publishing. - **Does AI choose who gets a call?** Optional AI evaluates your written criteria at a dedicated checkpoint. The saved graph controls branching, and you choose the automatic outcome used if AI is unavailable. Review criteria carefully and avoid treating AI output as a guaranteed score. - **Can I use the template without AI?** Yes. Replace the qualifier with fixed Logic routes or a manual-review ending, and publish the form as a fully static workflow. ## Paid-ad lead Canonical page: https://qualyoforms.com/templates/paid-ad-lead Category: Inbound routing Included route: 8 questions → Hard rules + AI fit → Calendar, review, or nurture Interactive preview: a privacy-safe local policy simulation using representative response profiles. It creates no lead or submission, triggers no form workflow, webhook, or email, and makes no AI request. Start with a paid-ad lead qualification flow that captures campaign intent and business context, then routes each lead to sales, review, or the promised resource. ### Decision and qualification policy Decision: Should this campaign lead move to sales, enter review, or receive the promised resource? The flow preserves campaign momentum while collecting only the signals that change delivery, ownership, or the next step. Policy: The example first routes Just researching responses, by timing or decision role, to nurture. Responses that clear both hard gates continue to contextual campaign-fit evaluation, where uncertain or unsuitable context maps to Needs review. - Timeline is not Just researching. - Decision role is not I’m researching. - The company, selected offer, and problem fit the campaign. - Contextual fit that does not earn a sales step goes to Needs review. Policy ownership: Your campaign defines the audience, intent policy, fallback, and next steps. The flow does not infer a universal sales-ready lead. ### Exact included questions 1. **What’s your first name?** Adds a personal transition without increasing the form’s cognitive load. 2. **Where should we send your recommendation?** Creates the delivery and follow-up channel promised by the campaign. 3. **What company do you work for?** Establishes that the response belongs to a business context. 4. **How large is your company?** Adds a lightweight segment signal for routing and follow-up. 5. **What brought you here today?** Connects the lead to the specific promise or action that earned the click. 6. **What is the main problem you want to solve?** Identifies the problem the respondent wants to solve in a fast, scannable choice. 7. **When do you want to address this?** Separates near-term action from research without adding a long readiness questionnaire. 8. **What role do you have in choosing a solution?** Shows whether the respondent decides, influences, or is gathering information. ### Route - Question path: Contact → company → size → offer → problem → timing → authority. - AI fit checkpoint: Evaluate the complete response against the campaign’s saved ICP and intent criteria. - Sales-ready route: Open an assessment, calendar, or other high-intent destination. - Review or nurture: Send the response to the team or deliver the promised resource. ### Before publishing 1. **Mirror the ad promise.** Use the same offer and vocabulary the respondent saw before clicking so the transition feels continuous. 2. **Keep only route signals.** Remove every field that does not change delivery, qualification, ownership, or follow-up. 3. **Write the campaign fit policy.** Define the target business, relevant problem, intent, timing, and automatic fallback without inventing certainty. 4. **Honor all three outcomes.** Connect sales-ready leads to a human next step, place ambiguous responses in review, and deliver the promised nurture resource to clear non-fits. ### Frequently asked questions - **What should a paid-ad lead form include?** Include the promised delivery channel, business context, campaign interest, main problem, timing, and decision role. Keep the form short and retain only fields that change the next step. - **How long should a lead generation form be?** There is no universal field count. This preset uses eight focused questions, but the right length is the smallest set that supports delivery and routing without breaking the campaign promise. - **Can different leads see different endings?** Yes. Route sales-ready responses to a calendar or assessment and earlier-stage responses to the promised resource or nurture handoff. - **Does this replace campaign tracking?** No. The template structures and routes the form response. Keep your advertising, attribution, consent, and lifecycle systems configured separately. - **Can I customize it for LinkedIn or Google Ads?** Yes. Replace the offer, audience, problem choices, criteria, and ending destinations so they match the exact campaign and channel. - **Can I use deterministic rules instead of AI?** Yes. Use choice branches or Logic cards for explicit segment and intent rules, or route every response to manual review. AI qualification is optional. ## Inbound routing Canonical page: https://qualyoforms.com/templates/inbound-routing Category: Inbound routing Included route: 5–7 questions → 5 deterministic destinations Interactive preview: a privacy-safe deterministic route choice. It creates no lead or submission, triggers no form workflow, webhook, or email, and makes no AI request. Start with a multi-path inbound routing flow that separates sales, support, partnership, careers, and general inquiries before showing each respondent a defined next step. ### Decision and qualification policy Decision: 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. Policy: 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. - The inquiry type selects the path. - Every path collects request details before routing. - Only sales or project inquiries receive budget and timeline questions. - Each inquiry type has one explicit external destination or confirmation ending. Policy ownership: Your team defines the inquiry types, external resources, calendars, and confirmation copy. Completed responses remain available in Qualyo; configured form-level notifications and webhooks can separately deliver all completed submissions. ### Exact included questions 1. **What’s your first name?** Gives the completed response a useful personal reference. 2. **What’s the best email for a reply?** Provides a reliable reply channel for every inquiry path. 3. **What company or organization are you with?** Adds business context without deciding the route by itself. 4. **What are you contacting us about?** Selects the deterministic path and prevents irrelevant follow-up questions. 5. **What should the right team know?** Collects the context needed for later follow-up from the response stored in Qualyo. 6. **What budget range are you working with?** Adds a practical project constraint only on the sales or project path. 7. **When would you like to move forward?** Adds timing context only when the inquiry is about a potential engagement. ### Route - 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. ### Before publishing 1. **Name the real request types.** Keep only the inbound categories your organization can recognize and own. 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. 3. **Keep questions path-specific.** Ask budget and timing only where they change the sales or project route. 4. **Test every destination.** Run all five paths and replace every placeholder before publishing the flow. ### Frequently asked questions - **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. ## Service-specific routing Canonical page: https://qualyoforms.com/templates/service-routing Category: Inbound routing Included route: 6 questions → 5 deterministic service destinations Interactive preview: a privacy-safe deterministic route choice. It creates no lead or submission, triggers no form workflow, webhook, or email, and makes no AI request. Start with a service-specific lead routing flow that captures the requested service and brief, then presents a calendar, resource, or tailored confirmation ending. ### Decision and qualification policy Decision: Which respondent-facing outcome should this service inquiry receive? The flow asks the prospect to select a service line, gathers one useful brief, and uses that explicit choice to make the visible next step predictable. Policy: This template is deterministic service routing, not contextual lead qualification. The selected service line chooses the respondent destination or confirmation ending, while request details and timing remain part of the completed response. - Every public service line maps to one external destination or confirmation ending. - The selected service line controls the route. - Request details and timing remain in the Qualyo response but do not override the choice. - Unrecognized requests finish with a general service review confirmation. Policy ownership: Your team replaces every example service line, calendar, resource, review confirmation, and ending. Completed responses remain available in Qualyo; configured form-level notifications and webhooks can separately deliver all completed submissions. ### Exact included questions 1. **What’s your first name?** Gives the completed response a useful personal reference. 2. **What’s the best email for a reply?** Provides a reliable reply channel for the service inquiry. 3. **What company or organization are you with?** Adds organization context to the completed response. 4. **Which service do you need?** Selects the deterministic respondent outcome without AI interpretation. 5. **What should the team know about your request?** Collects a useful brief for later follow-up from the response stored in Qualyo. 6. **When would you like to move forward?** Adds timing context without changing the selected service route. ### Route - Question path: Contact → service line → request details → target timeline. - Deterministic service route: The saved service-line choice controls the respondent destination or confirmation. - Five service-specific outcomes: Design calendar, growth confirmation, content brief, strategy calendar, or general confirmation. ### Before publishing 1. **List only real services.** Replace the example choices with service lines your team actively sells and supports. 2. **Define every outcome.** Choose an external calendar or resource, or write a tailored confirmation ending. Configure notifications and webhooks separately at the form level when completed submissions need delivery. 3. **Keep the brief concise.** Collect only the details needed for later follow-up from the completed response. 4. **Test every route.** Run each service choice and the unmatched route before publishing the workflow. ### Frequently asked questions - **What is service-specific lead routing?** It asks which service a prospect needs, collects a useful brief, and presents a predefined calendar, resource, or tailored confirmation ending. The completed response remains available in Qualyo. - **Does this flow use AI to choose the service?** No. The respondent selects the service line and deterministic routing follows that explicit choice. Request details and timing remain with the response but do not reinterpret the route. - **Can I replace every example service line?** Yes. Replace the labels, questions, calendars, resources, review confirmations, and endings with the way your team actually operates. Configure any submission delivery separately at the form level. - **What happens when no service matches?** The Another service path shows a general review confirmation. The completed response remains available in Qualyo for later follow-up. - **Can different services use different kinds of destinations?** Yes. One service can open an external calendar, another can show a review confirmation, and another can provide a service-specific brief or resource. - **Does the local preview create a lead?** No. It changes only the visible example outcome on this page. It creates no submission, sends no webhook or email, and makes no AI request. ## Customer onboarding Canonical page: https://qualyoforms.com/templates/customer-onboarding Category: Operational intake Included route: 10 questions → Preference route → Calendar or guide Interactive preview: a privacy-safe deterministic route choice. It creates no lead or submission, triggers no form workflow, webhook, or email, and makes no AI request. Start with a customer onboarding flow that captures setup context after the sale, then routes each customer to a live kickoff or self-serve guide. ### Decision and qualification policy Decision: Does this customer want a live kickoff or a self-serve setup path? The workflow gathers delivery context after the sale, then follows the customer's explicit support preference. Policy: No lead qualification is required. The saved flow uses a deterministic answer rule because the customer has already been accepted. - The purchased package determines the setup context. - The customer names the first goal and implementation owner. - The kickoff preference controls the final route. Policy ownership: Your delivery team defines the packages, setup questions, support choices, and destinations. Do not reuse this post-sale policy for prospect qualification. ### Exact included questions 1. **What’s your first name?** Makes the setup experience personal without repeating unnecessary account data. 2. **What’s your work email?** Provides a dependable channel for setup materials and kickoff details. 3. **What company are we onboarding?** Connects the onboarding response to the customer organization. 4. **Which plan or package did you choose?** Identifies the purchased scope so the handoff can reflect what was actually sold. 5. **How many people will use the product?** Signals the number of people who may need access, training, or rollout support. 6. **What is the first outcome you want to achieve with [Product]?** Centers onboarding on the first outcome the customer wants to achieve. 7. **Which tools are already part of your workflow?** Surfaces workflow dependencies and likely handoff or integration context. 8. **When would you like to be up and running?** Sets a practical target for setup without inventing urgency. 9. **Who will own implementation day to day?** Names the person responsible for day-to-day progress and coordination. 10. **Would a kickoff call help?** Creates a deterministic route between a live kickoff and a self-serve setup guide. ### Route - Question path: Contact → package → team → goal → tools → timing → owner → preference. - Preference route: Read the saved kickoff choice with deterministic logic. - Kickoff requested: Open the external kickoff calendar with context already collected. - Self-serve requested: Confirm onboarding and deliver the setup guide. ### Before publishing 1. **Match the purchased offer.** Replace the example plans with the packages or services customers can actually arrive from. 2. **Define the first outcome.** Tune the goal and timeline questions to the milestones your onboarding team can support. 3. **Name the handoff owner.** Ask for the customer-side owner and connect notifications or webhooks to the right internal team. 4. **Connect both preferences.** Replace the calendar placeholder and attach the correct guide, checklist, or confirmation to the self-serve route. ### Frequently asked questions - **What is a customer onboarding form?** A customer onboarding form collects the goals, package, team, tools, timeline, implementation owner, and setup preference needed to begin delivery after a purchase or accepted engagement. - **What questions should a client onboarding form include?** Ask what was purchased, who will use it, the first desired outcome, existing tools, target launch timing, implementation owner, and preferred kickoff path. Add only information the delivery team will use. - **Is this the same as a project inquiry form?** No. A project inquiry happens before acceptance and helps evaluate fit. Customer onboarding happens after the sale and gathers the context needed to deliver the agreed product or service. - **Does the onboarding template use AI qualification?** No. The included route uses deterministic logic on the customer’s kickoff preference. AI wording can be enabled separately, but it does not control the route. - **Can customers choose between a call and a guide?** Yes. The included preference question connects “Yes, book me in” to a calendar destination and the other answer to a setup-guide ending. Both can be edited. - **Can I send onboarding answers to another system?** Yes. Every plan supports webhooks for complete submission payloads. Qualyo does not replace a customer-success or project-management system. ## Blank form Canonical page: https://qualyoforms.com/templates/blank Category: Build from scratch Included route: Intro → End Interactive preview: none. The blank preset contains no questions, so its page explains the available building blocks instead of displaying a form. Start with a blank qualification-flow canvas, then add your own questions, criteria, outcomes, routes, and destinations around the decision your business needs to make. ### Decision and qualification policy Decision: What should this qualification flow decide? Start with the business decision, then add the smallest set of questions, rules, outcomes, and destinations needed to make it operational. Policy: The blank canvas includes no preset qualification policy. It begins with a connected welcome and ending so you can model your own workflow without deleting assumptions. - Define the hard requirements that need fixed rules. - Identify any contextual judgment that genuinely needs AI or review. - Choose the fallback and destination for every outcome. Policy ownership: Every criterion and route belongs to you. Qualyo does not supply a universal definition of a qualified lead. ### Exact included questions This preset intentionally includes no questions and displays no demo form. It connects a welcome directly to an ending. Owners can add short answers, long answers, email, phone, number, single-choice, multiple-choice, dropdown, file-upload, and signature questions; respondent-facing welcome notes, question helper text, and ending messages; private AI context; Logic, Qualifier, Router, and additional End cards. ### Route - Question path: No preset questions: the canvas is ready for your own fields and routes. - Connected ending: A simple confirmation screen ready to rewrite or replace. ### Before publishing 1. **Name the decision.** Write the single job this form must complete and the people who will respond. 2. **Add useful questions.** Create the smallest set of fields needed to route, review, or prepare the next step. 3. **Draw explicit routes.** Use fixed logic for clear rules and optional qualification only when open context needs judgment. 4. **Write every ending.** Give each path an honest confirmation, destination, resource, or handoff before publishing. ### Frequently asked questions - **What does the blank form template include?** It includes a connected welcome card and confirmation ending on the visual canvas, plus the standard form settings and publishing controls. It intentionally includes zero questions. - **Can I add questions and branching?** Yes. Add Question, Logic, Qualifier, Router, and End cards, then connect them into the route the respondent should follow. - **Can a blank form be conversational or classic?** Yes. Both presentation modes use the same saved questions, validation, and route graph, so you can change the respondent experience without rebuilding the workflow. - **Do I need AI to build from scratch?** No. A form can remain fully static with fixed questions and Logic routes. AI personalization, qualification, and summaries are optional. - **When should I use a complete template instead?** Choose a complete template when its questions and route already resemble your operating workflow. Start blank when removing those assumptions would take longer than adding your own structure. - **Can I duplicate and edit the blank template on Free?** Yes. Templates, static forms, and submissions are available on Free. AI-assisted respondent journeys use the plan’s AI allowance.