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

# Call to Action

Contact forms and newsletter signup sections in the Avante Shopify theme — collect customer inquiries and grow your email list.

Two sections for turning a visitor into a contact — a two-column contact page built around Shopify's contact form, and a full-width image banner with an email signup on top of it.

***

### Section overview

| Section                                                                                    | What it does                                                                                                                                               |
| ------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Contact Form](/docs/avante-themes/sections/call-to-action/contact-form-and-newsletter.md) | Shopify's contact form — name, email, optional phone and message — in one column, with your contact details, social profiles, and text blocks in the other |
| [Newsletter](/docs/avante-themes/sections/call-to-action/contact-form-and-newsletter.md)   | Email signup over a full-width image; subscribers are created as Shopify customers tagged `newsletter`                                                     |

***

### Quick decision guide

**Need people to reach you?** → [**Contact Form**](/docs/avante-themes/sections/call-to-action/contact-form-and-newsletter.md) — messages are delivered to the store contact email set in your Shopify admin, and the second column can carry your address, opening hours, and social links.

**Want email signups for marketing?** → [**Newsletter**](/docs/avante-themes/sections/call-to-action/contact-form-and-newsletter.md) — subscribers land in Shopify Customers with the `newsletter` tag, ready to segment or sync to your email app.

**Both on one page?** → They work independently, but keep them apart — two forms in the same screen and neither gets filled. A newsletter banner near the bottom of a page and a contact form on a dedicated contact page is the usual split.

***

### Shared features

Both sections support color scheme overrides, separate desktop and mobile paddings, and an optional consent checkbox with your own rich-text label. Both are template sections — they're added to a page, not to the header or footer areas.

Full setup details: [Contact Form & Newsletter](/docs/avante-themes/sections/call-to-action/contact-form-and-newsletter.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://staylime.com/docs/avante-themes/sections/call-to-action.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.