Understand the form system
Understand how one field definition connects public forms, AI conversations, customer accounts, tables, workflows, and response records.
A Laney form is not a separate survey data store. Define a question and its value rules once in Custom fields. Laney uses that definition in public forms, dashboard tables, AI conversations, and workflows. A Form combines the fields and write action for one customer task.
One contract, many input surfaces
| Part | What you set | Where Laney reuses it |
|---|---|---|
| Custom field | Target, key, label, description, kind, group, condition, and form scope | Public forms, dashboard editors, table filters, AI questions, and workflow conditions |
| Form | Address, content, basic fields, Mode, Access, and AI Prompt | Landing CTAs, links, AI goals, and the response ledger |
| Response | You do not create it directly. | It keeps the draft or final answers and the field definition used at submission time. |
| Customer account | The organization's platform sign-in providers | It shows a customer only their reservations, drafts, and submitted responses. |
For example, define Consultation type once as a Select field. The form and AI use the same
options. The reservation table filters the same value. A workflow reads it as
custom.consultation_type.
The consultation example in this guide
| Form group | Fields | Owner | Reason |
|---|---|---|---|
| Contact details | Name, email, and phone | Customer basic data | Do not duplicate existing contact fields. |
| Contact details | Consultation goal and interests | Customer | Keep these values for later visits and AI conversations. |
| Reservation | Date, time, and notes | Reservation basic data | They belong to this reservation. |
| Consultation details | Type, Other details, channels, and background notes | Reservation | These values can change for every request. |
The Description for Consultation goal becomes helper text under the input. The Field Group named Consultation details puts related questions in one section. Other details appears only when the customer selects Other.
Read the video steps
- Open Consultation goal in Custom fields.
- Review its customer-facing label and description.
- Review its Field Group and Forms scope.
- Open Consultation type and review its conditional follow-up.
- Use the same key in forms, tables, AI, and workflows.
Form modes
Mode | Action | Common use |
|---|---|---|
Update Self | Update the current visitor or linked customer. | Intake and profile update |
Insert | Create a reservation for the linked customer. | Reservation intake for a known customer |
Profile Then Insert | Save contact and customer fields, then create a reservation. | Public consultation or reservation request |
Update Target | Update the reservation fixed in a secure link. | Reservation change or pre-visit questions |
The example uses Profile Then Insert. The customer sees one page. Laney still saves lasting
customer values and request-specific reservation values to their correct owners.
Forms and AI share one goal
Connect a landing-page AI CTA to a Form. The valid form submission becomes the conversation goal. AI uses the Form Prompt as extra context. It gets its questions, options, required rules, and conditions from the same fields as the visual form. A completed AI conversation creates a normal Response.
Customer sign-in adds a personal workspace
Connect Kakao, LINE, or Meta platform sign-in for the organization. A signed-in customer can use
/account to view only their own reservations, drafts, and submitted responses. The same identity
supports cancellation, draft resume, and secure change links. Public intake can still work without
sign-in.
Submission keeps both the result and the evidence
Laney saves changed values as a resumable draft. Final submission validates the current field contract on the server. It removes unknown and hidden values. Retrying one submission does not run the customer or reservation action twice.
A final response keeps the form version, answers, and field definitions used at submission time. You can still understand an old response after you change a label or option.