Void does not email the signer

Void is the sender stopping an in-flight envelope. Every signing and embed link on it stops working. The signing page says This signing link was voided. The audit log records the void. A webhook can fire voided. What void does not do is email the signer. The link simply dies. That is silent-void honesty: outstanding people will not get a “this was cancelled” message from Inkpacket, and Settings → Outbound email being Resend configured does not add one.

When to void at all is when to void, correct, or resend an envelope. After a mark already landed, the comparison is void after a partial sign versus decline. Decline does notify the sender when mail is configured — that is the other direction. Desk help is Docs. This guide is the missing outbound message.

The FAQ says void stops signing links. Features names the same stop under envelope admin. Ask Inkpacket for void does not email the signer to open this article. Ask how to void an envelope to open help. Those phrases stay on the product screens. This article is the public version of why their inbox stays quiet after you cancel.

What silence means

• The token is dead. Opening it shows This signing link was voided. Embed shows the same close.
• Reminders stop. A scheduled nudge will not go out after the void.
• No void email is generated — with or without RESEND_API_KEY.
• The sender is not emailed a void receipt either. Read the document on the desk.

Tell outstanding people out of band if they need to know the deal is off. Paste nothing from the old copy box. That URL is finished. If mail was already skipping on the original invite — Invite email was not sent — void does not suddenly deliver a cancellation. Copy-link honesty still applies to the send you already made, not to this close — copy the signing link after mail skips.

Decline is the noisy close

When a signer declines, the sender is emailed when Resend is configured; otherwise the decline is logged. That is the one close that tries to talk to the desk operator. Void never tries to talk to the signer. Do not void expecting the product to “let them know.” Do not decline-on-their-behalf by asking them to refuse so that you get an email. If you already know collection should stop, void and send your own note.

Completed envelopes cannot be voided. Expired and declined envelopes cannot be voided either. Only SENT envelopes show Void envelope. Already-voided envelopes return This envelope is already voided. Public API: POST /api/v1/packets/:id/void with an optional reason. The reason is for your audit, not for an email body Inkpacket will not send.

The click-path

1. Open the sent document. Void envelope. Record a reason if you want it on the trail.
2. Message outstanding people yourself. Do not wait for Inkpacket to do it.
3. If the work still needs a signature, send a new envelope from the PDF or template. Count it.
4. If you only had the wrong email and nobody has signed, correct instead — that does send a new invite.
5. Do not open Billing to “turn on void mail.” Checkout is not open and does not add a From line for cancellations.

From and Reply-To are still install-level, not a workspace composer — Settings email From and Reply-To. There is no void-template card next to that flag. SMS is not a void channel either. Text-message (SMS) is coming soon still means no text, and with keys present void still does not text a cancellation. Drive archive waits for completed; a voided envelope is not archived as a filed copy.

Ask and webhooks

Ask Inkpacket for void does not email the signer to open this article. Ask how to void an envelope to open help. Marketing Ask stays site Q&A and deep links. It will not void the envelope or draft the out-of-band note. If your own system must tell the signer, listen for envelope.voided and send that mail yourself after you verify HMAC-SHA256 of timestamp.body — webhook signature verify checklist.

Caps and what is not open yet

Void is not a send. The send that created the envelope already counted. 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 void email or un-void an envelope. The FAQ and More on voiding, correcting and resending use void does not email the signer and the link simply dies in the same words.

Stop the links. Send the human note yourself. File signed-then-voided if a mark already landed. Open a workspace on Free — see published pricing — and void one throwaway so silent-void honesty is an inbox that stayed quiet on purpose, not a missing feature you opened Billing to buy.