Q1Short answer · Required
What’s your first name?
Makes the setup experience personal without repeating unnecessary account data.
Operational intakeCustomer success
Operational intake
Collect setup context, then honor the customer's support choice.
Use this secondary operational flow after the sale to prepare delivery and route each customer to a live kickoff or self-serve guide.
Best for: Post-sale teams that need structured setup context and a customer-chosen kickoff path.
Available on Free. Replace the example questions, policy, outcomes, and destinations before publishing.
Starting routing policy
Setup context → customer-chosen support
- Captures
- Purchased offer, team, goal, tools, timing, and implementation owner
- Qualifies
- No lead qualification; a fixed preference decides the support route
- Routes
- Kickoff calendar or self-serve setup guide
What this flow decides
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.
Captures
Purchased offer, team, goal, tools, timing, and implementation owner
Qualifies
No lead qualification; a fixed preference decides the support route
Routes
Kickoff calendar or self-serve setup guide
Routing policy
Make the onboarding route yours before it goes live.
No lead qualification is required. The saved flow uses a deterministic answer rule because the customer has already been accepted.
- 1
The purchased package determines the setup context.
- 2
The customer names the first goal and implementation owner.
- 3
The kickoff preference controls the final route.
Questions
See every question and the job it does.
Audit the complete starting blueprint before you copy it. Each rationale explains why the field exists and what decision it supports.
Customer context
Q2Email · Required
What’s your work email?
Provides a dependable channel for setup materials and kickoff details.
Q3Short answer · Required
What company are we onboarding?
Connects the onboarding response to the customer organization.
Q4Single choice · Required
Which plan or package did you choose?
Identifies the purchased scope so the handoff can reflect what was actually sold.
Starting choices: Starter, Growth, Pro, Enterprise
Implementation shape
Q5Single choice · Required
How many people will use the product?
Signals the number of people who may need access, training, or rollout support.
Starting choices: Just me, 2–5, 6–20, 21+
Q6Long answer · Required
What is the first outcome you want to achieve with [Product]?
Centers onboarding on the first outcome the customer wants to achieve.
Q7Multiple choice · Optional
Which tools are already part of your workflow?
Surfaces workflow dependencies and likely handoff or integration context.
Starting choices: HubSpot, Salesforce, Pipedrive, Zapier, Slack, Other, None yet
Ownership and timing
Q8Single choice · Required
When would you like to be up and running?
Sets a practical target for setup without inventing urgency.
Starting choices: This week, This month, Within 90 days, No fixed date
Q9Short answer · Required
Who will own implementation day to day?
Names the person responsible for day-to-day progress and coordination.
Kickoff preference
Q10Single choice · Required
Would a kickoff call help?
Creates a deterministic route between a live kickoff and a self-serve setup guide.
Starting choices: Yes, book me in, No, send me the setup guide
Logic, outcomes, and destinations
The customer chooses the route. No qualification is needed.
This post-sale workflow uses a fixed answer rule on the kickoff-preference question. The graph sends each customer to the matching next step without asking AI to reinterpret a clear choice.
Preference route
Read the saved kickoff choice with deterministic logic
Where the flow branches
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
Outcome destinations
Kickoff requested
Open the kickoff calendar
The customer chooses live support after providing the setup context.
Self-serve requested
Deliver the setup guide
The customer chooses the documented setup path instead of a live call.
Local deterministic route
Try the onboarding route locally.
Choose a kickoff preference to preview the deterministic destination. This example stays on the page, records no customer response, and submits nothing.
Local deterministic route
How does this customer want to begin?
The customer-owned preference controls the route. No qualification or AI judgment is needed.
Explicit route choice
Live kickoff
Open the kickoff calendar
Kickoff calendar
The customer chooses live support after providing the setup context.
No submission sent. No lead created. No answer stored. No AI used.
Customization
Replace the example policy with the way your team works.
Onboarding should reflect what your customer bought and how your team delivers it. Replace the example package, tools, ownership language, and resources before publishing.
- Step 1
Match the purchased offer
Replace the example plans with the packages or services customers can actually arrive from.
- Step 2
Define the first outcome
Tune the goal and timeline questions to the milestones your onboarding team can support.
- Step 3
Name the handoff owner
Ask for the customer-side owner and connect notifications or webhooks to the right internal team.
- Step 4
Connect both preferences
Replace the calendar placeholder and attach the correct guide, checklist, or confirmation to the self-serve route.
Use it for the right job
Onboarding starts after the customer says yes.
Good fit
- SaaS teams collecting goals, tools, timing, and ownership before implementation.
- Agencies or services teams preparing a new-client kickoff.
- Businesses offering customers a clear choice between live and self-serve setup.
Choose another workflow
- Pre-sale qualification or project inquiries from prospects who have not been accepted.
- A full customer-success platform, project plan, support desk, or training portal.
- A contract, invoice, payment, or managed legal-signature workflow.
Customer onboarding routing FAQ
Questions before you use the flow
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.
Start with the complete onboarding route.
Copy the 10 questions and fixed preference branch, then connect the kickoff and guide your customers actually need.