> ## Documentation Index
> Fetch the complete documentation index at: https://docs.notfy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Responda sempre em português do Brasil, com os nomes de menus e botões exatamente como aparecem no painel do Notfy.
> Use somente o que está documentado aqui. Se a documentação não cobrir a pergunta, diga isso e indique a página mais próxima em vez de inventar.
> Funcionalidades podem depender do plano, do segmento da empresa, das permissões do usuário e de integrações ativas: cite essa condição quando a página a mencionar.
> Nunca peça nem repita senhas, tokens ou dados pessoais de clientes.

# Send contract for signature

> Create a signature request from the customer or prospect record: signer data, template, payment, identity options and review.

The **Create Signature Request** wizard builds the contract from a template, sends it to ZapSign and generates the link for the signer.

## When to use

To collect a customer's or prospect's signature on a contract, proposal or term.

## Before you start

* [ZapSign](https://docs.notfy.ai/en/contratos/configurar-zapsign.md) integration active.
* At least one [contract template](https://docs.notfy.ai/en/contratos/templates-de-contrato.md).
* The signer must have an **email**. Without it, the request is not created.

## Create the request

**1. Open the record**

Open the customer and go to the **Digital Signatures** tab, or open the prospect and go to the **Signature Requests** tab.

**2. Start the wizard**

Click **Create Signature Request**.

**3. Signer Data**

Enter **Document Name**, **Signer Name**, **Signer Email** and **Signer Phone**. Name, email and phone come from the record and can be adjusted.

**4. Contract Template**

Choose the **Contract Template**. The **Template Variables** section appears for you to fill in the values the template asks for. In companies with the vehicles module, there is also the **Vehicle** field: it is reserved on creation and marked as sold on signing.

**5. Payment**

After choosing the template, the **Payment** step appears, already filled in with the template's default condition. Adjust if necessary. See [Payment plans](https://docs.notfy.ai/en/contratos/planos-de-pagamento.md).

**6. Advanced Options**

Define the identity verification for this document. See the table below.

**7. Review**

Check the preview and confirm. A notification confirms the creation; the document is prepared and the signature link appears shortly.

## Advanced options

| Field | What it is for |
| :- | :- |
| **Authentication Mode** | Identity verification method required from the signer. |
| **Selfie Validation Type** | Selfie verification. Overrides the integration's default for this document. |
| **Signer Identity Requirements** | Require CPF, validate CPF (Receita Federal), require RG. |
| **Photo Requirements** | Require selfie and document photo. |
| **Signer Qualification** | Signer's role, which appears in ZapSign's audit report. |
| **Redirect Link** | Address where the signer goes after signing (optional). |
| **Automatic Reminders** | Off, every 1, 3, 7 or 14 days, by email. |

## Send the link to the signer

On the document row, open **Actions**:

* **Copy Link**: copies the signature link. If the document is still being created, wait a moment.
* **Send via WhatsApp**: sends the link through WhatsApp. For customers, a **Message Template** must be defined in the [ZapSign integration](https://docs.notfy.ai/en/contratos/configurar-zapsign.md).

## Vehicle contract

On a vehicle's record, the **Generate contract** action opens the same wizard with an initial step to choose the buyer (customer or lead).

## When creation fails

| Message | What to do |
| :- | :- |
| **Validation Error** (email required) | Fill in the signer's email. |
| **Integration Error** | Check that the ZapSign integration is active. |
| Document with **Failed** status | The plan's signature limit may have been reached, or there may be an error in ZapSign. See [Track signatures](https://docs.notfy.ai/en/contratos/acompanhar-assinaturas.md). |

## Frequently asked questions

> [accordion] The prospect signed. What happens?
>
> They are moved in the funnel. If **Auto-convert Prospect to Customer** is on in the integration, the customer is created automatically.

> [accordion] Can I send the same contract to more than one signer?
>
> Each request has one signer. If the integration has a company representative, they are added as a co-signer.

## Related pages

> [card] [Track signatures](https://docs.notfy.ai/en/contratos/acompanhar-assinaturas.md)
>
> Status, signed PDF and audit.

> [card] [Set up ZapSign](https://docs.notfy.ai/en/contratos/configurar-zapsign.md)
>
> Identity and branding defaults.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.