Opt-out suppression implementation
Stop sending follow-ups to people who opted out.
Pay for one concrete code slice for an existing SMS, voicemail, email, or lead follow-up pipeline. Delivery is a suppression schema, pre-send guard, inbound STOP handler sketch, tests, and README patch.
No customer lists, passwords, live API keys, regulated data, or production dashboard access. Submit the stack, flow, and public repo/zip/spec link.
Pre-send guard
Skip suppressed contacts.
Call the guard before Day 1, Day 3, Day 7, Day 14, or Day 21 sends so permanent opt-outs and duplicate stage sends are blocked.
Inbound STOP
Record opt-outs.
Use the Lambda/API Gateway handler sketch to capture inbound STOP replies from SMS or provider webhooks.
Schema
Hash contacts by default.
The slice stores contact hashes, channel, reason, source, and timestamp so the suppression list can work without raw list exports.
Tests
Proof before wiring.
Unit tests cover phone normalization, permanent opt-outs, and duplicate-stage blocking inside the rolling window.
What the $99 slice includes
- Suppression-list schema for permanent opt-outs and rolling campaign windows
- Dependency-free Python pre-send guard module
- AWS Lambda handler sketch for inbound STOP capture
- Unit tests and build proof from the generated package
- README and handoff notes showing exactly where to wire the guard
Good fits
- Python lead pipeline with SMS or ringless voicemail stages.
- AWS Lambda, S3, DynamoDB, Airtable, or SQLite-backed workflows.
- Follow-up automations that need STOP handling before scaling.
- Buyers who can share a public repo, zip, or detailed spec without secrets.
Submit the stack
Checkout asks for tools, current follow-up flow, and a public repo/spec link.
Receive the code slice
The runner packages schema, guard code, Lambda sketch, tests, and handoff files.
Wire it safely
The owner connects it inside their account after reviewing the package and adding real credentials locally.
Real implementation boundary