Start with the packet and signer type
Two of the most common causes are on your side, not the signer's. First, the signing request only goes out after the packet is sent, so if the packet is still in draft, no email is triggered even though the document looks ready. Second, Anvil only emails signers whose type is email. If a signer is set up as an embedded signer, nothing is sent by design, because you are expected to deliver the signing link yourself.
Then check the address and the inbox
If the signer type is email and the packet was sent, confirm the address has no typos, since even embedded signers require a valid email. After that, treat it as a deliverability problem. Ask the signer to check spam and quarantine folders, allowlist your sending domain, and confirm your SPF, DKIM, and DMARC records if you send from a custom domain. Corporate security gateways often hold messages that contain outside links.
Stop depending on the email
The most reliable fix is to not depend on the email at all. With an e-signature API you can generate the signing link yourself and show it in your own app. In Anvil, the generateEtchSignUrl mutation returns a per-signer URL you can redirect to or embed in an iframe, and you can confirm progress with webhooks instead of watching an inbox. These links are short lived, so generate them when the signer is ready to sign rather than sending them ahead of time.
Back to All Questions