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

# Contact page

The **Contact page** is where a visitor goes when they have a question your product pages did not answer: sizing, delivery, a wholesale request, or a problem with an order. It carries a form that sends the message straight to your store email, so nobody has to hunt for an address.

Visitors reach it from the footer or the main menu, and often just before a first order, because a store with a working contact route feels safer to buy from. Like the About us page, it does not exist until you create it in the Shopify admin and attach a theme template to it.

<figure><img src="/files/3TttdjMwWgXkTo08Tczx" alt=""><figcaption></figcaption></figure>

### Step 1: Create the page in the Shopify admin <a href="#step-1-create-the-page" id="step-1-create-the-page"></a>

{% hint style="success" %}
**Steps:**

1. Go to **Shopify admin > Online Store > Pages**.
2. Click **Add page**.
3. Fill in:
   * Title: `Contact`
   * Visibility: **Visible**
4. In **Theme template**, select `contact`.
5. Click **Save**.
   {% endhint %}

*Result:* the page exists at an address such as `/pages/contact` and uses the theme template with the contact form on it.

### Step 2: Arrange the sections <a href="#step-2-arrange-the-sections" id="step-2-arrange-the-sections"></a>

{% hint style="success" %}
**Steps:**

1. Go to **Online Store > Themes > Customize**.
2. Open the template selector and choose **Pages**, then your Contact page.
3. Adjust the sections in the left sidebar, including the contact form itself.
4. Click **Save**.
   {% endhint %}

*Result:* the preview shows the contact layout with the form fields and labels you set.

{% hint style="info" %}
Messages sent through the form go to the sender email set in **Shopify admin > Settings > Store details**. Check that address is one you actually read before you publish the page.
{% endhint %}

### What is on this page <a href="#what-is-on-this-page" id="what-is-on-this-page"></a>

* [Page template sections](/velare/customize-your-pages/contact-page/page-template-sections.md): the sections the theme adds to this template by default.
* [Contact form](/velare/customize-your-pages/contact-page/contact-form.md): the form settings, from field placeholders to the enquiry dropdown.

### Related pages <a href="#related-pages" id="related-pages"></a>

* [About us](/velare/customize-your-pages/about-us.md): the page that usually sends visitors here once they trust the brand
* [FAQ page](/velare/customize-your-pages/faq-page.md): answers the routine questions before they turn into an enquiry
* [Footer](/velare/set-up-your-store/footer-group/footer.md): where the Contact link normally sits


---

# 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://uxsmart.gitbook.io/velare/customize-your-pages/contact-page.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.