Review responses and start follow-up work
Review the submission state, saved answers, and target record. Use the same custom-field values in table filters and workflows.
A customer success message is not the end of the operating check. Open Responses. Verify the final state and linked customer or reservation. The response ledger connects the input surface to the operating record.
Read the video steps
- Check that the newest response is Submitted.
- Open it. Review the submission time and target.
- Compare Answers and Definition.
Understand status
| Status | Meaning | Admin action |
|---|---|---|
| Draft | The customer changed a value but has not submitted. | Let the customer resume. Do not count completion. |
| Submitting | The final write is running. | Refresh later. Do not create a manual duplicate. |
| Submitted | Server validation and the target action completed. | Check the customer or reservation. Start follow-up work. |
| Failed | The final action did not complete. | Investigate with time and synthetic steps. Do not copy customer answers. |
1. Review the latest response
- Open Responses.
- Find the item by form, status, target, or submission time.
- Check that Status is Submitted.
- Review the basic and custom values in Answers.
- Review the submitted Label, Description, Kind, Options, Field Group, and condition in Definition.
- Open the linked customer or reservation.
A final response is read-only. Its Definition keeps the meaning used at submission time after you change the current field. Form Prompt is not part of this snapshot. It is an AI operating instruction, not a customer answer.
2. Check customer and reservation ownership
For Profile Then Insert, compare both targets.
| Value | Location |
|---|---|
| Name, email, and phone | Customer basic data |
| Consultation goal and interests | Customer custom fields |
| Start time and notes | Reservation basic data |
| Type, Other details, channels, and background | Reservation custom fields |
If request data is on the customer or customer data is copied to the reservation, deactivate the form. Correct the Target with Design descriptions, groups, and conditions.
3. Find the same value in a table
- Open Customers or Reservations.
- Show the required custom-field columns under View.
- Add the kind-specific search or filter from the column header.
- Find reservations where Consultation type is Other or Preferred channel contains Email.
- Save a frequently used query. Reopen it and check that the custom-field condition remains.
Text, Text Area, and Markdown use text search. Select filters one option. Multi Select filters a contained option. File does not provide an unsafe value filter.
4. Use the same key in a workflow
Use the stable field Key as custom.<key> in
Workflows.
query:
where:
"custom.consultation_type": { eq: "Other" }
"custom.preferred_channel": { contains: ["Email"] }Start with synthetic rows and a small limit. Check the selection before you add assignment, notification, or state-transition actions. A Label change does not break the saved query or workflow when the Key keeps the same meaning.
5. Compare AI and landing conversion
A visual form and a form-goal AI conversation use the same response ledger. Use a Submitted response and its linked target as completion.
- Review customer confirmation in Conversations.
- Review the final form and answers in Responses.
- Review the operating result in Customers or Reservations.
- Count the final response as the landing or campaign conversion.
Do not confuse a chat start or button click with a completed request.
Check the result
- The response is Submitted.
- Answers and Definition preserve the submission-time contract.
- Customer and reservation records contain only their owned values.
- Kind-specific table filters find the expected rows.
- A saved query restores the same custom-field conditions.
- A workflow selects only synthetic rows with the same
custom.<key>.