Feature gap in the new Send in Bulk environment

Gaps in the new Send in Bulk functionality

The new Send in Bulk experience is near parity with the classic experience feature set, but not completely.

Currently missing from the new experience is the option to add the sender as the first signer in two use cases:

  • When the new experience is used and recipients are added manually, the option to assign the sender as the first signer isn't available.
  • When creating a new Send in Bulk transaction in the new experience, if you want the sender to sign first, you must explicitly add them as the first recipient to each row. 
    • There is no button to automatically add the sender as the first recipient as there is in the classic experience.
Note:

Creating Send in Bulk transactions via API is also impacted by the "sender signs first" limitations.

API calls configured to order the sender as the first signer are not supported.

Customers should update their CSV to use the new experience format that includes the sender as the first recipient for each child agreement in the file.

Get help faster and easier

New user?