BlogTag
Bulk send
Send one workspace template to a list of names and emails. Each unique address gets its own envelope.
Related product pages
Guides
Bulk send for HR and sales envelopes
Send one Inkpacket template to a list of names and emails: CSV or paste, column mapping, one envelope per unique address, shared reminders, expiry, and optional access code.
Bulk send vs Web Forms: which tool starts the envelope
Choose between an Inkpacket bulk job and a published Web Form: you already have the emails, or strangers start themselves. Both count toward the monthly envelope cap — Free allows 5 packets a month.
Bulk send CSV column mapping
How Inkpacket maps a CSV or paste of names and emails on Bulk send: guessed columns, unique addresses, skipped rows, a 100-row job, and why preview exists before you spend the monthly envelope cap.
Bulk send Free envelope math
Each unique Inkpacket bulk-send row is one envelope toward Free’s 5. Preview the count. A row that would exceed it returns HTTP 402 ENVELOPE_LIMIT. Starter is 20 — more than Free. That is list-math honesty.
Bulk send: job created but send unfinished
If an Inkpacket bulk start fails after create, the desk says Job created, but sending did not finish. Open that job and retry. That is unfinished-job honesty — not a second CSV and not ENVELOPE_LIMIT by itself.
Why a bulk send job stops at 100 unique emails
An Inkpacket bulk send job accepts 100 unique emails. A 101st address is not a plan unlock and not HTTP 402. That is job-cap honesty — not checkout, not a second template.
Why a duplicate bulk email is one envelope
Inkpacket sends a bulk-send row once per unique email. A repeated address is not a second envelope. That is duplicate-email honesty — not HTTP 402, not checkout.