Bulk send for HR and sales envelopes

HR and sales both live on repeated paper: the same offer letter, the same handbook acknowledgment, the same order form, the same NDA. Placing fields fifty times is how those envelopes stall. Bulk send is the desk path that takes one workspace template and a list of names and emails and starts a separate envelope for each unique address.

This is not a mail merge that stamps fifty names onto one shared file. Each row becomes its own envelope, with its own signing link, audit trail, and status. Retries skip rows that already went out. The job stays inside the current organization. The in-app notes are at Docs; the feature write-up is bulk send on Features.

When bulk send is the right tool

Use it when the PDF and the field layout are the same and only the recipient changes. That is most HR envelopes and a large share of sales envelopes.

HR envelopes

• Offer letters that already have signature, date, and a text mark for the accepted title or start date.
• Handbook or policy acknowledgments you send to a new cohort.
• Equipment or confidentiality acknowledgments on a fixed form.

Sales envelopes

• A standard order form or statement of work cover that does not change per account.
• An NDA you send to every prospect who reached the same stage.
• A vendor envelope you issue to a list of new suppliers.

Do not use bulk send when each recipient needs a different PDF, a different field layout, or several people on the same envelope. Multi-signer routing — sequential order or parallel — lives on a single envelope, not on a list job. See More on signing order. One decline closes that row’s envelope; it does not route to a backup and it does not continue the rest of a sequential chain. If the file itself changes per person, send one-off envelopes — or maintain more than one template and run more than one job.

Start from a template

Bulk send requires a workspace template. The template is the PDF plus the signature, date, text, initials, checkbox, and select marks you placed once. Members of another organization cannot see or use it. Save the layout before you open the list. Templates that reuse field layouts and More on templates walk those three clicks.

If you only need one recipient, do not open Bulk send. Upload a PDF or start from the template and send a single link. The five-minute send is that path.

How the job runs

1. Open Bulk send on the desk.
2. Choose the workspace template.
3. Paste names and emails, or upload a CSV.
4. Map the columns so Inkpacket knows which field is name and which is email.
5. Preview the count. Confirm you are about to create that many envelopes.
6. Set reminder interval, expiration, and an optional access code — or keep the workspace defaults.
7. Start the job.

Each unique email gets its own envelope with the same field layout. Duplicate emails in the list are sent once. Retrying a job skips rows that already sent, so the same person does not get a second link from that job. Shared reminder and expiration settings apply to every row. The same optional access code, if you set one, covers every recipient in that job — see access codes for sensitive envelopes.

Reminders, expiry, and the monthly envelope count

The job uses the reminder interval and expiration you set, or the workspace defaults (every 3 days, 14 days until the link dies). Set the interval to 0 to skip reminders on those envelopes. After expiry the signer cannot complete that envelope. Reminders and expiry explains the hourly job.

Each row counts as an envelope against the workspace plan. Free allows 5 packets a month; Starter is 20 (more than Free, plus extra published Web Forms), Growth 100, Agency 500. A row that would exceed the remaining count returns HTTP 402 and ENVELOPE_LIMIT, the same as a single send. Seat counts on Pricing are planning numbers — invite does not refuse. Billing is published, not charging — workspaces stay on Free until checkout is live — but the send path still checks the monthly count. Choosing a plan and published pricing list the lanes.

After the job starts

You now have many envelopes, not one mega-envelope. Each has its own status, signing link, and audit log. You can void, correct, or resend a single row the same way you would a one-off send. A decline on one envelope does not void the rest of the job. Envelope admin is the in-place toolkit.

If mail is not configured, Inkpacket logs each invite the same way as a single send. Copy signing URLs from the desk when you need to deliver them yourself. Embedded URLs exist per envelope if you will iframe a specific signer — embedded signing is a per-token feature, not a bulk iframe of the whole list.

What this pass will not do

• It will not merge fifty names onto one shared PDF.
• It will not place different fields per row. Change the template, or send one-off.
• It will not route to a second signer after a decline.
• It will not invent a template. Save the layout first.
• It will not leak the job into another organization.

Operators who already have a template should keep More on bulk send open while they map columns. This article is the public, indexable version of that section: HR and sales examples, the monthly packet limit, and links out to templates, access codes, reminders, and signup if you still need a workspace. Send the list once. File each completed PDF on its own envelope.