Print supports three types of signature handling.
Static signature image
A pre-captured signature image embedded in the document. Use when you always sign the same way and want the document pre-signed.
To add one:
In the template editor, click Insert → Image
Upload your signature image (PNG with transparent background recommended)
Position and resize it
The signature appears on every generated document.
Signature block placeholder
A formatted block containing fields for signature, printed name, title, and date — left blank for manual signing after printing or for e-signature workflows.
To add one:
Click Insert → Signature Block
Choose the fields to include (signature line, name, title, date, all or any)
Style the block to match your document
E-signature integration (via automation)
ThatApp does not have a built-in e-signature tool, but you can combine Print with an e-signature platform (DocuSign, HelloSign, PandaDoc) via an automation:
Generate the document using Print
Pass the generated PDF to the e-signature platform via an automation action
The recipient signs in the e-signature platform
The signed document returns via webhook and is stored in FileHaven
Ask AVA to build this automation: "When I generate a Print document, automatically send it to DocuSign for the client's signature."
Related: How Print Works · How to Build an Automation With AVA