Why a bulk send job stops at 100 unique emails

Use Bulk send when the same PDF and field layout go to many people. Pick a workspace template, paste or upload a CSV of names and emails, map the columns, preview the count, and start the job. Inkpacket creates a separate envelope for each unique email. A job accepts 100 unique emails. A 101st address is not a second template, not a Free-plan tease, and not ENVELOPE_LIMIT. That is job-cap honesty: one hundred unique addresses is the paste box, Starter does not sell “more rows on this job,” and opening Billing will not grow the list.

How columns map is bulk send CSV column mapping. How the month counts is bulk send Free envelope math. If start fails after create, job created but send unfinished. Desk help is Docs. This guide is why the preview stops at one hundred unique emails, and why that stop is not the monthly send cap.

The FAQ and bulk send on Features send one template to a list. Ask Inkpacket for why a bulk send job stops at 100 unique emails to open this article. Ask how bulk send works to open help. Those phrases stay on the product screens. This article is the public version of A job accepts 100 unique emails — the string the desk already uses when the 101st unique address has nowhere to go.

What one hundred covers

• Up to 100 unique emails on one job. Duplicate emails in the list are sent once.
• Each unique address gets its own envelope. One hundred people are one hundred envelopes, not one envelope with one hundred recipients.
• Retrying a job skips rows that already sent. A second start does not mint a twin envelope for a person who already has a link.
• An optional access code (4–32 characters, no spaces) applies to every recipient on that job.

Need a 101st unique address? Start a second job from the same template. That second job’s sends count. Free allows 5 packets a month. Free at 5 packets a month is the live cap desk send, bulk rows, Web Form fills, and API send share. Hitting it returns HTTP 402 ENVELOPE_LIMIT. You can hit 402 on row 51 of a 100-row job on Free — the job cap and the month cap are different nos. A 101st unique email is refused before send. Do not use the 20-recipient list on one envelope to “avoid the job cap.” Twenty people on one id is routing, not bulk.

What this is not

• Not HTTP 402 ENVELOPE_LIMIT. That is the monthly send cap on a row that would exceed Free’s 5.
• Not Job created, but sending did not finish. That is start failing after create. Retry the same job.
• Not a seat cap. Teammate invites are a different object. Seat counts are planning numbers; invite does not refuse.
• Not checkout. Billing is not open. Paying a listed price does not add a 101st unique row.

Preview the count before you start. The number you see is unique emails, not raw paste lines. A list of 120 lines with 20 repeats is 100 unique — that job can start. A list of 101 unique addresses cannot. Mail still soft-fails per row. If invite email was not sent, open that envelope and copy the signing link. Text-message (SMS) is coming soon. Drive archive waits for completed. Stripe off: Payments not live. None of those flags raise the paste box.

The click-path

1. Open Bulk send. Pick a template. Paste or upload names and emails. Map the columns.
2. Confirm the preview is at or under 100 unique emails. Split a larger cohort into another job.
3. If a row returns HTTP 402 ENVELOPE_LIMIT, that is the monthly cap. Wait for the next month or stay on Free’s remaining sends.
4. If start fails after create, retry. Sent rows stay skipped.
5. On a phone, Bulk send is a drawer row. The 100-unique ceiling is the same. Help is not a drawer row — it stays in the header.

An envelope accepts up to 20 recipients. That is one id. Bulk send is the other direction: one template, many envelopes. Do not paste 100 names onto Documents → new #routing. Ask Inkpacket for why a bulk send job stops at 100 unique emails to open this article. Ask how bulk send works to open help. Ask bulk send to open the desk screen.

Ask and the list

Ask Inkpacket for why a bulk send job stops at 100 unique emails to open this article. Ask how bulk send works to open help. Marketing Ask stays site Q&A and deep links. It will not start the job, split the CSV, or add a 101st unique address from this article. One hundred is the job. A second job is the overflow.

Caps and what is not open yet

Adding a 101st unique email is not a send. Start of a legal 100-row job is — each sent row counts. Free allows 5 packets a month. Free at 5 packets a month is the live cap desk send, bulk rows, Web Form fills, and API send share. Hitting it returns HTTP 402 ENVELOPE_LIMIT. Starter is 20 envelopes — more than Free — plus 3 published Web Forms. Seat counts are planning numbers; invite does not refuse when a workspace is full.

Billing is published, not charging. Checkout is not open. Text-message (SMS) is coming soon. Drive missing: Drive not configured. Stripe off: Payments not live. Those flags do not add a 101st unique row or hide mapping. The FAQ and More on bulk send use A job accepts 100 unique emails in the same words.

Stay at one hundred unique on this job. Start another job if you must. Open a workspace on Free — see published pricing — and paste a 101st throwaway unique address so job-cap honesty is a stopped preview you already saw, not a Starter checkout you hoped would grow the box.