Formless

Every form ever built has the same asymmetry: it asks, you answer, and if you have a question there is nowhere to put it.

That is fine for a support ticket and quietly expensive for a sales enquiry, because the person filling it in frequently has a question that determines whether they finish at all — does this work with our stack, do you cover our region, is this even the right product.

Formless, built by Typeform, is a form that can answer. It is trained on your own data, so a respondent can interrupt with a question and get a real reply before continuing, and that single inversion is what the product is actually about.

The Two-Way Form In Five Lines

• It answers as well as asks — Formless is trained on your data, so respondents can ask it questions mid-form and get a real answer.
• No branching logic to maintain: the form adapts its path conversationally rather than through conditional trees you have to build and debug.
• Over 120 languages, which means one form rather than one per market.
• Built by Typeform, which brings a decade of form design behind it rather than a standing start.
• Embeds in multiple formats and integrates with HubSpot, Google Sheets, Mailchimp, Slack, Pipedrive and Zapier.

Formless: Product And Publisher

The Two-Way Form Is A Real Idea

Formless is described as an AI-powered form that asks and answers questions, trained on your data. The second half is the part worth dwelling on.

Consider what happens on a normal enquiry form when a prospect hits a question the form does not address. They guess, they abandon, or they submit a vague answer that makes the lead harder to qualify. All three are losses, and only the second is visible in your analytics.

A form that answers converts that moment into a conversation. The prospect asks whether you support their integration, gets an accurate answer from your own material, and either continues with confidence or self-disqualifies — and a fast self-disqualification is a genuinely good outcome for both sides.

It also changes what a form is for. A form is normally a data-collection instrument; this is closer to a first-line sales conversation that happens to produce structured data at the end.

The dependency is your source material. Trained on your data means the answers are only as good, current and complete as what you gave it, and an out-of-date document becomes an out-of-date answer given directly to a customer with your name on it. That is a maintenance obligation, not a one-time setup.

The nearest neighbour is not another form builder but a chat agent. Chatbase answers questions from your content without collecting structured data; this collects the data and answers questions as a consequence.

A form that answers converts abandonment into conversation — and a fast self-disqualification is a good outcome, not a lost one.

Why Removing Branching Logic Matters More Than It Sounds

Formless offers flexible logic without complex branching, and anyone who has maintained a large conditional form will recognise the problem being solved.

Branching logic starts simple and compounds. Three conditions are manageable; fifteen conditions interacting across twenty questions produces a structure nobody fully understands, including the person who built it. Paths go untested, dead ends appear, and the form silently breaks for some segment of respondents.

It is also why forms stop being updated. The cost of changing a heavily branched form is not the edit — it is re-verifying every path the edit might have affected, which is why so many organisations run forms that are two product cycles out of date.

Conversational adaptation sidesteps the structure entirely. The form decides what to ask next from what has been said, rather than from a tree you drew in advance.

The trade is determinism, and it is worth naming. A branched form is auditable — you can prove which questions a given respondent saw. A conversational one is harder to pin down, which matters if your questions are regulated, contractual or need to be identical for every applicant.

Where Do Conversational Forms Beat Ordinary Ones?

The honest position is that this is not better than a normal form. It is better at some jobs and worse at others, and the difference is predictable enough to decide in advance.

It wins where the respondent has questions, where the right next question depends on context, and where the interaction is itself part of the sale. Inbound lead capture, contact-sales flows, quote generation and complex job applications all fit that description.

It loses where the respondent already knows exactly what they want to give you. Someone submitting a support ticket with an order number does not want a conversation — they want four fields and a submit button, and making that slower is a worse experience however well it is done.

Speed is the specific cost. Conversational interfaces are inherently slower than a form you can scan, tab through and complete in twenty seconds, and that gap is widest for exactly the motivated respondents you least want to annoy.

The templates Formless publishes reflect this well. Inbound leads, contact sales, feedback, quizzes, quote generators and job applications are all cases where the extra time buys something — which is a more disciplined product position than claiming to replace every form you have.

For a conventional form built quickly, Makeform is the lighter answer, and for ongoing feedback programmes a survey platform such as SurveySparrow is designed around a different rhythm entirely.

• Use it for lead capture and contact-sales flows, where questions block completion.
• Use it for quote generation, where the right questions genuinely depend on earlier answers.
• Keep a plain form for support tickets and anything a respondent completes in under a minute.
• Keep a plain form where every applicant must see identical questions for compliance reasons.
• Review the training material on a schedule, since stale sources become wrong answers to customers.

Languages, Embedding And What Reaches Your Stack

Formless supports over 120 languages, and the operational meaning of that is one form rather than a form per market.

Multilingual forms are normally maintained as separate assets, which means every product change becomes a translation project and the versions drift apart. A single form that adapts to the respondent's language removes an entire maintenance category.

The caution is the same as anywhere else in the product: if the form answers questions in a language your source material is not written in, it is translating your content on the fly. That is usually fine and occasionally not, particularly for anything with legal or pricing implications, so spot-check the languages that actually matter to you.

On distribution, Formless embeds in multiple formats rather than only linking out, which matters because an embedded form on the page converts better than one behind a click.

Integrations cover HubSpot, Google Sheets, Mailchimp, Slack, Pipedrive and Zapier — CRM, spreadsheet, email, notification and the catch-all. That set is well chosen: it means a conversational lead lands in the same place as every other lead, rather than in a silo somebody has to check.

A lead landing in your CRM is only the start of the pipeline. Enrichment tools such as Clay and outbound platforms like Instantly pick up from there.

Setting It Up Without Creating A Liability

The setup risk here is not technical. It is that you have connected a system trained on your material directly to prospects and given it permission to speak.

Treat the training corpus as published customer-facing copy, because functionally that is what it now is.

1. Audit what you feed it before connecting anything, and remove internal, outdated or unapproved documents.
2. Test it adversarially with the questions your sales team actually gets, including the awkward ones about pricing and competitors.
3. Check what it says when it does not know, since a confident wrong answer is worse than a referral to a human.
4. Verify the integration path end to end so conversational leads land in your CRM alongside everything else.
5. Spot-check answers in the two or three languages that matter most to your business.
6. Put the training material on a review schedule tied to product releases, not to whenever someone remembers.

Formless Or A Plain Form?

Reach for Formless when

• Prospects abandon your enquiry form because it cannot answer their question.
• Your branching logic has grown past the point where anyone fully understands it.
• You operate across languages and maintain a separate form for each market.
• The right next question genuinely depends on what was just said, as in quoting.
• You want qualification to happen during capture rather than afterwards.

Use a normal form when

• The respondent already knows exactly what to give you, as in a support ticket.
• Speed of completion is the priority and a conversation would only slow it down.
• Compliance requires every respondent to see identical questions in a fixed order.
• You have no current, accurate source material to train it on.
• Nobody will own keeping that material up to date after launch.