Customize the Signer Invitation Subject and Message for One Request

When you start a new Request from a published Template, QCDS loads the sender’s current Signer Invitation email source into Request Details. You can change the Email subject and Message for this one transaction without overwriting the sender’s saved Email Template.

Where to Make the Request-Specific Change

  1. Choose Use on the published Template.
  2. In Request Details, review the Email subject and Message that QCDS loaded from the sender’s Signer Invitation source.
  3. Edit the subject, the message, or both for this transaction.
  4. Continue to Prepare & Send, finish assignments and routing, run Check, and use Send Now only when the Request is ready.

The current subject field is required and accepts up to 255 characters. The invitation message must also be nonblank before QCDS will send.

The Change Belongs Only to This Request

Editing Request Details does not publish anything back to Email Templates. The sender’s saved Signer Invitation remains the reusable starting point for later Requests. The edited subject/message is frozen into the immutable Request when Send Now succeeds.

This also does not edit the PDF Template. The reusable PDF layout and the transaction-specific invitation message are separate pieces of the workflow.

Tokens Are Resolved When QCDS Delivers the Invitation

You can leave supported QCDS tokens such as {{request.title}}, {{recipient.name}}, or {{request.link}} in the request-specific subject/message. QCDS freezes the message source with the Request, then substitutes the real participant/request values when an invitation is rendered for delivery.

That means you should not replace a token with sample data just to make the editor look complete. Keep the token intact when you want participant-specific information inserted at send/delivery time.

What to Verify

  • The subject describes this specific transaction.
  • The message gives the signer enough context without exposing private internal information.
  • Any token spelling remains intact.
  • The selected Plain Text or Custom HTML mode is appropriate for the message.
  • After Send Now, delivery history shows the invitation was queued/sent for the intended signer address.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDS feature? Visit the QC Digital Signature Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.