How to Qualify Website Leads Before Human Handoff

Buttr has reviewed the form. The seventeen-field version is resting somewhere safe.

Website lead qualification should identify the visitor, the problem, the likely fit, and the next useful action before a human joins. For a small team, the best flow uses three or four short questions, preserves the conversation, and sends the answers through a delivery channel someone already monitors.

Krispy is open-source (MIT) live chat with AI replies and human handoff to Telegram — self-host free on Cloudflare, or Krispy Cloud at $19/mo flat, no per-seat pricing. Its form and handoff tools can support this workflow, but the method works with any chat product that preserves context and lets a person take over.

What should website lead qualification accomplish?

Website lead qualification should help a human make a better first reply, not attempt to score a stranger with false precision. The useful output is a compact brief: who the visitor is, what they need, whether the request fits, and which next step makes sense.

For most founder-led businesses, four pieces of information are enough:

1. Identity: a name and a reliable reply address.
2. Need: the job the visitor wants done, in their own words.
3. Fit: one constraint that changes your response, such as team size, timeline, or a sensible budget band.
4. Intent: whether they are researching, comparing options, or ready for a human answer.

The chat transcript already contains valuable context. Do not ask the visitor to repeat the question in a form if the bot has captured it. Ask only for information that changes what the human does next.

Which questions should a lead form ask?

A lead form should ask the fewest questions required to route and answer the request. Start with name and email, then add one select field and one optional text field only when those answers change ownership, priority, or the reply.

Avoid collecting data because it might become useful someday. Every field creates work for the visitor and a retention obligation for you. If budget only matters after you understand the request, ask it during the human conversation. If company size never changes the response, remove it.

Krispy forms support text, email, tel, textarea, and select fields. A self-hosted configuration can express a small qualification form like this:

{
  "forms": [
    {
      "id": "project-fit",
      "title": "tell us what you need",
      "fields": [
        { "name": "name", "label": "your name", "type": "text", "required": true },
        { "name": "email", "label": "email", "type": "email", "required": true },
        {
          "name": "timeline",
          "label": "when do you need an answer?",
          "type": "select",
          "options": ["today", "this week", "planning ahead"]
        },
        { "name": "context", "label": "anything else?", "type": "textarea" }
      ],
      "connectorIds": ["tg-main", "sales-email"]
    }
  ]
}

The form collects the declared values; it does not add hidden referral, campaign, or UTM fields. Keep acquisition attribution in your analytics system.

When should the AI raise the form?

The AI should raise a form after it understands the visitor’s goal and a concrete follow-up would help. It should answer ordinary questions directly, avoid collecting details that are unnecessary for the answer, and offer a person whenever the visitor asks for one.

Useful triggers include:

• The visitor asks for a tailored quote or an answer that depends on their situation.
• The question involves an exception, negotiation, complaint, or sensitive account detail.
• The visitor explicitly asks to speak with a person.
• The AI cannot answer confidently from the supplied knowledge.

Krispy separates a form marker from a handoff marker. A form can collect a follow-up request without silencing the AI, while a handoff tells the bot to step back so the operator owns the thread. That separation matters: a captured lead is not automatically an emergency, and every handoff does not need a custom form.

The bot should also explain why it is asking. “Leave an email so we can answer the account-specific part” is clearer than presenting a blank card with no connection to the conversation.

How should the handoff reach a human?

The handoff should reach a channel that has a named owner and an expected response time. For Krispy’s self-hosted path, Telegram is the live operator channel; captured form values can also be delivered by email when Resend is configured.

Krispy also supports visitor-facing links for WhatsApp, phone, Instagram, Facebook, TikTok, and a normal web link. Those links let the visitor choose another contact path. They are different from server-side lead delivery: Telegram and email deliver the captured values, while the other connector types present a call-to-action for the visitor to tap.

There are no native Slack, Jira, or n8n connectors in this flow. If your process requires one of those systems, treat it as a separate integration project and verify the data boundary, retries, and duplicate handling before depending on it.

For Telegram setup, follow the human handoff setup guide. The important behavior is that the transcript stays attached to the handoff. A person should see the original question, the AI’s replies, and the submitted fields before typing anything.

How do you measure whether qualification is working?

Measure whether qualification improves the human conversation without depressing useful submissions. Review a small sample of real handoffs each week and track operational outcomes you can observe directly.

Start with four checks:

• Completion: do visitors finish the form after it appears?
• Context quality: can the operator write a specific first reply without asking the visitor to repeat themselves?
• Routing quality: do the right requests reach the person responsible for them?
• Resolution: does the conversation reach a clear next step or answer?

Change one question at a time. If removing a field keeps context quality stable and lifts completion, leave it out. If a select option repeatedly produces the same follow-up question, rewrite the option so it captures the distinction the operator actually needs.

When should you avoid automated qualification?

Avoid automated qualification when the visitor needs urgent help, is reporting harm or fraud, or has already asked for a person. In those cases, collect only the contact detail required to continue and make the handoff obvious.

Use Krispy when you:

• Want AI to answer repeat questions before qualification.
• Need a short configurable form and transcript-aware handoff.
• Already monitor Telegram or email for follow-up.

Choose a mature service desk when you need complex queues, SLA rules, audited assignments, or native CRM and ticketing integrations.

The human-in-the-loop live chat guide explains the operating model in more detail. For shipped product changes, the Krispy changelog is the record to check before depending on a capability.

FAQ

How many questions should a website lead form ask?

Most small-team lead forms should ask three or four questions. Collect identity, a reply address, the visitor’s need, and at most one constraint that changes your response. Use the existing chat transcript instead of asking the visitor to repeat information.

Should every chat visitor see a qualification form?

No. Show a qualification form when the conversation reaches a concrete follow-up or the answer depends on visitor-specific details. Routine questions should receive a direct answer, and a visitor who asks for a human should be allowed to hand off without passing a scoring test.

Where does Krispy send captured leads?

Krispy can deliver captured form values to Telegram and email when those channels are configured. WhatsApp, phone, Instagram, Facebook, TikTok, and web-link connectors are visitor-facing actions rather than server-side lead delivery. Krispy does not currently provide native Slack, Jira, or n8n connectors.

Does Krispy capture UTM parameters or referral data with a lead?

The documented Krispy lead form captures the fields you declare. It does not promise built-in UTM or referral capture. Keep campaign attribution in your analytics system unless you implement and verify a separate, consent-aware data path.

Can Krispy book meetings automatically?

Krispy can show a configurable form or a normal link as the next action, but that is not an automatic booking integration. Link to your chosen scheduling page if you use one, and confirm the appointment in that system rather than treating form submission as a booked meeting.