Skip to content

Tracking and managing a request

Everything on this page happens on the Sliick Signatures card on the record you sent from. Each request on the card has a menu of actions, and the actions offered depend on its status.

StatusMeaning
DraftNot sent yet.
Sent or In ProgressWaiting for signatures.
CompletedEveryone has signed.
DeclinedA signer declined to sign.
CancelledThe sender voided the request.
ExpiredThe signing window ran out.

The Sliick Signatures card with the action menu open on a completed request

ActionWhat it does
Resend reminderReminds signers who have not signed yet, on top of any automatic reminders. To avoid flooding signers, it is unavailable for an hour after a reminder.
Void requestCancels the request. Signers are told, and their signing links stop working. You can add an optional reason.
Duplicate & resendFor an expired, cancelled, completed or declined request. Creates a new draft with the same documents, fields, signers, order and message, and a fresh signing window. It has none of the original’s signatures or history, and the original is not changed. If anyone had already signed, you are warned that they will need to sign again.
Change documentOn a draft only. Regenerate the document from the record’s current data (for a document made from a template, handy when the numbers have changed), pick an earlier generated document, or attach a different file. If you have placed fields, it asks first, because they are cleared: they were positioned for the old document and could land on the wrong clause.
Reset signer verificationShown when a signer can no longer get a verification code, because they entered too many wrong codes or asked for too many. The card shows a note such as 1 signer can’t verify. Resetting lets them request a new code and sign. It only happens when you choose it: resending the request does not reset it.

If an invitation or a verification code could not be emailed, the card shows Stalled - something was not delivered. It says which signer is affected and what to do next. This shows on the record, not in an email, because email is what failed. So check the card when a signer says something never arrived.

Nothing else changes. The request stays open and signable, and automatic reminders carry on. The next reminder is usually the fix: the signer already has a working link, and the reminder brings them straight back.

A code that could not be sent does not count against the signer. They can simply ask for another once email is working.

If a signer’s browser cannot open one of the documents, the card shows A signer can’t open a document, with which document and what to do. The request stays valid: it can still be signed, reminded or cancelled.

When a request is complete, both you and the signers can download everything. On the card, you can choose:

  • Open request: the full request record, with its history.
  • Download combined PDF: all the signed documents in one PDF.
  • Download all (.zip): one file containing every signed document and the Certificate of Completion.

If a request completed without signed documents being put together, the card offers Download certificate instead, for the Certificate of Completion on its own.

The signed files you download are identical to the stored signed originals. Resend signed copies emails the signed copy and certificate to everyone again.

Signed copies are saved on the record (new in 3.4). When everyone has signed, Sliick Docs saves each signed document and the Certificate of Completion to the record the request was sent from, such as the Opportunity or Quote. Find them under Files on that record.

  • The files are view-only, so nobody can upload a different version over the signed copy.
  • Anyone who can see the record can open them, including Experience Cloud users who can see it. The certificate shows each signer’s email address and where they signed from, so check who can see the record before you send.
  • With a sealed signature mode, the file on the record is the sealed copy. It is added once sealing finishes.
  • Requests completed before 3.4 are not changed. Resend signed copies adds their files to the record, and also emails everyone again.

A signer must have verified who they are before they can download their copy, whether that is the signed document, the full package or the certificate. Having the link is not enough. If you reset a signer’s verification after the request is complete, they are asked to verify again next time, and can then download.

The Certificate of Completion records the sender, every signer, when each signed, where each signed from, the consent wording each accepted and its version, and the full history of the request. See Verification and certificates.

Every signed page carries a short reference code, in the header and the margin. The same code is on the certificate and in the emails, so any page of any copy can be matched to its request. It is a reference, not a password, so it is safe to read out to support.