> For the complete documentation index, see [llms.txt](https://docs.subscripta.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.subscripta.app/welcome-to-subscripta.md).

# Welcome to Subscripta

Subscripta is a professional email signature builder and manager for teams.

Use this documentation to learn Subscripta from zero to production rollout: create an account, build signatures, organize departments, share signatures with employees, export to email clients, review analytics, and understand what each plan includes.

## What Subscripta Does

Subscripta lets individuals and teams create, manage, and deploy branded email signatures. It includes a live-preview visual builder, reusable templates, custom brand styles, click analytics, campaign banners, QR code vCards, and multiple export modes for different email clients.

## Main Workflows

* Build and customize a branded email signature.
* Export the signature for Gmail, Outlook, Apple Mail, webmail, desktop clients, image fallback, or plain text.
* Install the signature in the sender's email client.
* Send test emails to verify rendering in Gmail, Outlook, Apple Mail, and mobile clients.
* Track clicks from saved signatures.

***

## Recommended Starting Points

<table data-view="cards"><thead><tr><th align="center"></th></tr></thead><tbody><tr><td align="center"><a href="/getting-started/complete-walkthrough.md">Complete Walkthrough</a></td></tr><tr><td align="center"><a href="/getting-started/create-your-account.md">Create your Account</a></td></tr><tr><td align="center"><a href="/getting-started/launch-checklist.md">Launch Checklist</a></td></tr><tr><td align="center"><a href="/exports/which-export-should-i-use.md">Exports and Formats</a></td></tr><tr><td align="center"><a href="/installation-guides/installation.md">Signature Installation</a></td></tr><tr><td align="center"><a href="/troubleshooting/images-logos-icons-not-loading.md">Troubleshooting</a></td></tr></tbody></table>

## Plans at a Glance

| Plan     | Best For                                                                                                           | Main Limits                                                                                          |
| -------- | ------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------- |
| Free     | Testing the builder and creating a small number of signatures.                                                     | 2 signature slots, up to 2 departments, 1 saved style.                                               |
| Pro      | Professionals and teams that need analytics, QR vCards, advanced editing, banner tracking, and saved brand styles. | 50 signature slots, 10 saved styles, 30-day analytics.                                               |
| Business | Companies and agencies managing larger teams and public WebCards.                                                  | 200 signature slots, 50 saved styles, all-time analytics, WebCard, CSV import/export, bulk creation. |

For the full breakdown, see [Plans and limits](/account-and-billing/plans.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://docs.subscripta.app/welcome-to-subscripta.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.
