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

# Contact form

The contact page: an eyebrow, a heading, intro text, and a form (name, email, optional phone, message). Submissions arrive by email at your store's sender address, and the visitor sees "Thanks — we'll get back to you shortly."

👉 Setup: create a page under **Online Store → Pages** and assign it the **contact** template, then customize via **Customize → page selector → Pages → your contact page**. Step-by-step: [Pages → Contact](/sitesbyseth-docs/showcase/pages.md#contact).

## Settings

* **Eyebrow** (default "SUPPORT") — small label above the heading.
* **Heading** — falls back to the page's title when empty.
* **Intro text** (rich text) — falls back to the page's content when empty.

## Pro tip

💡 Use the intro text to head off your most common question before the form: "Sizing question? Every product has a Find my size tool — for anything else, write us below." Fewer tickets, faster answers.


---

# 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://sitesbyseth.gitbook.io/sitesbyseth-docs/showcase/sections/main-contact.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.