Create and publish a consultation form
Build the current Laney consultation form with customer and reservation groups, then test a public submission.
This tutorial reproduces the current Consultation request form. The customer enters contact data, a lasting consultation goal, and request-specific reservation data on one page. Laney saves each value to its correct owner.
Build this structure
| Location | Fields | Setting |
|---|---|---|
| Contact details | Name, email, and phone | Customer basic fields. Do not duplicate them. |
| Contact details | Consultation goal | Customer, Text Area, required, has a Description |
| Contact details | Interests | Customer, Multi Select, optional |
| Reservation | Start time and notes | Reservation basic fields |
| Consultation details | Consultation type | Reservation, Select, required, condition gate |
| Consultation details | Other details | Reservation, Text Area, required when type is Other |
| Consultation details | Preferred channels | Reservation, Multi Select, optional |
| Consultation details | Background notes | Reservation, Markdown, optional |
Use Profile Then Insert, Public, and the starts_at and notes basic fields.
Read the video steps
- Open the consultation form in Forms.
- Review the customer-facing title, description, and success message.
- Keep only extra AI operating context in Prompt.
- Set Mode to Profile Then Insert.
- Use Public access for new consultation requests.
Before you begin
- Select the organization or branch that owns the form.
- Check the landing domain and hero image. A full-page public form uses the same brand image.
- Prepare synthetic contact and request data.
- Check availability rules before you collect a reservation time.
Do not recreate contact fields
Name, email, and phone are customer basic fields. A duplicate custom field can make the contact section repeat or make the form configuration invalid.
1. Define the form action
- Open Forms. Select Add.
- Enter
consultation-requestfor Slug. - Add a localized Label, Description, and Success Message. Tell the customer why you need the data and what happens next.
- Select
starts_atandnotesin Static Fields. - Select Profile Then Insert for Mode.
- Select Public for Access.
- If an AI CTA will use the form, add only extra operating context in Prompt. Do not repeat the questions. Do not put secrets in it.
- Turn on Active. Save the form. Do not share the link until testing is complete.
2. Add lasting customer fields
Open Custom fields. Create these fields. Search for the real form in Forms. Do not enter an arbitrary slug.
| Setting | Consultation goal | Interests |
|---|---|---|
| Target | Customers | Customers |
| Key | consultation_goal | learning_interests |
| Kind | Text Area | Multi Select |
| Description | Explain what the customer must include. | Tell the customer that several values are allowed. |
| Field Group | Customer details | Customer details |
| Visibility | Public | Public |
| Required | On | Off |
| Forms | consultation-request | consultation-request |
Profile Then Insert combines these fields with the contact basic fields. It does not create a
second customer group in the public form.
3. Add request-specific reservation fields
Set Target to Reservations, Field Group to Consultation details, and Forms to
consultation-request for each field.
| Key | Label | Kind | Required | Extra setting |
|---|---|---|---|---|
consultation_type | Consultation type | Select | Yes | Add the options that the organization serves. |
other_topic | Other details | Text Area | Yes | Set Show When to consultation_type=Other. |
preferred_channel | Preferred channel | Multi Select | No | Add the contact channels that you support. |
background_notes | Background notes | Markdown | No | Use for structured context or lists. |
Keep a gate and its follow-up in the same target, form, and group. Do not nest conditions. See Create conditional fields for the full rules.
4. Test the public form
Read the video steps
- Check the form-only layout and fixed hero image.
- Enter contact details and a lasting consultation goal.
- Select an available reservation date and time.
- Select Other and check that the follow-up appears.
- Enter background notes and confirm that only the form pane scrolls.
- Submit and wait for the success message.
- Copy the public link from Forms. Open it in a signed-out window.
- Check the fixed hero image on a wide screen and the single-column layout on a phone.
- Check that name, email, and phone each appear once.
- Read every Description. Check that customer and reservation fields are in the correct groups.
- Test the closed and open conditional paths.
- Enter synthetic values. Refresh before submission. Check that the draft returns.
- Submit once. The success message must appear only after the server write succeeds.
Check the result
Open the newest Submitted item in Responses. Compare Customers and Reservations.
| Location | Must contain | Must not contain |
|---|---|---|
| Customer | Contact details, consultation goal, and interests | Request-specific consultation fields |
| Reservation | Start time, notes, type, channels, and background | Copies of customer custom fields |
| Response | Submitted status, answers, field definitions, and linked targets | Data from another organization or branch |
Share the public link only after this check passes. Continue with Review responses and start follow-up work.
Understand the form system
Understand how one field definition connects public forms, AI conversations, customer accounts, tables, workflows, and response records.
Design descriptions, groups, and conditions
Define a question owner and meaning once. Use Description, Field Group, Forms, and Show When to create a clear form.