Claude Forms: 5 Forms Your Agent Builds and Scores From One Prompt (2026)

Claude forms start with one message: you describe what you need, and Claude builds the questions, the scoring and the ending for you. However, most people who try it get stuck on the same thing. They do not know what to ask for. So they type "make me a lead form" and get something generic.

This post fixes that with five forms you can copy today. Each one comes with the exact prompt to paste, what Claude builds from it, and why the questions are there. They cover the forms teams ask for most: lead qualification with scoring, candidate pre-screening, client onboarding, a demo request that books a call, and a feedback form that sends every answer to a webhook.

What Claude forms are (and what they are not)

Claude does not host forms on its own. Instead, it connects to apps through the Model Context Protocol, an open standard for connecting AI applications like Claude to external tools. So Claude forms are simply forms that Claude builds inside a form app it can reach through one of those connections. Claude does the building; the app hosts the form, collects the answers and scores them.

dForms is the form builder for AI agents, the one your agent actually wants to use. Through its connector, Claude can create, publish, update and revert forms, list the responses and read the analytics. It is also free and open source, with unlimited responses.

It is not the only option, to be fair. Typeform ships an MCP server, and so does Tally with its MCP server. The difference is what happens after the form exists: dForms scores every answer and routes the hot ones to your calendar or CRM. That is why each template below includes points.

Connect dForms to Claude once

The setup takes a couple of minutes, and you do it once. In Claude, open Connectors, choose Add custom connector, name it dForms and paste this URL:

https://mcp.dforms.ai/mcp

Then sign in with your dForms account. According to Claude's help center, custom connectors work on Free, Pro, Max, Ultra, Team and Enterprise plans, and Free users get one custom connector. The full walkthrough, with screenshots of every click, is in our guide on how to create a form with Claude.

How to use these five templates

Every template follows the same pattern. First, the prompt names the form and lists the questions with their answer options. Next, it says which answers earn points. Finally, it says what happens at the end and asks Claude to leave the form as a draft. Change the details to fit your business, but keep the structure. The structure is what makes the result usable on the first try.

Form 1: Lead qualification form with scoring

A lead form that does not score anything leaves the sorting to a person. That person is usually slow. In fact, a Harvard Business Review study that audited 2,241 US companies found that 23% never responded to a web lead at all. The same research found that firms who tried to reach a lead within an hour were nearly seven times as likely to qualify it.

So this first form scores while the lead types. Paste this into Claude:

Create a form in dForms called "Lead qualification".
Questions:
1. Full name (required)
2. Work email (required)
3. Company website
4. Team size: just me / 2 to 10 / 11 to 50 / 51 to 200 / 200+
5. Monthly budget for this project: under $500 / $500 to $2,000 / $2,000 to $10,000 / over $10,000
6. When do you want to start: this month / this quarter / just researching
7. What problem do you want to solve? (open text)
Points: team size 11 to 200 = 10, 2 to 10 = 5, others = 2.
Budget over $2,000 = 10, $500 to $2,000 = 5, under $500 = 1.
Start this month = 10, this quarter = 6, researching = 1.
Open answer that names a concrete process = 10, vague = 3, blank = 0.
At the end, show my calendar booking step only when the total is 70% or more.
Send every response to HubSpot. Leave it as a draft and give me the preview link.

What Claude builds. You get seven questions, the options with their points, the conditional ending and the HubSpot destination. Your brand kit applies if you have one.

Why it works. Budget, timeline and team size are the three answers that separate a buyer from a browser. Meanwhile, the open question catches intent that the options miss. If you want the full question bank behind this template, our post on how to qualify a sales lead lists 25 scored questions.

Form 2: Candidate pre-screening form

Recruiters lose good candidates in the gap between the application and the first call. A pre-screening form closes that gap, because it asks the deal-breaker questions up front. As a result, the recruiter only calls people who already fit.

SHRM's screening toolkit frames screening as narrowing the pool to the candidates who meet the job's requirements. That is exactly what the scoring does here:

Create a form in dForms called "Pre-screening: Account Executive".
Questions:
1. Full name (required)
2. Email (required)
3. Phone
4. Years of B2B sales experience: under 1 / 1 to 3 / 3 to 5 / 5+
5. Have you sold software with a deal size over $10,000? yes / no
6. Can you start within 30 days? yes / no
7. Salary expectation fits the range of $70,000 to $90,000 base: yes / no / I want to discuss it
8. Tell us about a deal you closed and how you did it (open text)
9. Upload your resume (file, PDF)
Points: experience 3 to 5 or 5+ = 10, 1 to 3 = 5, under 1 = 0.
Software deals over $10,000: yes = 10, no = 2.
Start within 30 days: yes = 8, no = 3.
Salary fits = 8, discuss = 4, no = 0.
Open answer with a specific deal and numbers = 10, generic = 3.
Leave it as a draft and give me the preview link.

What Claude builds. It creates nine questions, including the resume upload, with the points attached. After you publish, you can ask Claude to list the candidates sorted by score.

Why it works. The open question is the best predictor in the set. A candidate who explains a real deal, with numbers, writes very differently from one who does not. For 25 more questions to swap in, see our list of pre-screening interview questions.

Form 3: Client onboarding form

Not every form needs a score. An onboarding form exists to collect what your team needs before the kickoff: goals, assets, access and who approves the work. Here the job of the agent is different. It flags what is missing instead of ranking anyone.

Create a form in dForms called "Client onboarding".
Questions:
1. Company name (required)
2. Main contact: name and email (required)
3. Who approves the work on your side? (name and role)
4. What is the main goal for the next 90 days? (open text)
5. How will you measure success? (open text)
6. Who is your ideal customer? (open text)
7. Upload your logo and brand guidelines (files)
8. Which tools do we need access to? website CMS / ads accounts / analytics / CRM / other
9. Anything we should avoid? (open text)
Make questions 1 to 4 required. If "other" is picked in question 8, ask which tool.
Leave it as a draft and give me the preview link.

What Claude builds. The form includes the file upload, the required fields and a follow-up question that only appears when the client picks "other".

Why it works. The approver question and the success metric prevent the two most common agency fights: rework and "this is not what we asked for". When the answers arrive, ask Claude to read them and list what is still missing before the kickoff call. Our client onboarding questionnaire has 30 questions to pick from if you need more.

What the first three forms have in common

Look at the three prompts together. Each one asks for a few required basics, then for the answers that change the next step. None of them asks a question nobody will use. That is the real skill behind a good form prompt: every question should either score, route or prepare the next conversation. If a question does none of the three, cut it.

Form 4: Demo request routed to your calendar

A demo request form usually ends with "we will get back to you". Then the lead waits, and the HBR research above shows what waiting costs. A better ending lets qualified visitors book the call right away, while everyone else gets a polite next step.

Create a form in dForms called "Book a demo".
Questions:
1. Full name (required)
2. Work email (required)
3. Company name and website (required)
4. Your role: founder or executive / manager / individual contributor / student
5. How many people would use the product: 1 to 5 / 6 to 25 / 26 to 100 / 100+
6. What do you want to see in the demo? (open text)
7. When do you plan to decide: within 2 weeks / within 3 months / no date yet
Points: founder or executive = 10, manager = 7, individual contributor = 4, student = 0.
Users 26 to 100 or 100+ = 10, 6 to 25 = 6, 1 to 5 = 3.
Decide within 2 weeks = 10, within 3 months = 6, no date = 2.
Open answer with a specific use case = 10, vague = 3.
Show my calendar booking step only when the total is 65% or more.
Otherwise, end with a thank you message and a link to our product tour.
Leave it as a draft and give me the preview link.

What Claude builds. You get the questions, the points, the booking step for qualified requests and a separate ending for the rest.

Why it works. Role and decision date tell you whether the person can buy, and when. As a result, your calendar only fills with calls worth taking. The same logic drives our form with scoring guide, which explains how to set the threshold.

Form 5: Feedback form with a webhook

Feedback is only useful if it reaches the people who can act on it. So this last template sends every answer to a webhook the moment it lands. From there, your own system can post it to a channel, open a ticket or update a dashboard.

Create a form in dForms called "Product feedback".
Questions:
1. How likely are you to recommend us to a colleague? (0 to 10)
2. What is the main reason for your score? (open text)
3. Which part of the product do you use most? dashboard / reports / integrations / mobile app
4. What is one thing we should improve? (open text)
5. Can we contact you about your answer? yes / no
6. If yes, your email
Show question 6 only when question 5 is yes.
Points: score 9 or 10 = 10, 7 or 8 = 5, 0 to 6 = 0.
Send every response to this webhook: https://example.com/hooks/feedback
Leave it as a draft and give me the preview link.

What Claude builds. It creates the 0 to 10 question, the conditional email field and the webhook destination. Replace the example URL with your own endpoint.

Why it works. The open "why" question right after the score gives the number its meaning. Also, the consent question keeps the follow-up honest: you only contact people who said yes. If your team works in HubSpot, our guide to connect a form to HubSpot shows the other route for the same answers.

Four mistakes that weaken a form prompt

Most weak forms come from weak prompts, not from the tool. Before you paste any of the five templates, check your edits against these four mistakes.

• No answer options. "Ask about budget" gives Claude nothing to score. Instead, list the ranges, because points need fixed choices.
• Points without a threshold. Scores only help when something happens at a number. So say what the form does at 70%, or whatever line fits your sales team.
• Too many open questions. Open text is great for intent, but each one adds effort for the person filling it in. One or two per form is usually enough.
• Publishing before testing. Answer your own form once from the preview link. You will catch a missing option or an odd ending in under a minute.

Fix those four, and you get a form you can share the same day. Then the only work left is reading the answers.

How your agent runs Claude forms after you publish

Building the form is half the job. The other half is reading what comes back, and that is where an agent saves the most time. Once a draft looks right, open the preview link and answer it once yourself. Then tell Claude to publish. If you change something later, the edit stays in a draft until you publish again, and you can always revert to the version that was live before.

After the answers arrive, ask in plain words:

List this week's responses to "Lead qualification" sorted by score.
For every response at 70% or more, give me one line on why it looks like a fit.
Show me the drop off by question, and export everything to CSV.

Claude lists the scored responses, summarizes the top ones, reads the analytics and hands you the file. Because the booking step only shows above your threshold, the hot leads already picked a time.

Prefer a script or a server side agent to Claude? Create an API key on the Developers page instead. It acts as you in that workspace, at up to 120 calls a minute. Keep in mind that a key can publish directly and has no read-only mode. So if you want to approve every form, ask the agent to leave it as a draft, as all five prompts above do.

That is the full loop of Claude forms: one prompt to build, one word to publish, one question to read the results. For the bigger picture of what an agent needs from a form tool, read our AI form generator guide, or start from the dForms home page.

Frequently asked questions

Does Claude have a built-in form builder?

No, Claude does not host forms by itself. Claude forms live in a form app that Claude reaches through a connector, such as dForms, Typeform or Tally. With dForms connected, Claude creates the form, publishes it and reads the scored answers from the chat.

Are Claude forms free?

Yes, Claude forms built with dForms are free. Responses are not counted or billed, and the code is open source under the MIT license, so you can also self-host it. Claude's Free plan allows one custom connector, which is enough for dForms.

Do I need an API key to use these templates?

No. The Claude connector signs you in with your dForms account, so there is nothing to copy or store. API keys are for scripts and server side agents, and you create them on the Developers page.

Can Claude publish a form without asking me?

It can publish when you tell it to, so the safe habit is to ask for a draft first. Every prompt in this post ends with "leave it as a draft", which gives you a preview link to check. A published form can always be reverted.

Can I use these prompts with ChatGPT or Cursor?

Yes. The prompts are plain text, and the dForms connector uses the same URL in other MCP clients like ChatGPT, Cursor and Claude Code. Only the way you add the connector changes.

Can the forms send answers to my CRM?

Yes. dForms sends responses to HubSpot or to any webhook, and you can set the destination in the same prompt. Connecting HubSpot to your workspace for the first time happens in the dForms dashboard.