> 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/builder/create-your-first-signature.md).

# Create your first signature

The Builder is where you create and save signatures.

## Steps

1. Open **Builder**.
2. Choose a template from the template selector, or start from the default template.
3. Fill in the required fields:
   * Full name
   * Email
4. Add optional identity fields:
   * Job title
   * Department
   * Phone
   * Website
   * Company name
5. Add social links if needed.
6. Add profile photo, company logo, or banner assets.
7. Choose primary color, accent color, and font.
8. Enable QR code if the signature should include a vCard QR code.
9. Review the live preview.
10. Click **Save Signature**.

## Plan Notes

* Free: up to 2 saved signatures.
* Pro: up to 50 saved signatures.
* Business: up to 200 saved signatures.
* QR Code vCard requires Pro or Business.
* Advanced visual editing requires Pro or Business.
* WebCard public pages require Business.


---

# 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.subscripta.app/builder/create-your-first-signature.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.