> For the complete documentation index, see [llms.txt](https://docs.lufavo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lufavo.com/roomfolk/sections/contact-form.md).

# Contact form

A contact form — name, email, phone, message — with an optional subject field.

## Set it up

1. Add the section to a page, or use the Contact page which already has it.
2. Write a heading and a line of description.
3. Decide whether you want a subject field.

Messages arrive at the email address in **Settings → Store details → Sender email**. Check that is an address you actually read.

## Content

| Setting              | What it does                                                            |
| -------------------- | ----------------------------------------------------------------------- |
| Heading              | The form heading.                                                       |
| Description          | A line under it.                                                        |
| Required fields note | Explains the asterisk on required fields. Clearing it removes the line. |
| Button label         | The submit button text.                                                 |

Email and message are required; name and phone are not. The note explains the asterisk, so leave it in unless you have a reason not to.

## Subject field

| Setting              | What it does                                                       |
| -------------------- | ------------------------------------------------------------------ |
| Show a subject field | Adds a field letting the customer say what their message is about. |
| Subject label        | The field's label.                                                 |
| Subject options      | One per line.                                                      |

**The options control what kind of field it is.** List some options and the customer picks from a menu. Clear them all and it becomes a text field they fill in themselves.

A menu is better if you want to route messages consistently; a text field is better if your enquiries do not fall into neat categories.

## Layout, spacing and style

| Setting        | What it does                                 |
| -------------- | -------------------------------------------- |
| Heading size   | Small, Medium or Large.                      |
| Alignment      | How the heading and description are aligned. |
| Top spacing    | 0px to 120px.                                |
| Bottom spacing | 0px to 120px.                                |
| Button style   | Primary, Secondary or Accent.                |
| Color scheme   | Which scheme the section uses.               |

## What happens after someone sends one

The form reloads with a confirmation message. If something was wrong — a mistyped email address — it comes back with an explanation and the fields still filled in, so nobody has to retype their message.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.lufavo.com/roomfolk/sections/contact-form.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.