Form and custom field reference

This reference describes how form and custom field settings affect customers, reservations, and operating features.

Find form settings in Forms and field settings in Custom fields. Verify writes in Customers, Reservations, and Responses. Open Workflows to automate a query. Select the decision below and open the related section.

Form settings

Modes

The Profile Then Insert contact group includes name, email, and phone. It also includes public customer custom fields in the form. A new or saved phone number is required so the organization can confirm the reservation.

Basic fields

When Static Fields contains keys, the form shows only those keys. A key outside the target's public fields invalidates the form.

Custom field settings

Do not duplicate a key within one organization and target. Do not use name, email, or phone for customer custom fields in Profile Then Insert.

Custom field kinds

Public visibility does not make every kind safe for customer input. Member, Entity, and Organization remain internal-only. File stores a public HTTP URL and uploads into the current visitor's scoped Storage path. Unknown future kinds also fail closed.

Form scope

This table applies to a public-safe field with Public visibility.

Leave the scope empty for a field with one meaning across channels. For an event or campaign field, search and select actual forms in Forms. Free text and Enter cannot create an unknown slug. Selecting several forms reuses one field definition and storage key. Form scope does not change the value owner or internal table visibility.

Tables, queries, and automations

Customer and reservation tables show each custom field as a column with its Label. The column header provides a search or filter that matches the field kind. Saved table queries keep custom field filters with other conditions.

Automation and technical references use a custom.<key> path.

query:
  where:
    "custom.consultation_type": { eq: "Other" }
    "custom.preferred_channel": { contains: ["Email"] }

This query selects reservations with an Other consultation and an Email preferred channel. See Automation query reference for the full grammar.

AI form goals

Select a public form on a landing AI CTA. Final submission of that form becomes the conversation goal. Field kinds, options, required rules, and conditions also apply to AI submission. A field scoped to that named form is included when AI targets the same form.

An AI goal uses only a Public form. Do not send a Token form or customer-bound secure link into a conversation. Retries in one conversation do not duplicate the response or customer and reservation work. See Connect an AI conversation to a form goal.

Customer account

Connected Kakao, LINE, or Meta sign-in providers appear at /login on the tenant landing site. A signed-in customer can use /account to review owned reservations, form drafts, and submitted responses. They can cancel a pending or confirmed reservation. They can start a secure change when an active Update Target Token form exists. See Connect customer sign-in and reservation management.

Compare representative configurations

These are synthetic configuration examples. Include only the fields required for the operation. Before sharing a link, use Choose public or secure form access to check data sensitivity and record binding.

Draft and final submission

• A named form saves a draft after a value changes.
• An address with resume information restores an unsubmitted draft.
• A draft can omit required values.
• Final submission validates active required fields and value types.
• The write removes unknown keys and hidden conditional values.
• One submission key changes the customer or reservation once.
• A final submission keeps the form version, field definitions, and answers.
• The success message appears only after the write completes.

Use Create and publish a reservation form for setup. Use Test and troubleshoot a form for failure symptoms.