Configure forms and collect submissions
Create in-chat or link-only forms, define questions, and understand consent and delivery.
On this page
Choose a delivery type
Administrators manage forms in Forms. Each form has a visitor-facing name and description.
| Type | Visitor experience | Required destination |
|---|---|---|
| In chat | The chatbot collects, reviews, and submits answers. | A supported form connection and submission endpoint. |
| Link only | The visitor opens the configured website to complete a form there. | A Website URL. |
For an in-chat form, Website URL is an optional fallback link after unsuccessful submission. It is separate from the private Submission endpoint that receives the answers. Switching delivery type retains saved in-chat settings.
Control visibility, languages, and recommendations
Visible allows new discovery by the visitor and assistant. Hidden prevents new selections; it does not cancel an existing attempt. Use Classifications and Recommended for to suggest a form for particular needs.
Available for these languages controls eligibility based on a visitor's observed languages, interface language, or explicit requested form language. It does not choose the language sent to the destination. See Languages and translations.
Define fields in collection order
Each field needs the exact Form field name expected by the receiving form. A visitor question also needs a clear Question label and answer type.
| Field source | Purpose |
|---|---|
| Ask the visitor | Collect or prefill an answer the visitor can review. |
| Fixed value | Send a configured value without asking a question. |
| Copy another field | Reuse an earlier field's answer for another destination field. |
Use Plain text for names, companies, addresses, and identifiers that must stay unchanged. Use Free text or Free text, multi-line for descriptions eligible for submission translation. Email address validates email format. The phone answer type currently applies no phone-number validation. A choice pairs a visitor-facing label with the exact submitted value expected by the destination.
Mark fields Required when an answer is necessary. A copied field must refer to a field earlier in the form. Do not create two fields with the same destination field name.
Connect delivery and translation
Choose where to receive completed forms:
- Runs Agents workspace: Add a connection with this provider, then select it in your form. Confirmed submissions and their original answers stay in the workspace. Your team can review them in the conversation and receive submission notifications. No external form endpoint is needed.
- Contact Form 7: Select a Contact Form 7 connection and set the complete endpoint URL. Follow Connect Contact Form 7.
For Contact Form 7, optionally choose Submission translation. Only eligible free-text answers are translated for delivery. Names and identifiers must use appropriate non-translated field types. The original saved answers remain available for review.
What the visitor agrees to
The visitor agrees before form assistance starts. The assistant can prefill supported information from the conversation, collect missing required answers, and let the visitor correct them. It must not invent missing information.
The visitor then reviews and confirms the answers before submission. Consent to the interview and final confirmation are separate steps. A visitor may decline help, change form, or leave an unfinished form.
Interpret a submission result
For workspace delivery, success means Runs Agents has saved the confirmed submission. For Contact Form 7, success requires a successful response from the receiving form. An email notification is a separate action and does not determine the submission result.
An interrupted request can have an uncertain outcome. Check the current result and destination before repeating submission. During setup, test the complete route using synthetic information and confirm receipt at the actual destination.