Form With Scoring: How Your AI Agent Sets the Points for Leads, Candidates and Quizzes (2026)

A form with scoring turns every answer into points, so the total tells you what to do next. Without it, every response looks the same in your inbox. Someone still has to read each one and decide by gut feeling who gets a call, who gets an email and who gets nothing.

That reading is slow, and it is not consistent. Two people on the same team will rank the same ten leads in two different orders. Meanwhile, the best lead of the week waits behind twenty that were never a fit.

This guide shows how a form with scoring works: how to set the points, where to draw the lines and what to do with each group. Then it gives you three forms your AI agent can build in one message, for leads, candidates and quizzes.

What a form with scoring does

A form with scoring works in three parts. First, each answer option carries points. Next, the points of every answer add up to a total. Finally, that total falls into a range, and each range leads somewhere different.

Here is how that looks in dForms, the form builder for AI agents:

• Single choice, multiple choice and dropdown questions give each option its own points. With multiple choice, the points of every selected option add together.
• Sliders award points by value range, for example 0 to 10 gives 0 points and 41 to 100 gives 5.
• Points are whole numbers, and negative numbers are allowed. A negative value lowers the score, which penalizes a disqualifying answer without ending the form.
• Contact fields and free text do not score. Name, email and phone never change the total, and neither do short or long text answers.

The form also shows the highest possible score, which is the best option of every scored question added up. You need that number to set your ranges.

Points per answer, not per question

Not every form builder works this way. In a Google Forms quiz, for example, you set how many points each question is worth and mark the correct answer. That is right or wrong scoring, built for tests. A lead or a candidate form needs something else. Every option on the scale gets its own weight. After all, "51 to 200 employees" is not wrong; it is just worth more than "2 to 10".

Set the points: weights for fit, intent and disqualifiers

Good scoring starts with a simple question for every field: how does this answer change what we do next? If the answer does not change anything, the question does not need points.

Sort your questions into three kinds

• Fit questions say whether this person could ever be a customer or a hire. Company size, role, location and years of experience are typical. Give them steady positive points.
• Intent questions say how soon they want to act. Timing, budget and "what made you look today" belong here. Weight them the most, because intent goes stale fast.
• Disqualifiers are the answers that should pull the score down. "Just a student", "no budget this year" or "not authorized to work here" can carry negative points.

Keep the math easy to read

Use a small scale, for example 0 to 10 per question, so anyone on the team can read a score at a glance. Then check the total range. If the highest possible score is 40, a lead at 32 is clearly strong, and a lead at 12 is clearly not.

If your points already live in a spreadsheet, you do not have to type them twice. In the dForms editor you can paste two columns, option and points, and the options import with their scores.

For a ready list of scored questions, the 25 lead qualification questions template gives you the options and points for fit, need, timing, budget and authority.

Thresholds and routing: book, nurture or drop

Points only matter if each total leads to an action. So split the score into ranges, and give every range its own outcome.

In dForms these are outcomes. Each range has a label, a message and, if you want, a redirect URL with a short delay. The checks run from the lowest score up, and the first range that matches wins. The top range is always open-ended ("and up"), so no score is ever left without an outcome.

Rules that beat the score

Sometimes one answer should decide on its own. For example, anyone who picks "Enterprise" should land in the top range, whatever else they answered. A range can carry rules like that, so the answer forces the outcome regardless of the total.

Show questions based on the score so far

The form can also change as the person answers. A condition can read the score so far, the points collected before the current question. So a high scorer can see the booking step, while a low scorer skips it and finishes sooner.

Treat your first thresholds as a guess

Your first lines will be wrong, and that is fine. After a few weeks, compare the scores with the deals that closed or the people you hired. Then move the ranges. The score is a tool for sorting, not a verdict.

Three forms with scoring your agent can build

You do not have to set any of this by hand. Connect your agent to dForms, describe the form, and it builds the questions, the points, the ranges and the logic. In Claude, add the dForms connector at https://mcp.dforms.ai/mcp; our guide on how to create a form with Claude shows the steps. For a script or another agent, use an API key from the Developers page.

1. A lead qualification form

Create a form in dForms called "Demo request" with scoring on.
Questions: team size (1: 0 / 2 to 10: 3 / 11 to 50: 6 / 51 to 200: 10 / 200+: 8),
when they want to start (this month: 10 / this quarter: 6 / just exploring: 0),
budget approved (yes: 8 / in progress: 4 / no: -2),
then work email and full name (no points).
Outcomes: 20 and up "Great fit" with a booking step,
10 to 19 "Promising", below 10 "Not a fit yet".
Leave it as a draft and send me the preview link.

The AI SDR lead qualification form guide shows what happens after the booking.

2. A candidate screening form

Create a form in dForms called "Sales role screening" with scoring on.
Questions: years in B2B sales (0 to 1: 0 / 2 to 4: 5 / 5+: 8),
authorized to work in the US (yes: 5 / no: -10),
start date (within a month: 6 / one to three months: 3 / later: 0),
expected salary range (in our band: 6 / above it: 1),
then email, name and a resume upload (no points).
Outcomes: 18 and up "Invite to interview", 8 to 17 "Review", below 8 "Not this time".
Leave it as a draft.

For the questions themselves, see the 25 pre-screening interview questions your agent can score.

3. A scored quiz

Create a quiz in dForms called "Is your team ready for AI agents?" with scoring on.
Six single choice questions about tools, data, process and ownership,
each option worth 0 to 5 points.
Outcomes: 24 and up "Ready now", 12 to 23 "Getting there", below 12 "Start here",
each with a short message that uses the respondent's first name.
Leave it as a draft.

Your agent applies your workspace's logo and colors too. Review the preview, ask for changes in plain words, and publish when it looks right. A published form goes live right away, and you can revert it to the version that was live before.

Read and check the scores

Every response carries its score from the first answer on. You can see it in a Score column under Submissions and in the CSV export. In addition, the score travels to the places your team works:

• HubSpot: the total score goes to a number property you choose, and the outcome label to another, on completed submissions. Our guide on how to connect a form to HubSpot shows the mapping.
• Webhooks: the payload carries the score and the outcome label.
• Emails: the submission emails can include the score.

Or simply ask your agent:

List this week's responses to "Demo request" sorted by score.
Show how many landed in each outcome, and flag any response
where a disqualifier was picked but the score is still high.

One detail matters when you read the numbers. Skipped questions add nothing: a question hidden by a condition or jumped over by branching never counts. So the score reflects the answers the person actually gave.

dForms is free with unlimited responses, and it is open source under the MIT license. So scoring your next form costs you one message to your agent and a few minutes of review.

Frequently asked questions

What is a form with scoring?

A form with scoring assigns points to each answer and adds them into a total. The total then decides what the person sees or what your team does next, such as booking a call, sending a follow-up or closing the lead.

Can Google Forms give different points to each answer?

Not in a standard question. A Google Forms quiz sets points per question and an answer key of correct answers. To weight every option differently, you need a form builder with points per answer, such as dForms.

Can a score go below zero?

Yes. In dForms, an option can carry negative points, which lowers the total. That way a disqualifying answer pulls the score down without ending the form, and your lowest range can start below zero.

Do free text answers count toward the score?

No. Only choice, dropdown and slider questions score in dForms. However, your AI agent can still read open answers with a short rubric and flag them when it reviews the responses.

Can my AI agent build a form with scoring for me?

Yes. With the dForms connector in Claude or an API key, your agent builds the questions, the points, the outcome ranges and the logic from one message. Then you review the draft and publish it.

Is a form with scoring free in dForms?

Yes. dForms is free, responses are not counted or billed, and scoring is included. The project is MIT licensed, so you can also self-host it.