Marketingabout 25 min

    How do I qualify jobs with questions that change based on the answers?

    Short answer

    Add branching logic so an early answer, like job type or property size, determines which follow-up questions appear next. This keeps the form short for every visitor while still gathering the specific details each job type needs to be quoted accurately.

    Before you start

    • A form builder that supports conditional or branching logic.
    • A defined list of job types or service categories.
    • Knowledge of which follow-up questions each job type actually needs.
    • A way to flag or score answers that indicate a poor-fit lead.

    Step by step

    1. 1

      Pick the one question that splits your jobs

      Usually job type, property type, or urgency is the branch point.

      One good branch question avoids building a maze of logic later.

    2. 2

      Map the follow-up questions per branch

      Write out exactly what a roof job needs versus what a plumbing job needs.

      Irrelevant questions waste the visitor's time and lower completion.

    3. 3

      Build the branches in the form

      Set each follow-up section to show only when the matching answer is selected.

      This is what keeps the form short for everyone despite covering many job types.

    4. 4

      Add a disqualifying path

      If an answer indicates you cannot serve them, route to a polite explanation instead of the full form.

      It saves the visitor's time and keeps your pipeline free of dead ends.

    5. 5

      Tag the submission with the branch taken

      Store which path someone followed as a field on the contact record.

      Staff can see the job type at a glance without rereading every answer.

    6. 6

      Test every branch end to end

      Walk through each path as if you were a customer before it goes live.

      A broken branch can silently skip required fields for an entire job type.

    7. 7

      Review low-quality submissions monthly

      Check which branches produce leads that never book.

      This tells you where the qualifying questions need to be sharper.

    What good looks like

    • Every job type gets exactly the questions it needs, no more and no less.
    • Poor-fit inquiries are filtered before they reach the schedule.
    • Staff can see job type and key details without extra back and forth.
    • The form stays short even as the range of services you offer grows.

    Common mistakes

    The ways this goes wrong in marketing, and what to do instead.

    Same questions for every job type

    A generic form asks irrelevant questions of most visitors and misses details for others.

    Do this instead: Branch the follow-up questions based on the job type selected early in the form.

    Too many branch points

    Splitting on three or four different answers turns the form into a confusing maze.

    Do this instead: Pick one primary branch question and keep secondary variation to a minimum.

    No path for poor-fit leads

    Every submission lands in the same pipeline regardless of whether you can serve them.

    Do this instead: Add a disqualifying branch that routes those answers away from the active pipeline.

    Frequently asked

    5 questions about qualify jobs with conditional questions

    Keep it to one or two levels deep. Beyond that, testing and maintaining it becomes a burden.

    Pick the next thing to set up, or back up a step if something here assumed work you have not done yet.

    Was this guide helpful?

    Tell us what worked and what didn't. It shapes what we rewrite next.

    You didn't get into business to be in the tech business.

    Managed Tech clients hand this to us. We build it, test it, maintain it, and add to it as the business changes, so nobody on your team has to become the person who knows how the system works.

    Schedule a fit callCallCalls are answered by Troy, our AI assistant. Troy answers questions about the system and services and can schedule, reschedule, or cancel appointments. He never sells or makes offers. Any communication with TactStack is stored in our systems and referenced by Troy during certain interactions. AI can make mistakes.Full documentation