Docs
Signatures

Bulk Send

One template, hundreds of recipients. CSV/XLSX or typed lists, per-recipient data, and the review step.

Bulk send turns a template into many individual envelopes, one per recipient, in a single pass. Each recipient gets their own envelope, their own signing link, and their own audit trail; nothing about it looks or behaves like a mass email.

What you need

  • A template. The document with fields already placed. Bulk send reuses its field layout on every envelope.
  • A recipient list. Typed emails or an uploaded CSV / XLSX file.

The flow

Pick the template

Choose the template this run sends. Its document, field layout, and default options apply to every envelope.

Add recipients

Type or paste the list, or upload a spreadsheet. Rows map to the template's placeholders. A company column fills the company placeholder on each envelope, so every recipient gets a personalized document, not just a personalized email.

Review and send

The review step shows the count, any rows that failed validation (bad emails, missing required columns), and the options that will apply. Send creates one envelope per valid row.

What each recipient experiences

Exactly the normal signing experience. A personal email, their own document with their data pre-filled, the standard consent and signing flow. Recipients never see each other; bulk send produces N independent envelopes, not one shared one.

Managing the run

After sending, the envelopes appear in your signatures list like any others. Filterable, remindable, trackable individually. A bulk run is just many envelopes created at once; reminders, declines, and completions all behave per envelope.

Limits and validation

  • Every envelope created counts toward your plan's monthly signature-send limit. Check headroom on plans before a large run.
  • Rows that fail validation are listed at review. Fix the file and re-upload, or send the valid subset.
  • Template placeholders without a matching column stay empty. The review screen warns about unmapped data before you commit.

On this page