Save answer to lets you store a signer's answer in a field on the lead or process running the workflow. For example, a tenant can enter move-in instructions in the agreement, and LeadSimple can save those instructions to a process custom field.
This feature applies to native document templates used in workflow steps. An account admin must configure the answer destinations.
Set up answer saving
Create the destination custom field on the relevant pipeline or process type if it does not already exist, or identify a compatible writable built-in field.
Open the E-signature step's Configure E-Signature dialog and select a ready native template on Document.
Open Field Mapping and locate the agreement question.
In Save answer to, search for and choose the LeadSimple destination. Leaving it empty means Don't save.
If the signer should provide a new answer, leave Prefill from empty. If the question is prefilled and the signer should be able to change it, open the padlock beside Prefill from.
Select Save E-Signature Step.
The Move-in instructions question saves a new answer to a process custom field. No prefill is required.
Example: collect new move-in instructions
Add an editable Text question called Move-in instructions to the agreement. Leave Prefill from empty and choose the process custom field Move-in instructions under Save answer to. After all required signers finish, the answer is saved on that process.
The destination can be blank before sending, and you do not need a prefill mapping to save a new answer.
When answers are saved
Answers are applied after all required signers finish, before the workflow task completes and subsequent workflow steps use the resulting values.
Blank answers and locked fields do not overwrite saved LeadSimple values.
The destination must accept the answer's type and pass the normal field validation rules.
Each document question and each LeadSimple destination can be mapped only once in the step.
Protection for values edited after sending
If a teammate changes the destination while the request is waiting for signatures, LeadSimple preserves the newer value and flags the signer answer for review. Validation failures or conflicts appear in the request's existing error/details display, including on Signatures > Documents. The signature task can still finish; review any flagged answers and update the record deliberately if appropriate.
If a destination is missing
The list offers compatible writable fields on the current lead or process. It does not offer every field in the account. Related contact, property, and unit fields, signatures, attachments, and calculated fields are not supported destinations in this version.
Answer saving is not available for DocuSeal requests or standalone direct sends. Updating the template or mapping later affects future requests; already-issued requests keep the destinations captured when they were sent.