Allow ECF & default fields in Email Message Body (Next Sender / Email Notifications)

Problem / Limitation

Currently, Docusign allows the use of ECF (Envelope Custom Field) placeholders in the Email Subject line using syntax such as:

[[ECF:Client_Name]] 

However, ECF fields and standard merge fields (text, number,...) are not supported in the Email Message Body, including:

• Next Sender recipient emails

• Routing Order notifications

• Automated system emails tied to envelope progress

This creates an unnecessary inconsistency: dynamic data can be shown in the subject, but not in the email body where context matters most.

Why this matters

Customers frequently need to include dynamic, envelope-specific information in the email body, such as:

• Client or account name

• Contract reference number

• Opportunity ID

• Agreement type or region

• Internal tracking codes

Without merge support in the email body, customers must:

• Use vague, generic messages, or

• Build complex workarounds (Workflow Builder (formerly Maestro) workflows, external email systems, or manual intervention)

This reduces usability and adoption—especially in IAM workflows where automation and clarity are critical.