Skip to content
eSignStack Docs
On this page

Templates and in person

Markdown

Bulk send

Send a template to a list of people. Each person gets their own envelope to sign.

Before you start

The template needs exactly one role for the person on the list. Any other role needs a fixed person, set in the template's Roles step. If the template doesn't fit, the Bulk send dialog says why and links to the editor.

Bulk send emails each person a link to sign, so their role can't use SMS verification.

Send to a list

  1. Open the template and click Bulk send. You can also choose Bulk send from the template's ⋯ menu in Templates.
  2. Give the bulk send a name, such as "Fall camp parents".
  3. Paste the list, one person per line, or click Upload CSV. Each line needs a name and an email address, in any order.
  4. Check the summary under the list, then click Send.

The dialog checks the list as you type. Lines that can't be sent are left out and listed with their line number: a missing or broken email address, or a repeat of an earlier line.

A bulk send holds up to 2,000 people, including any you add later.

Fill sender fields from the list

Start the list with a header row, such as Name, Email, Child's name. A column whose header matches a template field you fill in before sending fills that field on each person's envelope. The dialog shows which field each column fills. Columns that match no field are ignored.

A repeat is a line with the same email and the same values as an earlier one. A parent with two children on two lines gets two envelopes.

If a required field you fill in before sending has no column and no value on the template, the list can't be sent until you add the column.

Follow a bulk send

After you click Send, Envelopes opens, filtered to the bulk send. The banner shows progress while the envelopes go out, and you can leave the page. Each envelope is named after the template and shows the signer's name.

Once sent, the banner shows how many have completed, declined or are still waiting. From it you can:

  • Remind the rest: remind everyone still waiting. The usual reminder limits apply.
  • Add people: paste more people. They're sent their envelopes straight away, under the same allowance rules as a new bulk send. People already on the bulk send, with the same email and values, are left out.
  • Send again: start a new bulk send with the same list.
  • ⋯: download the PDFs of the first 50 completed envelopes (select rows in the list for others), rename the bulk send or open the template. When a bulk send has stopped, Don't send the rest ends it where it is.

Export CSV downloads the bulk send's envelopes, with each sender field as a column and a Signed at kiosk or share link column. When the list is filtered to the bulk send and nothing else, it adds a row marked Not sent for each person not sent to yet.

Pick a bulk send from the filters in Envelopes to see it again. Each envelope's page links back to its bulk send, and the template's page lists its latest bulk sends.

If someone on the list signs the same template at its kiosk or share link after their envelope was emailed, their row says so and Remind the rest skips them. The banner offers to void their emailed envelopes. Nothing is voided until you confirm.

The match is by email address, ignoring case, so it needs the visitor to give the same email. A visitor who gives no email isn't matched. An email shared by several people on the bulk send, such as a parent with two children, isn't matched either, because the signing can't say whose envelope it was.

Allowance

Each envelope counts toward your API, MCP and bulk send allowance, as described in Plans and billing. The dialog shows how many of your remaining sends it uses.

If the list is longer than what's left and your plan has no extras, the first envelopes go now and the rest wait in the bulk send. Click Send the rest in its banner once your allowance resets or after you upgrade. On Platform, agree to the extras in the dialog to send everyone.

Sandbox envelopes never count.

API

There's no separate bulk send endpoint: create an envelope for each person. Envelopes sent by a bulk send have source: "bulk_send" and the bulk send's ID in bulk_send. List them with GET /api/v1/envelopes?filter[bulk_send]=bks_…, or the bulk_send argument of the list_envelopes MCP tool.