Chat forms

A chat form is a form presented as a conversation: instead of a page of labelled fields, the visitor sees one question at a time in a chat window and answers in their own words. It is the same idea as a conversational form — the name simply emphasizes the interface. What makes it a form rather than a chatbot is that it has a fixed set of information to collect and produces a structured record at the end.

A chatbot is open-ended — it answers whatever a visitor asks, and any given conversation can end anywhere. A chat form has a destination: a defined set of information it needs before it is finished, and a structured record it produces when it gets there. They share an interface and almost nothing else. If what you want is a completed intake rather than a deflected support question, you want a chat form.

Yes. Intake generates two snippets for every template. The standard one is an iframe plus a small loader script that resizes the chat as the conversation grows — it works on Webflow, WordPress, Framer, and any page that accepts a script tag. The script-free version is a plain iframe at a fixed height for hosts like Notion, Squarespace, and Wix that strip scripts. Both inherit your template's brand colors, font, and corner radius.

No. They open the link or land on the page with the embed, and start typing. There is no signup, no login, and nothing to download. Removing that step matters more than it sounds — an account wall in front of an intake form loses a meaningful share of the people who were willing to fill it in.

It can, and it usually changes what you get. A contact form typically returns a name, an email, and a sentence, which means the real qualifying happens later over email. A chat form can ask the qualifying questions while the person is still interested, accept whatever documents they already have, and hand you something you can act on. The tradeoff is time: a chat form asks for a few minutes rather than a few seconds, so it suits considered enquiries better than a quick question.

Better than a conventional form does. A long web form on a phone means pinching, scrolling, and mistyped fields; a chat is the interaction model people already spend most of their phone time in. It is one of the clearer advantages of the format.

You do not usually port it field by field. Describe what the form was trying to find out and let the template be generated from that description — the sections you care about, the things that always need chasing, the tone you want. The result covers the same ground, but the question order and the follow-ups are decided while the conversation is running rather than fixed in advance.