Verify form collection in AI conversations
Choose a website AI entry point or supported phone template that receives a form.
After this taskForm ID, customer and final answers match the test conversation.
Starting conditions and inputs
Identify the form and account used by the AI.
Values for this task
entry_url, form_id, account_id, test_answers, conversation_id, submission_url
Command sequence
open "$entry_url" && snapshot -i
# Outside browser: The test customer starts the collection conversation in the specified channel.
snapshot -i
click "$conversation_row" && snapshot -i
get text body
# Outside browser: The test customer answers one field at a time and tests a missing or invalid value.
snapshot -i
reload && snapshot -i
get text body
open "$submission_url" && snapshot -i
get text bodyRef targets and expected results
| # | Command / ref | Target and verification |
|---|---|---|
| 1 | Outside browser | The test customer starts the collection conversation in the specified channel. |
| 2 | click $conversation_row | Test customer conversation |
| 3 | get text | Read the question and field being collected. |
| 4 | Outside browser | The test customer answers one field at a time and tests a missing or invalid value. |
| 5 | reload | Reload the same test conversation. |
| 6 | get text | Compare follow-up questions for invalid values and the completed result. |
| 7 | open | Resulting submission record |
| 8 | get text | Compare test answers with stored values. |
Check the result
Form ID, customer and final answers match the test conversation.
Resuming after interruption
Check the original request ID and outcome first. Do not resubmit while its result remains unknown.
Confirm the supported entry point
Choose a website AI entry point or supported phone template that receives a form. Not every messenger conversation automatically starts the same collection task. Check the selected account and entry action.
Connect the form
Check the form goal, required fields, and public scope, then connect it to the AI action. Put collection context in the form prompt without duplicating field rules. For existing reservations, verify the target and access.
Test representative answers
Test answers one at a time and several at once. Test unknown values, corrections, and stopping midway. Check that AI does not invent required answers or submit values the customer did not provide.
Compare submitted results
Compare the final submission with customer or reservation records. An AI acknowledgement alone does not prove storage. Count incomplete conversations separately from completed submissions to observe collection drop-off.