> 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/frameora/sections/final-call-to-action.md).

# Final call to action

The Final call to action section displays a strong promotional message near the end of a page.

Use this section to encourage customers to take the next step, such as starting a custom order, visiting a product page, or learning how the product works.

### Open Final call to action settings

<figure><img src="/files/E46qvieTtaVU98uOu8nc" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
To edit the Final call to action section:

* From your Shopify admin, go to **Online Store > Themes**.
* Find **Frameora**.
* Click **Customize**.
* Open the page that contains the Final call to action section.
* Select **Final call to action** in the theme editor sidebar.
* Edit the section settings and badge blocks.
* Click **Save**.
  {% endhint %}

***

### Section content

The main section settings include:

* Kicker
* Heading
* Subheading
* Primary button label
* Primary button link
* Secondary button label
* Secondary button link

#### Kicker

Use the **Kicker** field for short text above the heading.

Example:

**READY TO START?**

#### Heading

Use the **Heading** field for the main call to action message.

Example:

**Create your wall of memories today**

#### Subheading

Use the **Subheading** field to explain the offer or action.

Example:

**Turn your favorite photos into peel-and-stick tiles made to move, restick, and brighten every room.**

Keep the message short and action-focused.

***

### Primary button

The primary button should link to the most important action.

Settings include:

* Primary button label
* Primary button link

Example:

**Primary button label:** Create Your Tiles\
**Primary button link:** Your custom photo tile product page

***

### Secondary button

The secondary button can link to a supporting page or section.

Settings include:

* Secondary button label
* Secondary button link

Example:

**Secondary button label:** See How It Works\
**Secondary button link:** A how-it-works page or section

***

### Badge blocks

The Final call to action section includes **Badge** blocks.

Use badges to show short benefits or trust points.

Each Badge block includes:

* Badge text

Frameora supports up to **3 badge blocks** in this section.

Examples:

* Damage-free
* Easy to restick
* Ships fast

Keep badge text short so it stays readable on mobile.

***

### Best practices

Use the Final call to action section near the bottom of high-intent pages.

Good final calls to action are:

* Clear
* Direct
* Benefit-focused
* Linked to an active product, collection, or page
* Easy to understand on mobile

Before publishing, test both button links.

***

### Save your changes

After editing the Final call to action section, click **Save**.

If changes do not appear immediately, refresh the storefront or open the page in a private browser window.


---

# 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/frameora/sections/final-call-to-action.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.