When I connected with support they confirmed through ticket #4102832 that the esign functionality was indeed compliant with regulations like the U.S. ESIGN Act, UETA, and the EU’s eIDAS. Maybe I didn't ask the right questions?

Sure glad to see this is under review. Standing by.

I connected with HighLevel on this when I heard of this feature and they confirmed that the digital certificates and audit trails issued are compliant with the U.S. ESIGN Act, UETA, and the EU’s eIDAS.

I haven't implemented it yet, but can I assume then that what I was advised was not entirely true?

The consent captured when a user clicks sign is missing literally EVERYTHING the E-Sign Act requires! Where's the disclosure about your right to get paper copies? Your right to withdraw consent? How to request paper documents? Hardware/software requirements? The scope of what you're consenting to?

Section 101(c)(1)(B) of the E-Sign Act specifically requires ALL of these disclosures BEFORE getting consent, meaning before the document is even SHOWN. This tiny disclaimer about "signature equals handwritten" doesn't even come close to meeting federal requirements.

I'm losing clients over this in the mortgage space. So frustrating that high level won't take this seriously!

Brady Bell there is a Under review where this comment should be. I am not sure they are amalgamating all of the context relevant comments.

See https://ideas.gohighlevel.com/documents-contracts/p/e-signature-docs-i-assume-hellosign-api When GHL starts putting things under review they need to account for all of the necessary requirements.

I hope this helps GHL meet the esignature requirements.

The document signing needs proof of who signed:

Capture Device Name, Device ID, Device IP Address etc. The information which normally appears on e-signature documents to enforce and prove point of origin of the signer. Especially when one chooses to use Simple text vs a manual signature. Adopting sign by Text and not a signature is not a viable nor enforceable option with the all of the collateral Proof of where, when, how and by who (Device identity). Great effort to include e-signature.

The Form fill area should flip to landscape on my mobile device when filling the signature in. (Maybe a Fill on Mobile QR code... then esig uploaded.)

Great effort on adding esigning capability. Thank you.

How we can improve the feature and make it more enforceable.

This function needs to show the Computer IP Address when and where signed. User information if we accept the Type as signature verses a hand Written signature. ensure that the Digital Signature ties back to a computer device where signature was enacted/executed like e-signing platforms include. IP Addres, Date, Time, GUID, etc Devices name, UserID, Email etc.

to make the signature as valid and binding as possible.

The document signing needs proof of who signed:

Capture Device Name, Device ID, Device IP Address etc. The information which normally appears on e-signature documents to enforce and prove point of origin of the signer. Especially when one chooses to use Simple text vs a manual signature. Adopting sign by Text and not a signature is not a viable nor enforceable option with the all of the collateral Proof of where, when, how and by who (Device identity). Great effort to include e-signature.

The Form fill area should flip to landscape on my mobile device when filling the signature in. (Maybe a Fill on Mobile QR code... then esignature uploaded.)

This thread is related and should be reviewed an considered:

I use make.com -> pandadoc for this currently. would love to see it happen internally

YES this needs to be done ASAP, this is one of th main reasons for using HIGHLEVEL, its an all in one platform, If i Cant sign Contracts its meaningless. Im so frustrated I built the form added the ability for a customer to sign, but now I can not download this application with the signature. Ideally I would be able to download all data collected from the customer with the signature in a pdf document.