Build a form once and use it two ways: as a card inside a chat, or as questions the assistant asks one at a time in conversation. Every question maps to a data point, so answers land on the right contact automatically. Purely browsing visitors are never asked; a form appears when someone is engaging.
Pick a ready-made form (new patient inquiry, appointment or callback request, insurance pre-check, or patient feedback) and it is copied into a draft you can customize. The original template is never changed, so your edits stay entirely yours.
Assemble a form from a catalog of common fields (name, email, reason for visit, urgency, consent, and more) or add your own custom field. Because each question is tied to a data point, what you collect stays consistent and reportable.
Each question has a type and a control: short text, paragraph, number, date, dropdown, radio, checkbox, multi-select, a rating, or a consent toggle. Answers are checked as they come in, so a bad email or empty required question is caught before it is stored.
Reveal a question only when an earlier answer calls for it, so people see a short, relevant form instead of a long one.
The same form renders as an in-chat card with real controls, or as a friendly back-and-forth where the assistant asks one question at a time. You author it once.
As a form is completed, answers are written onto the person's contact record: their details, interests, and consent. Sensitive clinical questions are routed to your records system rather than stored here.
Publishing a form sets its version, and every response records the version it answered, so later edits never scramble older answers. The Responses tab shows completion rate and where people drop off.