Client intake for agencies

Turn an open-ended project inquiry into a structured brief and a visible next-step route.

Qualyo gives agencies one visual flow for project context, fixed routing, optional AI qualification, and tailored endings—without hiding the route in a prompt.

The job to do

A generic contact form leaves account teams reconstructing scope, budget, timing, and decision context over email. The useful job is not to reject people automatically; it is to collect enough context to choose a responsible next step.

01 · Useful outcomes

What this workflow should make easier

01

A consistent brief before an account review

02

A visible path for fit, nurture, referral, or follow-up

03

A reusable intake flow across services or campaigns

02 · Workflow

Build the policy before the form

The form is the interface. The route brief, fallback, and endings are the operating decision.

  1. Step 1

    Define the engagement boundary

    List the services, minimum project constraints, geography, and situations your team can responsibly support.

    Output: A short route brief

  2. Step 2

    Collect decision context

    Ask about the business problem, requested work, budget band, desired timing, stakeholders, and how success will be evaluated.

    Output: A structured project brief

  3. Step 3

    Route with explicit rules

    Use choice routes or Logic cards for hard requirements. Add an AI Qualifier only where fit needs judgment across several answers.

    Output: An inspectable route graph

  4. Step 4

    Give each route a useful ending

    Send aligned inquiries to a call, early-stage prospects to a planning resource, and out-of-scope work to a clear referral or response.

    Output: A deliberate next step

03 · Question design

Ask only what changes review or routing

Q1

What outcome are you trying to create?

Reveals the job behind the requested deliverable.

Q2

Which services do you expect to need?

Surfaces scope alignment before a call.

Q3

What budget range has been approved or discussed?

Establishes a practical constraint without asking for false precision.

Q4

When does the work need to begin?

Separates immediate projects from exploratory planning.

Q5

Who will participate in the decision?

Clarifies the buying process and stakeholders.

Q6

What would make the project successful?

Creates context for qualification and the first conversation.

04 · Route map

Every answer path earns an ending.

Route 1

If: Service, budget, and timing match a published engagement boundary

Then: Project-call ending

The team has enough context to evaluate the opportunity live.

Route 2

If: Scope may fit but timing or decision context is early

Then: Planning-resource ending

The prospect gets value without forcing a premature call.

Route 3

If: Requested work is outside the agency’s services

Then: Referral or transparent decline ending

The response stays respectful and explicit.

05 · Product fit

What Qualyo covers—and where the workflow leaves Qualyo

Supported in Qualyo

  • Classic and one-question-at-a-time delivery share the same saved questions and routes.
  • Choice routing, Logic cards, Router cards, and ordered edges keep the decision path inspectable.
  • An optional AI Qualifier can evaluate earlier answers, with an explicit automatic fallback when AI is unavailable.
  • Every route can finish with a tailored ending, redirect, notification, or webhook workflow.
  • File-upload and drawn-signature questions collect supporting responses; each file is limited to 15 MB.

Boundaries to design around

  • 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.

06 · Production checklist

Ship the route, not only the questions.

Preview both form modes, test the fixed path and AI fallback, and confirm that every ending says what happens next.

Start from project inquiry template
  1. 01

    Start from Project inquiry.

  2. 02

    Replace example ranges and services with published agency boundaries.

  3. 03

    Connect fixed routes before adding an AI Qualifier.

  4. 04

    Choose and test the Qualifier fallback.

  5. 05

    Test every ending with representative answers.

  6. 06

    Publish by link, embed, or verified paid custom domain.

07 · Frequently asked questions

Questions about Qualyo for agencies

Can an agency use fixed logic without AI?

Yes. Choice routes, Logic cards, Router cards, and tailored endings work without AI. Static forms and submissions are unlimited on every plan.

Can different services go to different next steps?

Yes. Route from a service choice or use a Logic card to send each service, budget band, or timing combination to a specific ending.

How should an agency use the AI Qualifier?

Use it for judgment across several earlier answers, not for a hard requirement that can be expressed as fixed logic. Select an automatic qualify or disqualify fallback before publishing.

Can Qualyo send inquiries to our CRM?

Every plan can send complete submission data by webhook to an endpoint you control or an automation workflow. Qualyo does not currently advertise a native CRM connector.

Can we create intake forms for multiple clients or services?

Yes. The product has no configured paid workspace limit, and you can create separate forms or keep several service routes in one flow. Free is limited to one workspace.

Which plan should an agency start with?

Free is suitable for building and testing with 50 lifetime AI conversations and unlimited static submissions. Paid plans start at $29 per month for 250 AI conversations and add custom domains, branding removal, logo upload, and fast AI mode.

Start with a route you can explain.

Free includes 50 lifetime AI conversations and unlimited static submissions.

Use project inquiry template