> ## Documentation Index > Fetch the complete documentation index at: https://docs.inploi.com/llms.txt > Use this file to discover all available pages before exploring further. # Choosing form or chatbot > Control whether an application flow is presented as a form or a chatbot on your careers site # Choosing form or chatbot A flow defines *what* you ask candidates, not *how* it looks. The same flow can be presented to candidates in more than one way: * **Form** — a traditional, scrollable form experience. * **Chatbot** — a conversational experience, one question at a time. * **Agent** — an agent-led experience (coming soon). The important thing to understand is that this choice is **not** made on the flow itself. There is no form-or-chatbot switch in the flow builder. Instead, you choose the experience **on your careers page in the CMS**, on the button or block that opens the flow. This means the same flow can appear as a form on one page and as a chatbot on another. Whichever experience you choose, the underlying flow is the same — the same questions, logic, and **Submit Application** step. Switching between form and chatbot changes only the presentation, not what the candidate is asked or where their application is sent. ## How to choose on a button Most flows are opened from a button somewhere on your careers site — a hero call to action, a card, a footer link, and so on. Every CMS button has a **Destination** setting that controls what happens when a candidate clicks it. Two of the destination options open a flow: * **Flow** — opens the flow as a **chatbot**. * **Form** — opens the flow as a **form** in a pop-up drawer. In the [page editor](/studio/cms/pages/page-editor), select the button you want candidates to click to apply. Open the **Destination** setting and choose **Flow** (for the chatbot experience) or **Form** (for the form experience). Under **ID type**, choose how you want to reference the flow, then enter the matching value: * **Flow** — a specific flow by its Flow ID. * **ATS** — the job's ID in your ATS. * **inploi** — the job's inploi ID. Set a custom title and the colours and light/dark mode so the experience matches your branding. Save the page and [publish](/studio/cms/pages/publishing-and-versioning) when you're ready for candidates to see it. ## Dedicated blocks As well as the button destinations above, there are two purpose-built blocks you can add to a page: * **Flow button** — a button that always opens the flow as a **chatbot**. * **SDK Form** — a **form** embedded directly into the page, rather than opening in a pop-up drawer. Use this when you want the application form to sit inline on the page itself. The **Flow button** and **SDK Form** blocks are restricted, so they only appear for users with editing (update) permission on the CMS. If you can't see them, ask a colleague with the right access, or use a button's **Destination** setting instead. See [users and permissions](/studio/settings/users-and-permissions). ## Which should I use? | You want to... | Use | | --------------------------------------------------- | ----------------------------------------------------------- | | A conversational, one-question-at-a-time experience | Button **Destination → Flow**, or the **Flow button** block | | A traditional form in a pop-up drawer | Button **Destination → Form** | | A form embedded inline on the page | The **SDK Form** block | What flows are and how they capture candidate data Build a flow in the flow builder Add and configure buttons and blocks on a page How the conversational experience is embedded via the SDK