Why Signature Requests Land in Spam, and the Fix
A signature request that sits in a spam folder is a stalled deal with no error message. The sender sees nothing wrong, and the signer never sees the email. This post covers the mechanics that push signature requests into spam or Promotions, and the sender-side and signer-side steps that reduce the odds.
Delivery and deliverability are different events. Delivery means the message reached the recipient's mail server. Deliverability means it reached the primary inbox instead of the spam folder or the Promotions tab. A signature request can pass the first test and fail the second, and nothing on the sender's side reports the failure. The deal simply waits.
Mailbox providers such as Gmail, Outlook, and Yahoo each apply their own filtering rules, but the inputs overlap. Sender reputation, authentication, and engagement all feed the decision. Reputation is built from signals such as bounce rates, complaint rates, and how recipients react to your mail. A filter does not need to read your contract language to distrust a message; it only needs the sending pattern to look wrong.
Signature requests land in spam for specific reasons. They are short. They hinge on one link. They often come from an address the signer has never received mail from, at the moment a deal is live and time matters. Those traits resemble the profile filters are built to catch, so every other signal on the message needs to be clean.
Sender-side checks, in the order worth running:
- Link hygiene. Filters grow suspicious of links that point to spam-related domains, run through shorteners such as bit.ly, or pass through multiple redirects. Use the full, readable URL. If a link has to be shortened, make sure it resolves to a verified page.
- Attachment type. Files ending in .exe, .zip, and .rar are treated as potential threats, and some providers block executables outright. If you attach the agreement, send a PDF. Better, link to the document instead of attaching it.
- Subject line. Describe the item and the action in plain words. Avoid false prefixes that imply a reply thread that does not exist.
- Address quality. Invalid addresses produce bounces, and bounces count against reputation. A mistyped address on a one-off request is a small problem; a habit of sending to unchecked addresses is a reputation problem.
- Authentication. Confirm with your email provider that your sending domain is authenticated, since authentication is one of the inputs providers weigh.
- Monitoring. If you send from a Gmail account, Google Postmaster Tools can help you monitor sender reputation over time.
Complaints deserve their own line. The most common route into spam is a recipient manually marking a message as unwanted, which happens when mail reaches people who did not expect it. The sources behind this advice are written for bulk and marketing mail, so unsubscribe links and consent rules apply there more than to a one-to-one request. The underlying mechanism still carries over: a signer who did not expect the email is the signer most likely to flag it. Tell the counterparty a request is coming, by phone or chat, before you send it.
Signer-side steps are short. Ask the signer to check the spam folder and, on Gmail, the Promotions tab, since those are the two places a message that reached the server but not the inbox tends to end up. Give them the sender name and the subject line so they can search for it. If it is not there within a minute or two, change the channel instead of repeating the same send.
This is where channel choice matters. lockd lets you send the signing link by WhatsApp, SMS, or email, or copy it and paste it wherever the conversation is already happening. The signer opens it on their phone, with no account and no app download. If email is the channel being filtered, the same link goes out through another one. The audit trail records each action (drafted, sent, signed, finalized) with a timestamp and IP, so a deal that shows as sent but not signed is a clear cue to try a second channel rather than wait.
A practical order of operations when a request goes missing: first, confirm the address. Second, have the signer check spam and Promotions. Third, review the link and attachment against the list above. Fourth, resend through a different channel with the same link. Each step is cheap, and the sequence separates a one-time filter decision from a pattern worth fixing at the source.
None of this removes filtering variance. Each mailbox provider applies its own rules, so a message that reaches the inbox at one provider can be held at another. The goal is to remove the avoidable signals, keep a second channel ready, and make sure a quiet inbox is never mistaken for a signer who has gone silent.