Choose Plain Text or Custom HTML for a Request Invitation

Request Details lets you choose Plain Text or Custom HTML for the signer invitation of the current Request. The choice is frozen with that Request and does not change the sender’s reusable Signer Invitation Email Template.

Choose the Message Mode in Request Details

QCDS opens the invitation in the mode supplied by the sender’s saved Signer Invitation source. Use the Plain Text or Custom HTML buttons to switch the current Request to the format you want.

  • Plain Text: the invitation is delivered as a real text/plain message for this Request.
  • Custom HTML: QCDS uses the rendered HTML editor and sends the sanitized HTML version.

Switching modes is a Request-level change. It does not enable/disable Custom HTML on the saved Email Template.

Keep the Plain-Text Body Complete

The streamlined send path requires the plain-text invitation body to be nonblank even when Custom HTML is selected. Treat it as the readable text version/fallback of the invitation instead of leaving it empty.

For Custom HTML, the rendered HTML must also contain visible message content. An empty Custom HTML document cannot be sent.

How QCDS Sanitizes Custom HTML

The browser editor removes active content such as scripts, embedded frames/objects, event-handler attributes, and JavaScript URLs before editing. Send Now sends the HTML through the server-side sanitizer again before it is frozen into the Request.

Use ordinary email-safe structure and styling. Do not depend on scripts or other active browser behavior in an email message.

Token Substitution Happens at Delivery

Supported QCDS tokens remain as token text while you prepare the Request. At delivery time QCDS substitutes values such as the recipient, request title/number, secure signing link, expiration, sender identity, and site name. Token values inserted into HTML are escaped for HTML output.

Before You Send

  • Confirm the Email subject and plain-text body are not blank.
  • If using Custom HTML, confirm the rendered editor still contains the intended content after sanitization.
  • Do not remove or mistype tokens you expect QCDS to replace.
  • Run Check for the Request fields, then use Send Now and verify the invitation delivery state.

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.