Prepare a document with AI
In step 3 of the wizard — the editor — the left-hand panel has two tabs: Configure, where you place zones by hand, and Auto AI, where you describe them in words.
It exists for the case that is most tedious by hand: a twenty-page contract where every page takes two people’s initials and the last page takes the signatures.
Write what you want
Section titled “Write what you want”The tab opens with an example, which is also the best description of the format:
For example, type in the box below, in plain language, what you want to do:
add initials and a signature using chave móvel digital for joao silva, joao.silva@assinaja.pt, 911234567
Notice what the example includes: name, email and phone. The editor places zones for people, and a person with no contact details is not a signer — which is why an incomplete request comes back with “the contact is missing (name + email)”.
There is a Dictate button for anyone who would rather speak than type.
It shows you what it will do before doing it
Section titled “It shows you what it will do before doing it”Once the request goes in, Interpreting… appears and then a plan, under the heading I will apply. Actions arrive grouped:
| Group | |
|---|---|
| One entry per person | That person’s signatures and initials |
| Document fields | Text fields, dates, pagination |
| Adjustments to existing | Changes to what is already there |
| Deletions | What is going to be removed |
Every line spells itself out — “Initials for Ana Ribeiro on every page”, “CMD signature for João Silva on page 1” — with the position in plain words: on every page, one on each page, on page 1, on pages 2, 5, 9, in the document.
Confirm, or don’t
Section titled “Confirm, or don’t”The Confirm switch at the top sets the pace:
When on, actions need your confirmation before they are applied. When off, they are applied automatically.
Cancel answers “Cancelled — nothing was applied.” — the plan is discarded whole, not in part.
The result is counted
Section titled “The result is counted”Once applied, the summary says how many actions went through: “{n}/{total} actions applied”. When they do not all go through, it says why instead of leaving you to guess:
| If it failed | What to say in the next request |
|---|---|
| the contact is missing (name + email) | Add a name and an email |
| I could not find matching elements in the document | Describe the place differently |
| field type missing | Say which field — text, date, pagination |
| you did not say what to change | Be specific about the change |
| you did not say what to remove | Be specific about what goes |
None applied gives “No action was applied. You can rephrase the request and carry on with the conversation.”; some applied gives “Some actions were not applied. You can adjust the request and carry on.”
It is a conversation: the next request carries the context of the last one, so correcting beats starting over. Clear wipes the conversation — and warns that “Actions already applied to the document stay”, because clearing the history does not undo what is already on the document.
What is left to you
Section titled “What is left to you”The editor places zones. It does not send — step 4 is still yours, and still shows you the resources the send will consume. See Send a document for signature.
And check what actually landed before moving on: the Configure tab and the document itself show the zones, and it is quicker to fix here than after the document has gone.
When it is unavailable
Section titled “When it is unavailable”On an already-signed document the tab is locked: “Not available — the document is already digitally signed and cannot be changed.”
With no AI provider configured, the platform says so — “The AI feature is not available at the moment. Please contact the platform administrator.” — and it is not a setting you have failed to find.
The remaining cases, including the token balance and the consent asked for on first use, are in AI on the platform.