Conversa Labs

Last updated on Oct 21, 2026

Overview

The Contracts area gathers every document in your account into a list you can filter and where you follow each contract's lifecycle in real time. Each contract moves through well-defined states:

  • Draft β€” the contract was generated from a template and can still be edited.
  • Sent / in signature β€” the signing link was delivered and the document is awaiting the parties.
  • Partially signed β€” at least one signer has signed; others are still pending.
  • Completed β€” all signatures were collected and the final signed PDF was generated.
  • Voided β€” the contract was irreversibly cancelled after being sent.
  • Expired β€” the signing deadline passed without completion.
  • Rejected / cancelled β€” a signer declined or the contract was closed with no effect.

From the list and the contract screen you run every management action (send, remind, void, duplicate, download, share links) and inspect the immutable audit trail.

Prerequisites

  • The Contracts module must be enabled for your account. If you can't find the Contracts area, contact an administrator.
  • Your user needs permission to access and manage Contracts. Voiding a contract is restricted to administrators.
  • The contract must already have been generated from a template (with signers defined) before it can be sent for signature.

Step by step

  1. Send for signature β€” on a draft contract, use Send for signature. The platform freezes the document, generates the PDF for signature (without the "Draft" watermark, with a file name derived from the contract title), automatically signs the issuing company's side, and delivers the link to external signers as a card with a button in the linked conversation. At least one external signer (the other party) is required: with only the issuing company, the button is disabled and the screen explains why.
  2. Resend a reminder β€” use Remind to re-post the signing card and button in the conversation and nudge the pending external signers. If there is no linked conversation, the action has no effect.
  3. Void / cancel β€” use Void to irreversibly cancel a contract that was already sent. The status changes to voided and the document can no longer be signed. This action is restricted to administrators.
  4. Duplicate β€” use Duplicate to clone the contract into a fresh draft. Signers and items are copied, a new verification code is generated and no signatures are carried over.
  5. Download the signed PDF β€” use Download to get the signed URL of the most recent final document (falling back to the PDF sent for signature if there is no final yet). The download includes the SHA-256 hash so you can verify integrity.
  6. Copy / share the signing links β€” use Signing links to get each external signer's public URL, in case you need to resend the link manually through another channel. Parties that sign automatically have no public link, and the signing token is never exposed in the list.

Tracking and audit

  • Audit trail (events): every contract has a read-only forensic timeline with the signature lifecycle events β€” created, sent, viewed, OTP sent, OTP verified, signed, rejected, expired, downloaded and voided. Each event records the IP, device, consent, authentication method and the document hash at the moment of the event. The trail is immutable (append-only): no record can be changed after it is created.
  • Filter the list: you can filter contracts by status, signature level and, most usefully, by the support links β€” conversation, contact and CRM deal β€” plus the issuing company. This lets you quickly find every contract for a given customer or a specific deal.

Archive and restore contracts

  • Archive removes the contract from the default list without deleting it β€” handy for tidying up old or closed documents.
  • Restore returns an archived contract to the active list.
  • A contract with a real signature (partially signed or completed) is a legal record and is never deleted β€” only archived. Permanent deletion is allowed only for a draft that is already archived.

Integrations with Tasks and Follow-up

From the contract itself you can trigger other modules of the platform (when enabled):

  • Create a follow-up Task β€” generates a Task already linked to the contract's conversation, contact and CRM deal. Requires the Tasks module enabled.
  • Enroll in a Follow-up sequence β€” enrolls the contract's contact into a follow-up sequence (idempotently, with no duplicates). Requires the Follow-up module enabled and a contact linked to the contract.

Review and edit a draft before sending

  1. Open the contract title or Review document. The Contract document section shows the complete merged body, including long clauses; View draft PDF uses the native document layout and a draft watermark. No signature or final document is created by previewing.
  2. If the body is empty or a merge field has no value, use Edit draft to fill in the agreement and variables. Cancel discards only the unsaved form. Save draft updates this draft, then refreshes the preview; it does not change the source template.
  3. Send for signature opens a review of the document and its parties. Confirm the review before sending. Closing the review sends nothing. The original signer routing, authentication and signature level still apply.
  4. In a conversation, the Contracts panel keeps its contact and conversation context. Each card exposes Review document, Send for signature for drafts, and More actions for editing, reminders, download, archive or void when status and permission allow. Opening the complete area preserves the contextual filter in the URL.

For a sent or signed contract, Open original PDF opens the stored file instead of regenerating the document. A draft preview and its verification link do not certify a completed signature or ICP-Brasil validity. If the browser cannot display PDFs inline, use the visible link to open the PDF in a new tab. A preview error is shown explicitly; it is not replaced by a one-page notice presented as the complete agreement.

Links and follow-up enrollment

Tasks created from a contract inherit its linked conversation, contact and deal. Contracts generated by automation or Flow preserve the conversation that triggered the action. Review these links before sending for signature.

Follow-up enrollment and its contract link are saved together. If the link cannot be saved, the new enrollment is rolled back and does not start follow-up. Repeating the same sequence reuses the linked enrollment, including when it has already ended. A contract keeps one linked sequence: selecting another is declined with guidance to select the existing sequence or manage the enrollment in Follow-up. The existing enrollment and link are preserved.

Settings & options

  • Use owner, status, and deadline filters to follow only contracts that require team action.

Use cases

  • Close a deal in the CRM, send the contract in the same conversation and create a task to follow up on the signature.
  • Resend the reminder to a customer who opened but hasn't signed the document yet.
  • Void a contract sent by mistake and duplicate it to fix the details in a new draft.
  • Download the signed PDF and archive the completed contract to keep the list clean.

Tips, limits & best practices

  • Use the audit trail to know exactly who viewed and who signed before chasing a pending signature.
  • Voiding is irreversible β€” confirm before using it. To merely fix details, prefer to duplicate and send the new version.
  • Always check the SHA-256 hash when downloading the final document if you need to prove integrity.
  • Keep the list tidy by archiving completed and old contracts.

Troubleshooting

  • The Send for signature button is disabled: the contract only has the issuing company as a signer. Add the other party under Parties & signers and send again.
  • The status is stuck on "partially signed": someone is still missing. Check the audit trail to see who has signed and use Remind or Signing links to chase the pending parties.
  • The signer didn't receive / didn't sign the link: confirm the channel (WhatsApp/email) and the signer's contact details; resend with the Remind button or copy the signer's signing URL and send it through another channel.
  • The contract expired: the signing deadline passed. Duplicate the contract to create a fresh draft and resend.
  • I can't void the contract: voiding is restricted to administrators and applies only to contracts that were already sent.
  • I can't delete the contract: contracts with a real signature are never deleted β€” archive it; permanent deletion is allowed only for a draft that is already archived.

If a legacy draft contains invalid saved fields, the editor explains the problem and asks you to restore the fields from the document. The text stays intact. Review and enter the field values before saving; canceling preserves the original draft.

See also