> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/sa-request-a-quote/help/contact-support.md).

# Contact support

How to reach the SA Request a Quote team, and what's worth including so the first reply is a useful one.

## Email us

[**support@samita.io**](mailto:support@samita.io)

## From inside the app

The dashboard has a **Need any help?** section with three routes, so you don't have to leave your admin:

<table><thead><tr><th width="230">Option</th><th width="150">Button</th><th>Use it for</th></tr></thead><tbody><tr><td>Help docs</td><td><strong>Learn more</strong></td><td>Opening this documentation.</td></tr><tr><td>Get email support</td><td><strong>Contact us</strong></td><td>Anything that needs someone to look at your store.</td></tr><tr><td>Start live chat</td><td><strong>Start chat</strong></td><td>A quick question, when chat is available.</td></tr></tbody></table>

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2Fgit-blob-98450088c984a6647af22822f9b085ff37b9cd2d%2FScreenshot%202026-09-30%20at%2000-43-00.png?alt=media" alt="The app dashboard with the Need any help section outlined in red"><figcaption><p>Help, email support and live chat all sit at the bottom of the dashboard.</p></figcaption></figure>

**Contact us** is also in the app menu in your Shopify sidebar, below **Pricing plans**.

{% hint style="info" %}
**Pricing plans** lists **24/7 email support** under **What every plan gets you**, so email is available whichever plan you're on. The page itself is the authority on what your plan includes.
{% endhint %}

## What's worth including

Storefront problems are much easier to answer when the reply doesn't have to start with questions. These four usually save a round trip:

<table><thead><tr><th width="230">Include</th><th>Why it helps</th></tr></thead><tbody><tr><td>Your store URL</td><td>Lets someone look at your actual settings and theme rather than guessing.</td></tr><tr><td>A link to the page with the problem</td><td>A specific product or collection URL is far more useful than "the product page".</td></tr><tr><td>A screenshot</td><td>Shows exactly what you're seeing, including anything your theme is doing.</td></tr><tr><td>What you expected instead</td><td>Separates a bug from a setting that just needs changing.</td></tr></tbody></table>

{% hint style="info" %}
If the problem is with an email, also say which address you tested and roughly when. Quote notifications are sent from **<no-reply@samita.io>** unless you have set up your own **SMTP** provider, so say which of the two applies.
{% endhint %}

## Things the app itself points at support for

A few settings say to get in touch rather than offering a button:

<table><thead><tr><th width="270">Where</th><th>What it says</th></tr></thead><tbody><tr><td><strong>Quote PDF template</strong></td><td>"Remove the watermark from your PDF. Please contact us to verify your store and receive this service for free." See <a href="/sa-request-a-quote/pdf-templates/quote-pdf.md">quote-pdf.md</a>.</td></tr><tr><td><strong>Admin email</strong>, in the <strong>Mail notifications</strong> editor</td><td>"A maximum of 5 addresses is allowed. Contact us to increase the number of emails added." See <a href="/sa-request-a-quote/emails/change-recipients.md">change-recipients.md</a>.</td></tr></tbody></table>

Theme-specific button placement is the other common one — if your theme puts its buy buttons in unusual markup, the quote button may not land where you expect, and that's worth sending in with a product URL.

## Before you write

Many issues have a documented fix that's faster than waiting for a reply:

* [Troubleshooting](/sa-request-a-quote/help/troubleshooting.md) — quote button missing, prices still showing, blank quote pages, emails not arriving
* [FAQ](/sa-request-a-quote/help/faq.md) — short answers to common questions
* [Plan comparison](/sa-request-a-quote/reference/plan-comparison.md) — if a feature seems missing, check it's on your plan

{% hint style="success" %}
A feature you can't find is often a plan difference rather than a fault. Open **Pricing plans** in the app menu to see which plan you're on and what it includes.
{% endhint %}

## If you're asked for access to your store

Some theme-specific problems can't be diagnosed from the outside, so you may be asked for collaborator access. That's yours to grant or refuse: you set it up in your own Shopify admin, and you can revoke it once the issue is resolved.

{% hint style="warning" %}
Don't send your Shopify password to anyone, including us. Collaborator access is granted through Shopify's own system and never needs it.
{% endhint %}

## Legal and privacy

* [Privacy policy](https://docs.samita.io/privacy-policy)
* [Terms and conditions](https://samita.io/pages/terms-and-conditions)
* [Permissions and data](/sa-request-a-quote/reference/permissions-and-data.md) — what the app accesses and stores

## Next steps

* [Troubleshooting](/sa-request-a-quote/help/troubleshooting.md) — check the common fixes first
* [FAQ](/sa-request-a-quote/help/faq.md) — quick answers
* [Pricing plans](/sa-request-a-quote/settings/pricing-plans.md) — check what your plan includes


---

# 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://docs.samita.io/sa-request-a-quote/help/contact-support.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.