Forms captured
When an assistant fills out a form during a conversation — name, email, what they're looking for, preferred time, anything — that completed form lands here. It's the structured-data twin to the Conversations inbox: same conversations, but viewed as rows of clean fields instead of free-text transcripts.
The page lives at /captured-forms.
What you can do with it
- Lead intake review (real estate / mortgage) — A loan officer skims yesterday's "mortgage lead" form submissions: name, loan amount, credit range, timeline. Top 10 get called today; rest get nurture emails.
- Healthcare intake follow-up — A clinic's "new patient intake" form gets filled by the assistant on inbound calls. The front-desk team works the list each morning — confirming insurance, scheduling first visit.
- Survey rollups (e-commerce) — A brand runs a post-purchase NPS form via the chat widget. The forms page rolls every response into a sortable table for the CX manager.
Pick a form first
The page is per-form. You pick a form from the dropdown at the top, and the table reloads with that form's submissions. Columns are dynamic per form — they match the fields you defined on the form when you built it.
What each row shows
- When — submission timestamp.
- Conversation link — click to open the source conversation in the Conversations view.
- One column per form field — whatever the form defined.
What's not here
- No inline edit. Submissions are records of what was captured. To correct a value, edit the underlying contact in Contacts.
- No bulk action. Process rows one at a time, or pull via API for bulk handling.
Webhooks
Every form submission also fires the captured_form.created webhook (and captured_form.updated if the assistant updates a field later in the same conversation). See Form captured webhook.
Where to next
- Conversations — full transcript context for any submission.
- Contacts — the contact each submission was attached to.
- Form captured webhook — push submissions to your CRM in real time.