# Qualyo Forms: full public context Generated from reviewed typed registries. Last verified: 2026-09-01. Last verified: 2026-09-01 Canonical website: https://qualyoforms.com Support and corrections: support@qualyoforms.com ## What Qualyo is Qualyo is a **lead qualification platform**. Its core promise is: **Turn inbound leads into qualified opportunities.** Qualyo sits between inbound demand and the sales process. It captures the context needed to assess an inquiry, evaluates that context against the customer's own qualification criteria, determines an outcome, and routes the prospect to the right next step. A form is the lead-facing interface through which qualification happens, not Qualyo's primary product category. The central positioning is: **You define what good looks like. Qualyo does the qualification.** Supporting language includes **Forms collect answers. Qualyo turns them into qualification decisions.** ## The problem Qualyo solves Many businesses use a basic form and calendar to send nearly every inquiry to a discovery or sales call. Budget, scope, timing, authority, need, and customer fit are discovered during that call, after valuable founder or sales time has already been committed. Manual pre-call qualification is often inconsistent or skipped. Qualyo moves the qualification decision before the call. Better-fit prospects can receive a fast path to the appropriate conversation, while early-stage, unclear, or out-of-scope inquiries can receive review, follow-up, a resource, a referral, an alternative offer, or a respectful decline. ## Capture -> Qualify -> Route - **Capture:** Gather only the context needed to determine fit or prepare the next human conversation. - **Qualify:** Evaluate that context against criteria defined by the customer. Use deterministic rules for explicit requirements and optional AI for nuanced judgment. - **Route:** Send each prospect to the next step configured for the resulting outcome. There is no universal definition of a qualified lead. Criteria can include budget, company size, industry, location, project scope, timeline, need, authority, and buying intent. **The customer defines what a qualified lead means. Qualyo identifies those leads automatically.** AI is optional. It may personalize the wording of an already-selected question, evaluate owner-written qualification criteria, or generate a response summary. It does not rewrite the saved graph or independently define what a good lead means. Every AI Qualifier stores an owner-selected automatic qualify or disqualify fallback, so provider or allowance failure follows an explicit path. ## Ideal customer profile Primary ICP: **Agencies and high-ticket service businesses with meaningful inbound demand, variable lead quality, and valuable founder or sales time.** The strongest initial segments are web, design, marketing, branding, and development agencies; consultants and specialist consultancies; and other high-value B2B service businesses with meaningful differences in budget, scope, timing, intent, or fit across inbound inquiries. Read the dedicated [ICP and problem knowledge](https://qualyoforms.com/knowledge/icp.md) for buyer roles, behavioral signals, buying triggers, desired outcomes, and poor-fit conditions. ## Core capabilities - Conversational and classic delivery from the same saved questions, validation, and routes. - Visual intro, question, condition, qualifier, router, and ending nodes connected by ordered edges. - Choice routing and deterministic Logic cards for fixed rules. - Optional AI qualification and question personalization with an explicit fallback. - Public hosted links plus inline, full-page, popover, and banner embeds. - Analytics for verified views, completed submissions, conversion rate, daily trends, countries, devices, and traffic sources. - CSV export, email notifications, file-upload questions, and drawn-signature questions. - Webhooks and unlimited email-notification recipients on every plan; paid custom domains, logo upload, branding removal, and fast AI mode. - Public API v1 with 14 account, workspace, form, submission, analytics, schema, and health operations. - MCP connections with the same 14 operations as agent-friendly tools, available through OAuth or manual tokens. - Templates for demo requests, project inquiries, discovery calls, paid-ad leads, multi-path inbound routing, service-specific lead routing, customer onboarding, and a blank flow. - Submission start/end dates, a total response cap, and respondent back navigation. ## Plans and metering | Plan | AI conversations | Allowance cadence | Monthly USD | Annual USD | Availability | | --- | ---: | --- | ---: | ---: | --- | | Free | 50 | Lifetime | $0 | $0 | Public | | Pro 250 | 250 | Per month | $49 | $490 | Purchasable | | Pro 750 | 750 | Per month | $99 | $990 | Purchasable | | Pro 2,000 | 2,000 | Per month | $199 | $1,990 | Purchasable | | Pro 5,000 | 5,000 | Per month | $399 | $3,990 | Purchasable | | Legacy Pro | Unlimited | No limit | Not publicly sold | Not publicly sold | Existing eligible subscribers only | One respondent journey counts once after its first successful AI request. Later AI turns in that journey are included. Static forms and submissions are unlimited. Free includes 50 lifetime AI conversations and does not reset. Paid allowances reset each calendar month, do not roll over, and do not create automatic overage charges. Annual plans bill once yearly at ten times the corresponding monthly price. ## Capability gates Free includes one workspace, unlimited notification recipients, hosted links and embeds, templates, visual logic, form modes, analytics, CSV export, 15 MB file uploads, drawn signatures, webhooks, AI qualification, and AI personalization. Paid plans add custom domains, logo upload, branding removal, fast AI mode, and no configured workspace limit. ## Important product boundaries - Qualyo is not a built-in CRM or Kanban pipeline. - External CRM and automation workflows are webhook-based unless a page explicitly documents a native integration. - Qualyo supports private file-upload responses and drawn-signature questions. Each file is limited to 15 MB; a submission is limited to 10 files and 25 MB total. - Qualyo does not provide payment collection, contract generation, managed legal e-signature workflows, or invoicing. - There is no direct importer from competitor form platforms. - External calendars are linked from an ending; there is no advertised native calendar integration. - AI output is not a guaranteed score or conversion prediction and should not be the sole basis for a consequential decision. ## Best fit Agencies and high-ticket service businesses that need to qualify inbound leads before committing founder, sales, or delivery time. Broader applicable workflows include agencies, consultants, SaaS sales teams, recruiters, coaches, and freelancers when answers should change the path, outcome, or quality of a subsequent human conversation. ## Poor fit Qualyo is a weak primary fit for very small or low-volume businesses whose inbound leads are already qualified, teams that need only a basic survey, or organizations whose central requirement is a built-in CRM, payment workflow, managed document signing, a large native-integration marketplace, or enterprise controls not documented by Qualyo. ## Public source hierarchy 1. Current deployed product and hosted schema/function state. 2. Versioned database migrations and server enforcement. 3. Typed billing, product, use-case, and comparison registries in the repository. 4. Current public pages and checkout. 5. Generated knowledge files such as this one. If a generated file and the current product disagree, report the exact URL and evidence to support@qualyoforms.com. Do not infer a feature from a historical implementation plan. Last verified: 2026-09-01 Canonical website: https://qualyoforms.com Canonical product knowledge: https://qualyoforms.com/knowledge/qualyo.md ## Category and promise Qualyo is a **lead qualification platform**. Its core promise is: **Turn inbound leads into qualified opportunities.** One-sentence positioning: Qualyo helps agencies and high-ticket service businesses define what a good lead looks like, automatically qualify every inbound inquiry, and route each prospect to the right next step before valuable sales time is spent. The form is the prospect-facing experience. The product is the customer-controlled qualification and routing system behind it. ## Core problem The common inbound workflow is: **Inquiry -> basic form -> calendar -> discovery or sales call -> discover whether the lead fits** This postpones basic qualification until an expensive human interaction. Founders and salespeople use calls to learn whether the prospect has an appropriate budget, relevant scope, realistic timeline, genuine need, decision authority, and fit with the company's ideal customer profile. Manual pre-call review is often inconsistent or skipped, so strong and weak inquiries receive the same path. Qualyo changes the workflow to: **Inquiry -> qualification flow -> customer-defined fit decision -> appropriate next step** The problem is not simply a lack of time to inspect submissions. It is that the business has not operationalized its definition of a qualified lead before the sales process begins. ## Primary ideal customer profile Agencies and high-ticket service businesses with meaningful inbound demand, variable lead quality, and valuable founder or sales time. ### Strongest segments - Web, design, marketing, branding, and development agencies. - Consultants and specialist consultancies selling high-value B2B services. - Other service businesses with minimum requirements for budget, scope, timing, industry, or geography. The current commercial wedge is especially strong for founder-led or owner-led web, design, marketing, branding, and development agencies. This is a go-to-market focus, not a restriction on who can use the product. ### Defining business traits - The business sells a relatively high-value service that normally requires a discovery, project, or sales conversation. - It receives enough inbound interest for inconsistent lead quality to create a recurring cost. - Its definition of fit includes meaningful boundaries such as budget, scope, service, industry, geography, timing, authority, need, or intent. - Prospects currently reach a calendar or human follow-up before those boundaries are consistently evaluated. - Founder or sales time has meaningful economic value. - Different inquiry types should receive different outcomes instead of one generic thank-you page. Company size is secondary to these behaviors. A smaller company with recurring, mixed-quality inbound demand can be a strong fit. A larger company with low inbound volume or already-qualified leads can be a weak fit. ## Buyer, operator, beneficiary, and respondent - **Economic buyer:** Founder, agency owner, managing director, sales or revenue lead, or another leader accountable for the value of sales time. - **Product operator:** Founder, marketer, sales operator, account manager, consultant, or client-experience lead who defines criteria and routes. - **Internal beneficiary:** The salesperson, consultant, strategist, recruiter, or delivery lead who receives better-qualified and better-prepared opportunities. - **Respondent:** The prospective customer completing the lead-facing qualification experience. ## Job to be done > When an inbound prospect asks for help, determine whether the opportunity fits before committing sales time, then give that prospect the appropriate next step. ## Behavioral and pain signals - Prospects can book calls before the business knows their budget, scope, timing, or fit. - Qualification is manual, inconsistent, or skipped. - A meaningful share of inbound inquiries should not receive the same sales path. - Founders or salespeople spend economically valuable time discovering basic fit on calls. - The business needs qualified, early-stage, unclear, and out-of-scope inquiries to receive different outcomes. Common prospect language includes: - "Too many people can book directly onto my calendar." - "We only discover the budget or real scope during the call." - "A lot of inquiries are not relevant to what we offer." - "I manually inspect every submission." - "Good leads and bad leads currently receive the same experience." - "We spend too much time on calls that never had a realistic chance of progressing." ## Buying triggers - Inbound lead volume increases. - The business launches paid acquisition or another demand-generation channel. - A public booking calendar begins filling with weak-fit calls. - The company raises its minimum engagement size or narrows its ICP. - A founder's calendar becomes a growth constraint. - The business hires its first salesperson or formalizes a sales process. - Discovery-call-to-opportunity conversion is weaker than expected. - The team needs separate paths for qualified, early-stage, unclear, and out-of-scope inquiries. ## Qualification ownership There is no universal Qualyo score and no universal definition of qualified. The customer defines qualification according to its ICP, economics, capacity, constraints, sales process, and goals. - Use deterministic rules where certainty matters, such as a minimum budget, service selection, location, or explicit timeline. - Use optional AI where interpretation is useful, such as evaluating an open-ended project description against owner-written criteria. - Keep routes, outcomes, and failure behavior under customer control. - Do not describe AI as autonomously deciding who deserves access to a service or as the sole basis for a consequential decision. ## Desired outcomes - Fewer unqualified calls and less manual lead review. - Faster attention for strong inbound opportunities. - Better-prepared discovery, sales, and project conversations. - Consistent application of the customer's own qualification policy. - Less repetitive follow-up to collect missing context. - A clear and truthful next step for every inquiry. The economic value is protection of valuable founder and sales time, plus faster handling of good opportunities. Qualyo should not be sold primarily as cheaper form software. ## Differentiation Traditional forms and calendars collect answers for a human to interpret. Qualyo collects context, evaluates fit, determines an outcome, and routes the lead. Qualyo operationalizes the qualification decision. - **Forms collect answers. Qualyo turns them into qualification decisions.** - **You define what good looks like. Qualyo does the qualification.** - **Do not sell the form. Sell the qualified opportunity.** Qualyo complements calendars, CRMs, and sales workflows. It is the qualification layer before those systems, not a replacement for every downstream tool. ## Poor fit and anti-ICP - Very small or low-volume businesses whose inbound inquiries are already qualified. - Teams that only need a basic survey or generic data-collection form. - Teams that primarily need a built-in CRM, payment workflow, or managed contract-signing product. - Organizations that require undocumented enterprise controls or a large native-integration marketplace. The clearest anti-ICP is a very small, low-volume business whose few inbound inquiries are already qualified and whose manual review cost is negligible. ## Broader applicable audiences Qualyo can also support coaches, consultants, freelancers, recruiters, and SaaS sales teams. These are valid use cases when answers should change a prospect's route or prepare a valuable human conversation. The homepage and category should remain broad enough for that expansion, while agencies and high-ticket service businesses remain the strongest initial proof audience. ## Language guidance Lead with lead qualification, qualified opportunities, qualification flow, qualification criteria, qualification rules, AI qualification, lead fit, inbound opportunities, qualification outcomes, and routing. Conversational forms, visual design, AI-assisted wording, submissions, and data collection are product details, not the primary category. Support and corrections: support@qualyoforms.com Last verified: 2026-09-01 Canonical pricing page: https://qualyoforms.com/#pricing Currency: USD | Plan | AI conversations | Allowance cadence | Monthly USD | Annual USD | Availability | | --- | ---: | --- | ---: | ---: | --- | | Free | 50 | Lifetime | $0 | $0 | Public | | Pro 250 | 250 | Per month | $49 | $490 | Purchasable | | Pro 750 | 750 | Per month | $99 | $990 | Purchasable | | Pro 2,000 | 2,000 | Per month | $199 | $1,990 | Purchasable | | Pro 5,000 | 5,000 | Per month | $399 | $3,990 | Purchasable | | Legacy Pro | Unlimited | No limit | Not publicly sold | Not publicly sold | Existing eligible subscribers only | ## Billing rules - Static forms and submissions are unlimited on every current plan. - One respondent flow counts once after its first successful AI invocation; later AI turns in the same flow are included. - Free's 50-conversation allowance is lifetime-scoped and does not reset. - Paid AI allowances reset each calendar month. - Unused AI conversations do not roll over. - There are no automatic AI overage charges. - When AI is unavailable or the allowance is used, the static form continues and each Qualifier follows its saved automatic fallback. - Annual plans bill once per year at ten times the monthly price: two monthly prices less than paying monthly for twelve months. - Taxes, currency presentation, proration, renewal, and cancellation timing are shown by Stripe before confirmation where applicable. - Legacy Pro is not offered to new customers. Eligible existing subscribers may retain it until cancellation or selection of a current plan. ## Free capability boundary Free includes 50 lifetime AI conversations, unlimited static forms and submissions, one workspace, unlimited notification recipients, hosted links and embeds, templates, visual branching, custom endings, analytics, CSV export, 15 MB file uploads, webhooks, AI qualification, and AI personalization. ## Paid capability boundary Every current Pro bundle adds custom domains, logo upload, removal of Qualyo branding, fast AI mode, and no configured workspace limit. Webhooks and unlimited notification recipients are included on every plan. The four Pro bundles differ by monthly AI-conversation allowance and price. ## Buying guidance Start with Free when the workflow can be built and tested within 50 lifetime AI-assisted respondent journeys or can remain fully static. Select the smallest Pro bundle that matches expected successful AI-assisted journeys. Do not count static submissions as AI usage, and do not describe a larger bundle as adding unrelated product features. Questions about billing errors or a refund request go to support@qualyoforms.com. Qualyo does not publish a blanket refund promise. Last verified: 2026-09-01 Use-case index: https://qualyoforms.com/use-cases These guides describe practical workflows without invented customer quotes, conversion percentages, or outcome guarantees. The recurring method is: define the boundary, collect only useful context, express fixed routes directly, add optional AI judgment with a fallback, and give every route a deliberate ending. ## Agencies Canonical page: https://qualyoforms.com/use-cases/agencies Template: https://qualyoforms.com/templates/project-inquiry Discovery priority: Primary use case Qualify project inquiries against your agency's own commercial and delivery criteria before they reach the calendar. ### Qualification policy For a web agency, a qualified project might require a supported project type, a minimum budget, a realistic timeline, and a business that fits the agency's target client profile. - Supported project type - Minimum project budget - Realistic delivery timeline - Target client profile Policy ownership: These are example criteria, not Qualyo defaults. Your agency defines what qualified means and can change every rule, judgment, and destination. ### Recommended questions - **What outcome are you trying to create?** Reveals the job behind the requested deliverable. - **Which services do you expect to need?** Surfaces scope alignment before a call. - **What budget range has been approved or discussed?** Establishes a practical constraint without asking for false precision. - **When does the work need to begin?** Separates immediate projects from exploratory planning. - **Who will participate in the decision?** Clarifies the buying process and stakeholders. - **What would make the project successful?** Creates context for qualification and the first conversation. ### Decision logic - **Apply explicit project boundaries:** Use fixed rules for service scope, minimum budget, geography, or timing when the answer has a clear business consequence. - **Interpret the project context:** Use optional AI only where the brief needs contextual judgment, such as whether the problem and requested work align with the agency's expertise. - **Choose the next step:** Send a strong fit to a strategy call, an uncertain fit to team review, and an out-of-scope inquiry to a useful alternative. ### Route outcomes - **If:** Service, budget, and timing match the agency’s published engagement boundary **Then:** Strong fit → Strategy call. The team has enough context to evaluate the opportunity live. - **If:** Project fit is plausible but timing, scope, or decision context is uncertain **Then:** Needs review → Team review. The agency can resolve uncertainty before anyone promises a call. - **If:** A firm budget, service, geography, or timing boundary does not match **Then:** Not qualified → Alternative outcome. The response stays respectful and offers a transparent next step. ### Product boundaries - Qualyo does not provide a native CRM or calendar integration; use an ending link or a webhook on any plan. - There is no direct importer from another form platform. - File uploads and drawn-signature questions are supported; payment collection and contract e-signature workflows are not. ## Consultants Canonical page: https://qualyoforms.com/use-cases/consultants Template: https://qualyoforms.com/templates/discovery-call Discovery priority: Primary use case Capture the decision context that turns a vague consulting inquiry into a useful first conversation. ### Qualification policy A qualified consulting opportunity might involve a problem the practice can solve, an accountable decision owner, feasible timing, sufficient scope, and a commercial range that fits the engagement model. - Problem and expertise fit - Decision ownership - Scope and business impact - Timing and commercial fit Policy ownership: These criteria belong to the consultant or service business. Qualyo applies the policy you save and leaves uncertain opportunities available for review. ### Recommended questions - **What business problem needs attention?** Identifies the issue without assuming the solution. - **What is the cost or impact of leaving it unchanged?** Adds importance and urgency context. - **What work has already been attempted?** Prevents repeating approaches without context. - **Who owns the decision and who else is involved?** Makes authority and stakeholders visible. - **What timing or deadline matters?** Surfaces delivery feasibility. - **What investment range is available?** Sets a practical engagement boundary. ### Decision logic - **Enforce explicit engagement limits:** Use fixed rules for geography, minimum scope, availability, or another requirement with an unambiguous answer. - **Interpret business context:** Use optional AI when problem fit, urgency, and likely impact need to be considered across several answers. - **Match the next action:** Invite a strong fit to discovery, request review when material context is missing, or provide a clear resource or referral. ### Route outcomes - **If:** Problem, authority, scope, timing, and commercial context align **Then:** Strong fit → Discovery call. The first call can examine fit instead of collecting basic facts. - **If:** Potential fit remains but material context is missing **Then:** Needs review → Context request. The prospect knows exactly what is needed before scheduling. - **If:** Scope, expertise, or timing is outside the practice **Then:** Not qualified → Resource or referral. The response is useful without creating a false expectation. ### Product boundaries - Qualyo does not generate proposals, contracts, invoices, or managed signed-document workflows. - It has webhooks rather than advertised native CRM or project-management integrations. - Qualification output should inform a consultant’s review, not make a binding acceptance decision. ## SaaS sales teams Canonical page: https://qualyoforms.com/use-cases/saas-sales-teams Template: https://qualyoforms.com/templates/demo-request Discovery priority: Primary use case Turn a demo request into a structured buying-context record and a deliberate route. ### Qualification policy A qualified SaaS opportunity might have a relevant business use case, meaningful buying intent, a workable time frame, and the right routing context for the team. Company size can inform ownership, but it should not determine qualification by itself. - Relevant business use case - Buying role and intent - Timing and urgency - Territory or sales ownership Policy ownership: The sales team owns the policy. A strong SMB can qualify, an enterprise request can require review, and Qualyo applies the route the team defines rather than a universal score. ### Recommended questions - **What are you trying to improve?** Captures the use case rather than only a category. - **How does the team handle this today?** Adds current-process and replacement context. - **How many people would use the solution?** Provides size context without assuming a segment. - **What is your role in the evaluation?** Clarifies the respondent’s perspective and stakeholders. - **When do you want a solution in place?** Adds timing and urgency. - **What would you like to happen next?** Lets the respondent express demo, trial, pricing, or information intent. ### Decision logic - **Apply explicit routing rules:** Use fixed logic for territory, product availability, or another requirement with a certain answer. Never use company size alone as a fit verdict. - **Interpret use case and intent:** Use optional AI only where open-text workflow context or buying intent benefits from judgment across several answers. - **Send demand to the right path:** Route a strong fit to sales, an uncertain request to review, and exploratory demand to self-serve or nurture. ### Route outcomes - **If:** Use case, region, buying intent, and timing match a sales-owned route **Then:** Strong fit → Demo or sales follow-up. The team gets relevant context and a defined owner, regardless of company size alone. - **If:** The use case may fit but intent, ownership, or other context is incomplete **Then:** Needs review → Sales review. The automation does not invent certainty. - **If:** There is no relevant business use case or active sales evaluation **Then:** Not qualified for live sales → Self-serve or nurture. The respondent can move forward without a forced meeting. ### Product boundaries - Qualyo does not advertise native HubSpot, Salesforce, or calendar integrations; use webhooks and external ending links. - It is not a CRM, marketing-automation platform, or product-led onboarding system. - AI qualification should not be described as a certain score, conversion predictor, or autonomous acceptance decision. ## Recruiters Canonical page: https://qualyoforms.com/use-cases/recruiters Template: https://qualyoforms.com/templates/blank Discovery priority: Secondary use case Collect consistent candidate context, then route every application to a transparent human-reviewed next step. ### Qualification policy A recruiting workflow might collect the selected opening, relevant experience, work evidence, availability, and explicit location or working-arrangement requirements before a human review. - Selected opening - Job-relevant experience - Required work evidence - Explicit administrative requirements Policy ownership: The employer owns the policy and its legal review. Qualyo should automate administration, not make or imply a consequential hiring decision. ### Recommended questions - **Which role are you applying for?** Routes the application to the correct opening and review owner. - **Which experience is most relevant to this role?** Gives reviewers job-related context in the candidate's own words. - **What project or result best demonstrates that experience?** Surfaces concrete evidence without asking for a miniature work assignment. - **Is there a work sample or public link you would like us to review?** Lets candidates add relevant evidence without making it mandatory for every role. - **When would you be available to start?** Captures a practical timing constraint for the recruiter. - **Which location or working arrangements can you support?** Checks an explicit role requirement while avoiding unrelated personal questions. ### Decision logic - **Route explicit administrative facts:** Use fixed rules for the selected opening, application completeness, location, or a published working-arrangement requirement. - **Keep suitability under human review:** Send job-related experience and work evidence to a recruiter or hiring manager. Do not use AI as the sole basis for advancing or rejecting a person. - **Explain what happens next:** Confirm human review, request missing information, or identify another published opening without claiming an automated selection decision. ### Route outcomes - **If:** The selected opening and explicit location or working-arrangement requirements align **Then:** Human-review ending. A recruiter receives a consistent application record and remains responsible for the decision. - **If:** Required application context is missing **Then:** Information-request ending. The candidate knows what to add before review continues. - **If:** The opening is closed or another published role may be more relevant **Then:** Recruiter-review or alternate-opening ending. Administrative routing stays transparent without making an automated suitability decision. ### Product boundaries - Qualyo is not an applicant tracking system, interview scheduler, background-check service, or reference-check platform; external systems are connected through ending links or webhooks. - Do not use AI qualification or summaries as the sole or automatic basis for advancing or rejecting a candidate. Keep consequential employment decisions under meaningful human review. - Recruiting, privacy, accessibility, notice, consent, and record-retention requirements vary. Form owners must choose lawful, job-relevant questions and review the workflow with qualified counsel where needed. ## Coaches Canonical page: https://qualyoforms.com/use-cases/coaches Template: https://qualyoforms.com/templates/discovery-call Discovery priority: Secondary use case Understand goals and readiness before inviting a prospect into a discovery conversation. ### Qualification policy A coach might look for a goal that matches the program, a suitable start window, readiness to participate, and practical alignment with the offer. - Program fit - Desired outcome - Readiness and timing - Practical investment context Policy ownership: The coach owns these criteria. Qualyo applies the saved route and should never be presented as deciding whether coaching is appropriate for every person or need. ### Recommended questions - **What would you like to be different?** Centers the intake on a concrete desired change. - **What is getting in the way right now?** Adds context without turning the form into a coaching session. - **What have you already tried?** Shows prior effort and expectations. - **When would you like to begin?** Clarifies urgency and program timing. - **Which format are you considering?** Routes one-to-one, group, or self-guided interest. - **What investment range are you prepared to consider?** Makes the practical constraint explicit before a call. ### Decision logic - **Check program boundaries:** Use fixed rules for availability, supported formats, location, or other explicit requirements. - **Review readiness in context:** Use human review or optional AI only when goals and readiness need contextual interpretation. - **Offer the right next step:** Route an aligned prospect to discovery and offer a resource, waitlist, group program, or boundary message to everyone else. ### Route outcomes - **If:** Goal, timing, format, and investment context align **Then:** Discovery-call ending. The call can focus on mutual fit and next steps. - **If:** Goal fits but timing or investment is not ready **Then:** Resource, waitlist, or group-offer ending. The prospect gets a truthful next step without pressure. - **If:** Need is outside the coach’s scope **Then:** Referral or boundary ending. The form avoids implying that coaching is appropriate for every need. ### Product boundaries - Qualyo is not a scheduling, payment, course, or coaching-delivery platform. - An AI Qualifier evaluates the criteria you provide; it does not replace professional judgment or an explicit fixed rule. - Sensitive health or clinical intake requires a separate compliance review before use. ## Freelancers Canonical page: https://qualyoforms.com/use-cases/freelancers Template: https://qualyoforms.com/templates/project-inquiry Discovery priority: Secondary use case Replace email back-and-forth with a compact project brief and a route you can review quickly. ### Qualification policy A freelancer might require a supported service, workable scope, a budget above a personal minimum, a realistic deadline, and a clear approval owner. - Service fit - Scope and budget - Availability and deadline - Decision ownership Policy ownership: The freelancer sets every boundary. Qualyo applies that saved policy and can leave uncertain work for manual review. ### Recommended questions - **What are you trying to make or improve?** Captures the objective in the prospect’s words. - **Which service best matches the project?** Checks alignment with the published offer. - **What needs to be delivered?** Surfaces scope before a call. - **What budget range are you working with?** Makes a central constraint visible early. - **When do you need the work?** Checks availability and schedule feasibility. - **Who will approve the work?** Clarifies feedback and decision ownership. ### Decision logic - **Check firm project boundaries:** Use fixed rules for services, minimum budget, availability, or a deadline that clearly cannot be met. - **Review nuanced scope:** Use manual review or optional AI only when the project description needs interpretation across several answers. - **Close the loop:** Route a fit to a project call, a capacity mismatch to a waitlist, and out-of-scope work to a referral or resource. ### Route outcomes - **If:** Service, scope, budget, and timing align **Then:** Project-call ending. The inquiry is ready for a focused fit conversation. - **If:** Project fits but availability does not **Then:** Waitlist or alternate-date ending. The prospect gets a clear timeline instead of silence. - **If:** Service or minimum boundary does not match **Then:** Referral or resource ending. The route remains professional and useful. ### Product boundaries - Qualyo is not a project-management, invoicing, contract, payment, or general file-transfer platform; it can collect supported files as form responses. - A booking link is configured as an ending; there is no advertised native calendar connector. - The form should request only the information needed to review an inquiry. 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. # Comparison summaries ## Qualyo vs Typeform Page: https://qualyoforms.com/compare/qualyo-vs-typeform Choose Qualyo when the route itself needs to be visible, deterministic, and paired with optional AI qualification. Choose Typeform when you need a mature general-purpose form platform, a broader direct integration catalog, advanced enterprise options, or Typeform-specific research and marketing workflows. Choose Qualyo when: - You want conversational and classic presentation to share one saved route graph. - A reviewer must be able to inspect every branch and ending visually. - AI qualification needs an explicit owner-selected failure fallback. - Unlimited static submissions matter more than a large native integration catalog. Choose Typeform when: - You need Typeform’s broad direct integration and developer ecosystem. - Your organization requires mature enterprise controls, custom response packages, or dedicated account support. - You need payments, video responses, research tooling, or a mature contract e-signature workflow. - Your workflow centers on Typeform’s contact enrichment, automations, or research products. ## Qualyo vs ScoreApp Page: https://qualyoforms.com/compare/qualyo-vs-scoreapp Choose Qualyo for flexible forms whose explicit routes can qualify, redirect, or end without forcing every workflow into a score. Choose ScoreApp when the scorecard itself is the lead magnet and you need score tiers, dynamic result pages, PDF reports, funnel tooling, or a purpose-built assessment workflow. Choose Qualyo when: - Your outcomes depend on explicit branches rather than a scorecard model. - You need classic and conversational forms from the same saved graph. - AI qualification needs an automatic fallback route. - You want unlimited static submissions rather than a response allowance. Choose ScoreApp when: - A score, category, or assessment report is the product you deliver. - You need dynamic result pages or PDF score reports. - You want built-in scorecard funnel and CRM connections. - Split testing, enrichment, or high-volume scorecards are central. ## Qualyo vs Jotform Page: https://qualyoforms.com/compare/qualyo-vs-jotform Choose Qualyo when you want a focused visual route graph, a shared classic/conversational form model, and optional qualification with deterministic fallback. Choose Jotform when you need a broad platform for payments, files, signatures, widgets, apps, tables, approvals, stores, PDFs, or mature enterprise workflows. Choose Qualyo when: - You want to inspect a route as nodes and edges. - The same flow should render conversationally or classically. - Unlimited static submissions are more important than a widget catalog. - Your qualification step needs an explicit AI fallback. Choose Jotform when: - You need payments, document signing workflows, PDFs, or specialized widgets. - You want Jotform Apps, Tables, Sign, Store Builder, Workflows, or PDF tools. - A broad template and integration ecosystem matters most. - You need Jotform’s established enterprise offering. ## Qualyo vs Google Forms Page: https://qualyoforms.com/compare/qualyo-vs-google-forms Choose Google Forms for fast, familiar surveys and quizzes with effortless Google collaboration and a direct Sheets workflow. Choose Qualyo when the respondent experience, branded publishing, visual multi-route logic, deliberate endings, or optional AI qualification matters more than native Workspace familiarity. Choose Qualyo when: - You need a branded lead or application experience. - The full route must be visible as a graph. - You want classic and conversational modes from one saved flow. - Open-ended answers should inform an AI qualification step with fallback. Choose Google Forms when: - The team already works primarily in Google Drive and Sheets. - You need a simple survey or quiz with minimal setup. - Real-time collaborator editing is more important than publishing control. - A direct Google Sheets response destination is essential. ## Qualyo vs involve.me Page: https://qualyoforms.com/compare/qualyo-vs-involve-me Choose Qualyo for form-centric qualification where a visible route graph, deterministic conditions, and fallback-aware AI matter. Choose involve.me when you need quiz funnels, scoring, calculators, built-in email sequences, a CRM, many direct marketing integrations, A/B testing, or conversion campaign tooling. Choose Qualyo when: - The workflow is a form route rather than a marketing funnel. - You want every branch and ending visible on one graph. - AI qualification must fall back deterministically. - You prefer unlimited static submissions over tiered funnel volume. Choose involve.me when: - You need quizzes, calculators, score outcomes, or interactive landing pages. - Built-in CRM and email automation should live in the platform. - Direct HubSpot, Klaviyo, Salesforce, or marketing-pixel integrations matter. - A/B tests, partial submissions, OTP verification, or campaign optimization are required. ## Qualyo vs Deformity Page: https://qualyoforms.com/compare/qualyo-vs-deformity Choose Qualyo when the saved route graph, edge order, shared classic/conversational model, deterministic AI fallback, and API/MCP operation parity are central to the workflow. Choose Deformity when you need payments, broader upload and signature workflows, more native integrations, or API and MCP access explicitly included in its free plan. Choose Qualyo when: - Every respondent path must be inspectable as nodes and edges. - An AI qualifier must have an owner-selected failure route. - Classic and conversational views should share canonical questions and logic. - You want the Public API and MCP server to expose the same account, workspace, form, submission, and analytics operations. Choose Deformity when: - You need API and MCP access explicitly included in Deformity’s free plan. - Payments, broader upload/signature controls, or managed document workflows are required. - Direct Google Sheets, Zapier, GTM, Analytics, or Meta Pixel integrations matter. - You need a broader free feature set or 3-seat paid team plan. # Published field guides - https://qualyoforms.com/blog/ai-lead-qualification-forms - https://qualyoforms.com/blog/client-intake-process-flow-chart - https://qualyoforms.com/blog/client-questionnaire - https://qualyoforms.com/blog/coaching-sales-process - https://qualyoforms.com/blog/discovery-call-conversion-rate - https://qualyoforms.com/blog/how-to-pre-qualify-leads-before-discovery-call - https://qualyoforms.com/blog/pre-qualification-questions-coaches - https://qualyoforms.com/blog/reduce-discovery-call-no-shows - https://qualyoforms.com/blog/what-information-does-the-client-intake-form-gather - https://qualyoforms.com/blog/what-is-an-intake-form # Legal and correction links - Terms: https://qualyoforms.com/terms - Privacy: https://qualyoforms.com/privacy - Comparison method: https://qualyoforms.com/compare#methodology - Corrections and support: support@qualyoforms.com