PrismAMS eSignature is e-signature built into the management system. Most agencies rent a signing tool, then spend the rest of the week downloading signed PDFs and attaching them to the right client. Here the envelope starts from the client record, the signer consents and signs on their phone, and the executed PDF files itself back to that client with the audit trail, legal statement and disclosure already appended. Nothing to download. Nothing to re-attach.
What's included
Upload the document, drop in signature, date, text, checkbox and attachment fields, and name them. Presets for the usual ones (full name, email, phone, title, company, address) mean the signer gets the right keyboard and prompt the first time.
The signing page is built for a phone first. Fields scroll into view, the email and phone keyboards show up when they should, and name and email pre-fill from the envelope.
Every signer reads the Electronic Record and Signature Disclosure and agrees to it before the document opens. Consent time, IP address and browser are stored per signer and printed on the Certificate of Completion. No consent, no signature.
A signer can decline from the disclosure or from the signing page. One decline voids the whole envelope, the sender gets an email with the reason, and the activity lands on the client's timeline.
When the last signer finishes, the executed PDF is filed into Documents on the client record, tagged as a signed eSign document with its SHA-256 hash, and a document-added activity posts to the client feed. The eSign hub links straight to the filed copy.
Every executed PDF carries an appended audit page: each signer, when they consented, when they signed, from what address and browser, and the document hash with instructions for verifying it.
After the certificate, the PDF carries a Legal Statement and Signature Certification (legal effect under E-SIGN and UETA, attribution, integrity, right to decline, retention) and the exact disclosure the signer agreed to, reproduced word for word and versioned. The record shows what the signer saw.
Review & Send requires a document type. The E-SIGN section 103 carve-outs, such as a notice cancelling health or life insurance benefits, court documents, or anything that must be notarized, are listed and can't be sent. The interface blocks them and the server refuses them.
On completion the sender and every signer get an email with a link to the executed PDF. One envelope can carry multiple signers, each with their own consent record.
Edit, merge and split PDFs, insert images, and save the result straight into Documents. Get the document ready and send it for signature without leaving the system.
How it works
Upload the document, place and name the fields, pick the document type, add the signers. The envelope belongs to the client record from step one.
Each signer opens a link, reads and accepts the disclosure, and signs on whatever device is in their hand. Consent and signature are recorded separately, per signer.
The executed PDF gets the Certificate of Completion, the legal statement and the disclosure appended, and the SHA-256 hash of the document is recorded.
The finished document lands in the client's Documents, the activity lands on the timeline, and everyone involved gets a copy. Nobody downloads anything and re-attaches it.
Why it's different
FAQ
PrismAMS eSignature is built for United States transactions under the federal E-SIGN Act and UETA. Each signer consents to electronic records before signing, and the executed PDF carries the Certificate of Completion, the legal statement and the disclosure the signer accepted. It is not an EU eIDAS advanced or qualified signature, and it does not provide notarization.
One PDF: the signed document, then the Certificate of Completion with every signer's consent and signature times, IP address and browser, the document's SHA-256 hash, the legal statement, and the disclosure. It's the same shape of record carriers already accept from the big e-signature vendors.
The SHA-256 hash of the signed document is printed on the certificate and stored with the envelope. Recompute the hash of the file and compare. A file can't contain its own hash, so the certificate spells out exactly which bytes were hashed.
E-SIGN section 103 leaves some document types to other law. The one an agency is most likely to hit is a notice of cancellation or termination of health or life insurance benefits. Those types are listed on Review & Send and can't be sent. A property and casualty cancellation request is fine.
Give us 30 minutes and we'll walk through your real workflows in a tenant set up for your agency. No slides.
