Deterministic trigger
The form appears after the visitor message count you set, from the first message up to the eighth. No model judgment involved.
Setup, control, channels, pricing, and privacy. Open a question or ask the live Fetchply assistant for more detail.
Fetchply gives every customer question the right path. Repeat questions can receive approved Instant Answers, predictable requests can follow Guided Flows, open questions can use your business knowledge, and complex conversations can reach your team.
Launch one assistant for approved answers, guided journeys, knowledge-based help, and human handoff—without forcing every request through AI.
A visitor asking questions is worth following up with. Fetchply shows a short form at the exact moment you choose, records the answers as a clean structured lead, and delivers it wherever your team works.
Free plan · 200 AI messages a month · No credit card
Do you offer volume pricing for teams?
We do. Leave your work email below and our team will send you the team pricing sheet today.
Lead forms render inside the website chat widget conversation.
Fetchply captures leads with an in-chat form on the website widget. You decide after how many visitor messages the form appears, which of the one to eight fields it asks for, and which are required. Name, email, and phone answers map to fixed lead columns, submissions are rate-limited against junk, and every lead lands in the dashboard, syncs to a connected Google Sheet, or posts to your systems through the new-lead webhook.
Capture is deterministic, not left to the model’s judgment: the trigger and fields are rules you set.
You set a rule: after N visitor messages, a short form appears inside the conversation. The visitor fills it in without leaving the chat, the answers are validated and recorded as a structured lead, and the lead flows to your dashboard, spreadsheet, or CRM webhook automatically.
The problem
The visitors most worth following up with are the ones already asking questions:
Generic popups fire at the wrong moment and collect junk. Email-gated chat scares off the casual question that would have become a sale.
Capture at the moment of demonstrated interest and the same traffic produces a follow-up list that is actually warm.
Capabilities
The form is a deterministic rule you design, rendered natively inside the conversation, with validation and rate-limiting built in.
The form appears after the visitor message count you set, from the first message up to the eighth. No model judgment involved.
One to eight fields of text, email, or phone type. Mark which are required and write the labels visitors see.
The form renders inside the conversation, so the visitor hands over details without a context switch.
Name, email, and phone answers map to fixed lead columns, so the list stays filterable however you label fields.
Submissions are rate-limited and required fields must validate, keeping the list free of spam.
Leads sync to a connected Google Sheet and fire a new-lead webhook, so your CRM gets them as they arrive.
Channels
Lead capture runs on the website widget, and the rest of the platform keeps working around it.
The lead form renders inside the widget conversation, triggered by your message-count rule.
A connected sheet receives every lead live, with customizable columns your team already understands.
The new-lead event posts each lead to your endpoint, ready for Make, n8n, Zapier, or your own stack.
The form politely waits while a Guided Flow runs and appears after it finishes, so scripted journeys are never interrupted.
Escalation
A lead is only worth what happens next. Fetchply keeps the handoff to your team clean:
The same agent answers the visitor’s questions before and after the form, so capture never blocks the conversation.
Setup
Pick one to eight fields, mark required ones, and write the labels your visitors will see.
Choose after how many visitor messages the form appears, first through eighth.
Link a Google Sheet or point the new-lead webhook at your CRM pipeline.
Run a conversation in the dashboard and confirm the form appears exactly when you want.
Embed the widget and review the lead list as submissions arrive.
Results
What the lead list gives you:
Because the trigger is deterministic, you can tune the moment of capture and compare lead volume in analytics period over period.
Comparison
Before: Question answered, visitor leaves, no trace
Answered, then captured with a two-field form
Before: Dismissed by reflex, junk emails collected
Form appears mid-conversation, after real intent
Before: A name in a notebook, zero context
Structured record with the full conversation attached
Before: Manual copy-paste from chat transcripts
New-lead webhook posts it automatically
Before: Cleanup work every week
Rate-limiting and validation keep the list clean
Ready to stop losing engaged visitors?
Start free and design your form in minutes.
FAQs
After the visitor message count you set, anywhere from the first message to the eighth. The trigger is a rule, not a model decision, so it is completely predictable.
Connect Google Sheets for a live spreadsheet of leads, or use the new-lead webhook to post each lead to your own endpoint and forward it anywhere, including through Make, n8n, or Zapier.
Submissions are rate-limited per visitor, and required fields must validate before the form is accepted.
The form is intentionally held back while a flow is in progress and appears after the flow finishes, so scripted journeys are not interrupted.
Yes. The form is a moment inside the conversation, not the end of it. The agent keeps answering before and after the capture.