Closing a deal usually means several documents at once: the agreement to sign, a certification or acknowledgment, and the proposal and NDA that were already signed earlier. A signing packet puts all of them behind one link. The client reads them in order and signs once, and that signature applies to every document in the packet that needs one.
Two kinds of item
A packet is made of two kinds of item, and the difference matters:
- To sign — built fresh from one of your document templates when the packet is assembled. These are what the signature applies to.
- Reference — a document already executed on this deal (the accepted proposal, the signed NDA). It is carried along read-only, showing the signatures it actually holds, and it can never be re-signed or altered by the packet.
Set up a packet template
- Open Settings → Templates → Packets and create a packet.
- Add each item in the order the client should read it. For a to-sign item, choose the document template it is built from. For a reference item, choose the document type and the status that counts as executed — a Proposal is accepted, an agreement is signed.
- Mark an item required if the packet should refuse to go out without it.
- Optionally choose who counter-signs after the client, using the "After the client signs…" control at the top.
Match the required status to reality
A reference item asks for a document type in a particular state. A Proposal reaches accepted and never signed, so a Proposal item set to "signed" can never resolve. If a packet refuses to send, the message names the item, says what it found instead, and tells you which status to change.
Send one from a deal
- Open the deal, go to the Documents tab, and choose Send packet.
- Pick the packet, the recipient (any contact on the deal), and an optional deadline for the link.
- Review the preview: what will be signed, what is carried for reference, anything skipped, and who signs in what order.
- Send. Only the first signer is emailed — the next person is invited automatically when their turn comes.
You are told what is already in play
Before sending, PULSE checks whether this deal already has a packet out for signature, one already executed, or an automation rule that would send the same packet later. Anything it finds is shown with the option to continue anyway — sending a second link for the same agreement is sometimes right, but it should never be an accident.
Merge fields are filled in when the packet is assembled
To-sign documents are built from your templates with their merge fields resolved from the deal, company, and contact, and each document keeps a record of what was merged. If a field has no value to fill, the packet refuses to send and names the field rather than showing a client raw {{tokens}}.
What the client sees
One page, every document in order, with each reference copy marked as already executed and showing its real signatures. They sign once at the bottom — drawn or typed — confirm the name to print on the documents, and optionally add their job title. Nothing is asked of them twice, and there is no account to create.
Counter-signing, and when the certificate appears
If your packet names a counter-signer, they receive their own link the moment the client finishes — never the client's link. The packet stays "partially signed" until they sign, and no Certificate of Completion is issued before then: certifying an agreement your own side has not signed would be a false record. Once everyone has signed, PULSE emails all parties a link to the completed certificate, which lists every document, every signer, and a fingerprint of the executed set.
While it is out
Open Packets in the sidebar, or the Signing packets block on the deal, to see what is in flight and who it is waiting on — including when the ball is with your own side. From a packet you can send a reminder, withdraw it, or re-issue it if it expired or was declined. A packet that is fully executed cannot be withdrawn: the certificates have already been sent, and the record has to keep saying what happened.
Sending one automatically
A packet can also be sent by an automation rule — for example when a proposal is accepted. The rule will not send a second copy of a packet that is already out for signature on that deal, and you can add the condition "Signing packet already out is false" if you want a rule to hold off while anything at all is pending.