Loading…
Loading…
Forms
Workspace-owned questionnaires you design once and reuse across web embed, optional lead capture before chat, and Flows. Every submission is stored with an ID, can update standard and custom contact fields, and shows up in Contacts, Analytics, and the conversation timeline.
In the product: Workspaces → Forms → /workspaces/forms
| Name | Title | Submit text | Actions |
|---|---|---|---|
LeadSeed | Get in touch | Submit | |
SupportSeed | Support request | Submit | |
School Admission Form | — | Submit |
Purpose
Marketing, support, and automation stay aligned when the same workspace form powers embed, lead capture, and Flows—and writes into one contact record.
Replace messy free text with validated fields—required rules, choice lists, and dropdowns—before or during a conversation.
Set the title, submit label and hex color, the intro line before the form opens in chat, and thank-you copy after a successful submit.
Map each answer to first name, last name, email, phone, organization, job title, or workspace custom fields—no manual copy-paste.
Drop a Show form step into a Flow for mid-journey capture; submissions get stable display IDs for support references and reporting.
At a glance
The rows below mirror the live product: builder, API, embed, Flows, and how submissions surface in Contacts and Analytics.
| Area | What ChatMaven provides |
|---|---|
| Form types | Lead, Support, and unlimited custom forms per workspace. Seed forms are created when you first open the Forms page so you can start immediately (Seed badge in the list). |
| Field types | Text, Textarea, Single choice, Multi choice, and Dropdown—each with label, placeholder, required, reorder, and remove. |
| Field configuration | Auto field keys from labels (normalized slug). For choice types, options are one label per line. Fields can be marked inactive alongside required and order. |
| Contact mapping | Per field: do not map, standard keys (first name, last name, email, phone, organization, job title), or workspace custom fields from Workspaces → Custom fields. Optional custom key text for advanced cases. |
| Form chrome | Internal form name, public title, message before the form opens in chat (clear for no line), submit button text, submit color with hex and picker, thank-you header and body after submit. |
| Lifecycle | List all workspace forms; add; edit in a full-screen modal; delete deactivates the form—agents still pointing at it need another form assigned. |
| API | REST under the workspace: GET/POST /workspaces/:workspaceId/forms and GET/PUT/DELETE …/forms/:formId—same patterns as the rest of your workspace admin API. |
| Submission | POST /api/contacts/forms/submit validates required fields, ensures the form belongs to the agent’s workspace, upserts contact data, inserts form_submissions, and returns confirmation. Supports embed context with agent unique id and optional chat session id to merge with the visitor session. |
| Embed | The widget loads form config when a response has responseType show_form—initial flow, streaming replies, or a queue of multiple forms. Agent Appearance controls show on open versus after N visitor messages. |
| Flows | Show form node: pick a workspace form by id. Optional per-flow field → contact overrides on the node when mapping should differ from the form default. |
| Downstream UI | Contacts → profile Forms tab lists submissions with view and edit where supported. Chat can show a readable “Form submitted” summary line. Analytics includes dedicated form submission views. |
In the product
Forms are workspace assets. Point your embed, lead capture, and Flow nodes at the same definition so answers always land on the same schema-backed contact.
Workspaces → Forms at /workspaces/forms. List, add, edit, and delete workspace-owned forms—the same sidebar surface as Agents, Flows, Templates, Tags, and Custom Fields.
Settings → Agent → Appearance to choose which workspace form powers lead capture and timing (show on open vs after N visitor messages). Combine with your embed snippet so visitors see the right experience.
Workspaces → Flows with a Show form step: pick a form by id and optionally override contact mapping for that flow only when defaults are not enough.
Typical usage
Confirm Lead and Support seed forms—or click Add form for a custom questionnaire. Seeds are suggestions you can edit or clear.
Use Text, Textarea, Single choice, Multi choice, and Dropdown. Set required flags and options (one label per line) where needed.
Point email, phone, and custom attributes at the right fields so submissions enrich Contacts without duplicate entry.
Customize title, intro chat line, submit label and hex color, plus thank-you header and body after a successful submit.
In Agent → Appearance, turn on lead collection and pick the form and timing. Optionally add a Show form step in a Flow for mid-journey capture.
Inspect submissions on each contact’s Forms tab and in Analytics—same submission IDs your team can reference in support tickets.
Structured capture without extra tools
Open Workspaces → Forms, map fields to your contact schema, connect Agent Appearance and Flow Show form steps, and keep Contacts, Analytics, and chat on one source of truth.
Free plan available · No credit card needed · Cancel anytime