Listening …
For senders
MarketMute sits on both sides of the same call. The individual gets their opt-outs enforced — you get a way to respect them before you dial, without ever receiving a single piece of personal data from us.
Verso · The argument
An opt-out that only lives in a system you never check doesn't travel with a list you just bought. The check is one API call, not a project.
Every call to someone who objected risks a case, an escalation, and time your organization hadn't planned for.
Removing the people who will never say yes raises the hit rate on what's left. You call fewer people, but the right ones.
Every check gets a timestamped receipt number. If someone claims you called despite an opt-out, you can show exactly what you asked and what you were told.
Recto · The integration
You send a hashed identifier and a purpose. We answer whether an opt-out exists — never who the person is, never why. The excerpt below is the entire integration, not a simplified version of it.
# Before sending: ask whether the recipient is opted outcurl -sS https://api.marketmute.com/v1/suppression/check \ -H "Authorization: Bearer $MARKETMUTE_KEY" \ -H "Content-Type: application/json" \ -d '{ "channel": "phone", "identifier_hash": "sha256:9f1a…c07d", "purpose": "direct_marketing" }' # Response{ "suppressed": true, "scope": "sender", "receipt_id": "rcpt_01HZK4…"}Four steps separate registration from the first check. Two happen in your systems, two happen in ours. The middle column is the boundary — and raw contact data never crosses it.
Organization number and a contact channel. No integration required to get started.
Incoming deletion and opt-out requests are handled in our interface, free of charge for you.
The number is normalized and hashed in your systems. We never receive raw contact data.
One call per recipient, or a batch before the campaign. The receipt is kept on both sides.
Boundary
Next step
Start with the portal. Add the API when volume calls for it.
Answering incoming requests costs nothing and needs no technical integration. The pre-send check is the next step, once you'd rather avoid the problem than manage it.