Approve client campaigns with findings you can point to later
An agency signs off on sends it did not fully build and will still be blamed for. SendProofs gives the account lead a repeatable evidence step between the final test and the word "approved" — one that leaves a record in the thread.
The moment this matters
The approval moment: the client's campaign is built, the final test has landed, and the go/no-go sits with your account lead in an email thread. Today the diligence is usually someone on the team clicking through the test in their mail client — real work that leaves no trace. When a tracked link dies after launch, the client's first question is "did you check the links before approving?", and a memory of clicking is not an answer. A recorded pre-send QA step is.
Who owns the decision
The account lead who replies "approved" on the client's behalf. They did not build the template, they may have nothing beyond a preview of the client's platform, and they carry the accountability anyway. The asymmetry is the whole problem: the client owns the list and the sending platform; the agency owns the sign-off — and inherits the blame. That is exactly the position where the decision-maker needs evidence that exists outside anyone's memory.
The evidence step before sign-off
-
Get the final test delivered to your own inbox
Have the client's platform send it to your address directly. The delivered message is the artifact — with the client's link rewriting and tracking already applied.
-
Save the message as a .eml file
Works with an email saved from Gmail or Outlook on the web.
-
Upload it to your SendProofs workspace
Links recognized as action-bearing by URL and link-text patterns — unsubscribe, sign-in, order actions — are marked Protected and never requested, which matters doubly when the account being acted on is your client's, not yours.
-
Review every state before you reply
Healthy needs nothing. Warning, Protected and Inconclusive items each need a named human decision — some of them the client's, not yours (what each state asks of you).
-
Write the findings into the approval thread
Read the report in your workspace and state what it shows: the check date, how many resources were checked, what was flagged and what you are asking the client to confirm.
The evidence handoff
The handoff is textual, and it is yours: the report stays inside your workspace, and the approval email carries the findings in your own words. A useful pattern — one line for the run (date, resources checked, outcome), then one line per item that needs the client: an Inconclusive partner domain to confirm, a Warning on tracking values to accept or fix. Months later the thread itself is the record — the diligence happened, on a date, with named findings. What a report contains.
A sample scenario
Sample data
A client supplied a co-marketing URL for the campaign's partner block. On the delivered test, partner.example/offer answered 403 to the SendProofs request: Inconclusive — the destination limited automated access, so the check could establish neither that it works nor that it is broken. The account lead flagged it in the approval thread and asked the client to open the link manually and confirm it before the send. The rest of the campaign's findings were resolved the same afternoon, and the approval went out with both facts stated.
Limitations and non-goals
- The report is read in your workspace, and the findings travel in your own writing — nothing is published or sent to the client automatically.
- SendProofs checks the delivered test you upload. It has no access to the client's sending platform, audience lists, segmentation or scheduling.
- Inconclusive is a finding, not a formality. A destination that refuses automated access needs a person to confirm it — usually the client — before you sign off.
- A clean run does not guarantee the campaign performs. It is evidence about link destinations at the moment of the check, and that is how you should present it.
Make the check a line item in every approval
Free workspace, no card at signup — run the evidence step on the next client test.