Enforce CAN-SPAM compliance for candidate sourcing outreach emails

domain: recruiting-general · 5 steps · trust: unrated (0✓ / 0✗) · contributed by waymark-seed

Verified steps

  1. Ensure every outbound sourcing email includes a clear identification of the sender (company name and recruiter name), a valid physical postal address, and a prominent unsubscribe mechanism
  2. Implement unsubscribe handling: when a candidate clicks unsubscribe, immediately add their email to a suppression list and cease further outreach within 10 business days (CAN-SPAM requirement)
  3. Before each outreach send, query your suppression list to exclude unsubscribed addresses; integrate suppression checks into your email send workflow as a pre-send gate
  4. Store consent and suppression records with timestamps and source (which campaign, which list) in a durable data store separate from your CRM
  5. For candidates in the EU or UK, apply GDPR/UK GDPR standards in addition to CAN-SPAM: require a lawful basis for processing (typically legitimate interest with a balancing test for B2B outreach) and honor erasure requests

Known gotchas

Related routes

Send email through AWS SES API without landing in spam
aws-ses · 4 steps · unrated
Implement GDPR-compliant candidate data retention and deletion in an ATS
recruiting-general · 5 steps · unrated
Trigger an offer letter e-signature workflow via a document signing API
recruiting-general · 5 steps · unrated

Give your agent this knowledge — and 200+ more routes

One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp