Purser Sign, by GTM Cloud · Close and renew · In design
Status: Purser Sign is a planned feature of Purser, not a separate app, and it isn’t built yet. This is the version 1 design.
E-signature inside Salesforce, on the record where the document was made
Purser Sign is designed to let people sign the document Purser has generated: in person, from a Salesforce login, or in your portal. The signed copy would be saved to the record beside the original.
You know this one
Monday: the order form is generated from the opportunity, and it looks right. Then it leaves Salesforce. It’s downloaded, emailed, printed, signed in pen, scanned on the office copier, and sent back as an attachment to a reply nobody linked to anything.
Friday: the customer says it’s signed. Sales says they’re still waiting. Somewhere there’s a PDF with a signature on it, and it isn’t on the record.
For one order form, a nuisance. For an approval that needs signatures in order, a week.
E-signature inside Salesforce for the documents Purser generates
Purser Sign is designed to add signing to the document you’ve generated. You’d choose Send for signature on the record and name the signers, and each would read, accept and sign. The document is frozen when it’s sent, and the signed copy ends with a certificate page. No outside service is involved.
See it first. Take it back. Keep the receipt.
| Preview | Undo | Prove |
|---|---|---|
| The sender sees where each signature will go, and the signer reads the exact, frozen document. | Void a request any time before the last signature. A completed signature stands; a correction is a new request. | A certificate page, a fingerprint of the document as sent and as signed, and a Verify button. |
What it is designed to do
Sign where the document was made
Send for signature from the document you generated. The signed file is saved beside the original.
A certificate page you can check later
It ends with who signed, when, how, the consent they accepted and the document’s fingerprint. Verify compares that fingerprint with the stored file, so a changed file fails.
How it would work
- Switch it on. Turn on signing and read the consent wording with your counsel.
- Add signature blocks. One in the template for each signer.
- Send. Generate, choose Send for signature, and name the signers.
- Sign. The signed copy lands on the record.
Two readers, two reasons
If you’re the admin
Switch signing on, mark the templates that may be signed, and add a Signature block per signer. No connector, no outside service.
If you’re the one signing off
Many documents need a signature and a record of it, not a signing platform. Order forms and approvals would stay inside Salesforce.
Today, and with Purser Sign
| Today | With Purser Sign |
|---|---|
| Download, email, print, sign, scan, upload | Send for signature from the record |
| A signing service to set up and connect | No connector and no outside service |
| A signed copy in someone’s inbox | The signed copy saved to the record |
| No way to show the file is unchanged | A fingerprint you can verify |
Where it should be strong, and what to know first
Where Purser Sign should be strong
- The document is frozen when sent, so what’s read is what’s signed
- A certificate page and fingerprints, with a Verify action
Good to know before you join the pilot
- It’s a planned feature of Purser. It’s in design, isn’t built yet, and the details may change.
- It’s a simple electronic signature, not an advanced or qualified one, and it puts no certificate-based digital signature inside the PDF.
- Version 1 has no emailed signing link. Signers need a Salesforce or portal login, or sign in person on a signed-in user’s device.
- It signs documents Purser generated, not uploaded files.
- Whether an electronic signature is enough depends on the document and the place. Ask your legal adviser, and use your signing provider where you need more.
Questions people ask
Is this legally binding?
That depends on the document, the parties and the law that applies, and we can’t advise on it. Purser Sign is designed to record who signed, when, how, and the consent accepted, and to let you verify the file hasn’t changed. For more, Purser’s hand-off to a signing provider is unchanged.
Can someone outside our org sign?
In version 1, as designed: in person on your user’s device, or through your Experience Cloud site if they have a login there. An emailed signing link is planned for a later version, but it isn’t part of version 1.
What if the record changes after we send?
Nothing changes in the document. It’s frozen at the moment it’s sent, and the signed copy is made from that frozen content, so what the signer read is what was signed, even if the record has moved on.
Do we need to stop using our signing provider?
No. Signing would be off until you switch it on, and each template says whether it may be signed this way. Your existing hand-off to a signing provider is unchanged, so you can keep using it for documents that need more.
How do I get a document signed inside Salesforce without a separate signing service?
That’s what Purser Sign is designed for: generate the document with Purser, choose Send for signature, and name the signers. They’d sign with a Salesforce or portal login, or in person on a signed-in user’s device. It isn’t built yet, so the pilot is where to start.
Works well with
- Purser: Purser Sign would be part of it. Generate the document first, with a preview.
Purser Sign sits in the Close and renew stage. Planning how documents flow in your org? Our Salesforce services can help. Pair it with Sistership to clone a renewal with the right fields reset.
Built on the platform
- Native to Salesforce. Requests, signatures and files would live in your org.
- Off until you switch it on, and each template says whether it may be signed.
Bring the document that takes a week to come back
Purser Sign is in design. Join the pilot and tell us which documents you would sign this way.