Forms run inside the conversation itself, one question at a time, and every answer lands on the contact record where you can segment and branch on it.
A form that sends someone to a web page loses most of them at the tap. This one never leaves the conversation.
Triggered on a keyword, so nobody has to remember to send it.
triggerOne thing at a time, phrased as a person would ask it.
question 1Validated against the sizes in your catalog, then stored.
validated31st February is refused, and the question is asked again politely.
re-askedSize and date are fields now, not text buried in a chat log.
fields setThe journey books it and confirms, using her own answers in the message.
bookedYes. Forms run inside the conversation itself, one question at a time, and every answer lands on the contact record. There is no link to tap and no page to load.
It is asked again. Answers are validated, so a malformed date or an unavailable size is refused rather than silently accepted, which is the difference between usable data and noise.
As fields on the contact record. That means you can segment on them, branch a journey on them and personalise a message with them, rather than reading a dead-end submission.
Yes, a form can be published as a public link when a conversation is not the right place.
Yes. Consent is checked in the data layer before a form is sent, and a form cannot open a conversation outside the messaging window without an approved template.
