Chat
When can you talk?
yeah tuesday works
after 3 is better
Structured context
Messy in. Typed out.
Respondents type like people. The agent maps that into fields, then ships a webhook payload and an MCP-ready object.
Structured context
Speak to the form agent. Get structured context.
People chat or leave a voice note. The agent listens on the left. Crystal-clear fields come out the other side: company, meeting time, intent, and a payload your stack can use.
Speaking to the agent
Voice
0:18
budget around forty k. need it before the offsite.
Chat
What company is this for?
acme inc, east coast team
Structured context
Convex
Typed fields land in the dashboard as a complete record.
Webhook
The same object fires to your endpoint, not a CSV dump.
MCP
Existing agents can read the submission without scraping chat.
Why it matters
Agents need objects, not screenshots of chat
A freeform reply, a company name typed loosely, a PDF dropped in the thread, and a short voice note can become company, meeting_at, intent, and a file URL. The dashboard shows the fields. Your webhook receives the same object.
That is structured context. It is the difference between a conversation you have to reread and a record another agent can use.
The transform on this page is a sample intake. It is illustrative, not live traffic. The live path is the published form you build and the destinations you configure.
Sample record
What ships after the chat
- company
- text
- Northwind Labs
- meeting_at
- datetime
- 2026-08-25T15:00:00Z
- intent
- choice
- pilot
- brief
- file
- intake.pdf
Ready to collect answers without a page of fields?
Publish a conversation. The agent keeps asking until every required block is filled.