Print, sign, scan, email
The classic loop: send a PDF, hope it comes back signed, then someone files the scan by hand — if it lands in Salesforce at all.
Salesforce consent & agreement forms
Salesforce consent forms that are personalized, signed, and filed automatically.
Write a consent or agreement once with a rich-text merge document, drop in Salesforce fields like {{Prefill_Contact.LastName}}, and every signer reads a version personalized to them. They verify by email, sign on screen, and a signed PDF is attached to the Salesforce record you choose. A simple DocuSign alternative for basic agreements and consent — native to Salesforce.
- Native to Salesforce
- Personalized from Salesforce data
- Signature + signed PDF
- Verified signer, no login
Consent & Agreement
Dear Cohen,
I, Dana Cohen, confirm that I have read and agree to the terms of the Volunteer program described above, and consent to the processing of my data as set out in the policy.
Merged live from Salesforce — one document, personalized per signer.
Signature — signed 2 Jun 2026
The problem
Getting a signature is easy. Getting it onto the record isn't.
Consent forms, waivers, and simple agreements are everywhere — but the signed copy rarely ends up clean, personalized, and attached to the right Salesforce record.
DocuSign is overkill (and priced for it)
For a one-page consent or waiver, per-envelope e-sign pricing and a separate platform are a lot — and it still needs syncing back to Salesforce.
Nothing is personalized
A generic PDF can't say "Dear Dana, regarding your Volunteer agreement dated…" without someone editing each copy by hand.
No proof of who agreed
An emailed signature with no identity check is weak evidence. You can't easily show the right person agreed to this exact text.
The solution
A merge document, a signature, and a signed PDF on the record.
TwinaForms is a native Salesforce app. Build the consent document once with merge tokens, share a public link, and each signer reads a personalized agreement, verifies, signs, and submits — the signed PDF lands on the Salesforce object you choose.
Rich-text merge document
Write the agreement in a rich-text editor and insert Salesforce fields with tokens like {{Prefill_Contact.LastName}} — headings, paragraphs, and terms, personalized per signer.
On-screen signature
The signer draws their signature directly below the document on any device — no app, no account, no printing.
Verified identity
With User Verification, the signer confirms a one-time email code matched to their Salesforce Contact before the document opens.
Signed PDF on the object you choose
On submit, the merged text and signature are rendered to a PDF and attached to the standard or custom Salesforce object you configure.
How it works
From agreement text to a signed record in four steps.
Write the document with merge tokens
In the Designer, type the consent or agreement text in the rich-text merge editor and insert Salesforce field tokens where you want personalized values.
It personalizes per signer
Prefill loads the signer's Salesforce data, and the tokens become their real values — one document, a personalized version for everyone.
They verify & sign
The signer confirms a one-time email code, reads the document, and signs on screen — on a phone, tablet, or desktop.
Signed PDF attached to Salesforce
On submit, the signed PDF — merged text plus signature — is attached to the Salesforce object you chose, with the signer's details recorded.
A simple, honest alternative
Where this fits next to DocuSign and print-and-scan.
TwinaForms covers the common case — a personalized, single-signer consent or agreement that needs to live in Salesforce. It is intentionally simple; it does not replace a full e-signature platform for complex signing.
| TwinaForms (native) | DocuSign & similar | Print / scan / email | |
|---|---|---|---|
| Best for | Simple, single-signer consent & agreements | Complex, multi-party, regulated signing | Ad-hoc one-offs |
| Personalized from Salesforce | Yes — merge tokens in the document | Via templates / connectors | Manual editing |
| Lands on the Salesforce record | Signed PDF on any object, automatically | Via integration / sync | Manual filing |
| Signer needs an account / login | No — email verification only | Usually an account / envelope | No |
| Cost model | Included in your plan, no per-envelope fee | Per-envelope / per-seat | Staff time |
| Multi-party routing & certified audit | Not in scope | Yes | No |
Where teams use it
Built for everyday "read and agree" documents.
Consent & data privacy
GDPR/marketing consent, photo & media release, research or treatment consent — personalized and filed on the Contact.
Waivers & releases
Liability waivers and activity releases signed on a phone, with the signed PDF attached to the relevant record.
Membership & volunteer agreements
Membership terms, volunteer agreements, codes of conduct, and policy acknowledgments — signed and stored against the person.
Good to know
A practical record — check your legal requirements.
TwinaForms preserves the exact document the person agreed to, their drawn signature, and (with User Verification) a verified email and timestamp, in a signed PDF on the Salesforce record. Whether that satisfies the rules for a legally binding electronic signature depends on your jurisdiction and the type of agreement, so please consult your legal team about requirements such as ESIGN, UETA, or eIDAS for your use case.
FAQ
Common questions about Salesforce consent forms.
What is a Salesforce consent form with e-signature?
It is a public TwinaForms form that shows a consent or agreement document personalized with Salesforce data, lets the person sign it on screen, and attaches a signed PDF back to a Salesforce record. The document is built with a rich-text merge editor, so you write the text once and drop in Salesforce fields like {{Prefill_Contact.LastName}} that fill in per recipient.
How does the merge document personalize the agreement?
In the Designer you write the consent text in a rich-text editor and insert merge tokens that reference Salesforce fields, for example "Dear {{Prefill_Contact.LastName}}". When a specific person opens their link, prefill loads their Salesforce data and the tokens are replaced with their real values, so each signer reads an agreement personalized to them.
What happens on the Salesforce record when someone signs?
On submit, TwinaForms generates a signed PDF that contains the merged document text and the drawn signature, and attaches it to the Salesforce object you choose (standard or custom). The submission also records the signer's details, and when User Verification is on, the verified email and the time of signing are captured too — so you have a practical record of who agreed to what and when.
Is this a DocuSign alternative?
For simple, single-signer agreements and consent it can replace DocuSign: a personalized document, an on-screen signature, and a signed PDF on the Salesforce record, with no per-envelope fee and no separate platform. It is intentionally basic compared to DocuSign and does not do multi-party signing routing or a certified enterprise audit trail. For complex or highly regulated signing workflows, a dedicated e-signature platform is still the right tool.
Is the e-signature legally binding?
TwinaForms captures a drawn signature, the merged document the person agreed to, and (with User Verification) a verified email and timestamp, all preserved in a signed PDF on the Salesforce record. Whether that meets the legal requirements for a binding electronic signature depends on your jurisdiction and use case, so consult your legal team about requirements such as ESIGN, UETA, or eIDAS for your specific agreements.
Can I confirm who actually signed?
Yes. Turn on User Verification so the signer must enter a one-time code sent to the email on their Salesforce Contact before the document opens. The signature is then tied to a verified identity, with no Salesforce login or per-user license for the signer.
Which Salesforce object does the signed PDF attach to?
Any standard or custom object you choose in the form's submit configuration. The signed PDF is attached as a Salesforce File on that record, so a consent can live on the Contact, a waiver on a custom Agreement object, a release on a Case, and so on.
Ready to get it signed
Turn your next consent or agreement into a signed Salesforce record.
The merge document, signature, and signed-PDF writeback are TwinaForms Pro features; User Verification is included from Starter. Install into a sandbox and send a personalized, signed consent in an afternoon. Nonprofit discount available.