ConversaLabs Help Center
en
Language
pt_BR Portuguese (Brazil) en English es Spanish

Contracts & E-signature overview

Open in
View as Markdown Open in ChatGPT Open in Claude
Conversa Labs

Conversa Labs

Last updated on Jun 27, 2026

Overview

The ConversaLabs Contracts & E-signature module lets you create, send, sign and validate contracts without leaving the platform. You build documents from templates with variables, fill in the data automatically from information that already lives in your support workspace (contact, conversation, CRM deal, catalog and account), send the signing link through native channels (WhatsApp and email) and track the status in real time.

The signing process is fully electronic and offers different legal levels — from a simple signature (consent with IP and device record) to a qualified one with an ICP-Brasil A1 digital certificate. Every contract produces an immutable audit trail, a final signed PDF and a public validation page so anyone can check the document's authenticity.

Prerequisites

  • The Contracts module is optional and must be enabled for your account. If you can't find the Contracts area, talk to an administrator.
  • Your user needs permission to access and manage Contracts.
  • To issue contracts you must register at least one issuing company (the "contracted" party). For qualified signatures, that company needs an A1 digital certificate.
  • To send the signing link through channels, have a WhatsApp or email Inbox configured.

Step by step

  1. Open the Contracts area from the sidebar (commercial section, next to Payments).
  2. Register your issuing company and, if you'll use qualified signatures, upload its A1 certificate.
  3. Create a contract template in the editor or upload a ready-made model, using {{ }} variables wherever the content changes from one contract to another.
  4. Generate a contract from the template: variables are filled in automatically with the contact/conversation/deal data; adjust anything missing.
  5. Define the signers and the desired signature level.
  6. Send the link through native channels. The contracted party can sign automatically; the other signers sign on the public page.
  7. Track the status to completion and download the signed PDF. Share the validation page whenever you need to prove authenticity.

Settings & options

  • Issuing companies: register as many as you need, each with its own details, branding and A1 certificate.
  • Templates and clauses: a reusable library of models and clauses.
  • Signature levels: simple, advanced (with OTP) and qualified (A1).
  • Module settings: document retention, time-stamping (TSA) and other adjustments.
  • Automation: contracts can be created/sent via Automations, Macros and the Flow Builder.

Use cases

  • Close a deal in the CRM and send the contract for signature in the same conversation.
  • Issue service agreements, proposals and membership terms with a standardized model.
  • Collect a signature over WhatsApp with OTP for stronger legal assurance.
  • Generate a charge in the Payments module right after the contract is signed.

Tips, limits & best practices

  • Standardize your contracts as templates to gain speed and reduce mistakes.
  • Choose the signature level based on the document's risk — the higher the value, the stronger the recommended signature.
  • For full legal validity of qualified signatures, keep the A1 certificate valid and, where applicable, configure an accredited time-stamp (TSA).
  • Always double-check the auto-filled data before sending for signature.

Troubleshooting

  • I don't see the Contracts module: it may not be enabled for the account or your role — talk to an administrator.
  • I can't issue a qualified contract: make sure the issuing company has a valid, in-date A1 certificate.
  • The signer didn't get the link: confirm the channel (WhatsApp/email) and the signer's contact details.

See also