Enforce · Verify
Automated sequencing. Human-controlled sending.
MapProtector prepares the next step and shows you exactly why it can or cannot be sent. A person approves it. It goes out from a sender you have verified, in your own words. Then the product watches for the cure.
Why can — or can’t — this send?
Before a notice is live, every blocker is shown as a first-class item: no seller contact on file, evidence not sealed, the policy changed since approval, the case already cured, a data-quality hold, an unverified sender, this month’s notice allowance used. A notice with one blocker cannot be sent, and the screen says which one.
- Blockers are explained in words, next to the action they block
- Approve and Send are separate, deliberate steps — never a casual button
- A sent notice is an immutable snapshot of exactly what went out
- Seller contact on fileClear
- Evidence sealedClear
- Policy unchanged since approvalClear
- Case not curedClear
- No data-quality holdClear
- Sender verifiedBlocks sending
- Within this month’s notice allowanceClear
Your templates, your sender, your words
Notices are built from templates you write — with a starter example you are asked to review against your own legal and compliance policy before using it. They are sent from a sender identity you have verified, with your reply-to, so a seller’s response comes back to you. MapProtector does not put its name on your notice.
- Templates with placeholders for the seller, the product, the price and the policy
- Sequences: a first notice, an escalation, a final notice — each stage approved
- Monthly notice allowance by plan; a test marker on anything sent outside production
- Stage 1First notice · sent 2026-09-04 · delivered
- Stage 2Escalation · due 2026-09-11 · awaiting approval
- Stage 3Final notice · not yet scheduled
Response, cure and recurrence
After a notice, the product keeps watching. A reply is recorded against the case. A subsequent observation at or above MAP records a cure and closes the episode. A later drop opens a new one and marks the recurrence — so a repeat offender looks like one, and a first offence looks like one.
- Cure recorded from observation, never assumed from silence
- Delivery failures and bounces surfaced, not swallowed
- The full chronology stays with the case for as long as you keep it
- 09-03 06:40 UTCBelow-MAP offer observed at 149.00 USD (MAP 199.00)
- 09-03 09:12 UTCConfirmed by D. Okafor · case opened
- 09-03 09:14 UTCEvidence captured and sealed
- 09-04 10:02 UTCFirst notice approved and sent from brand sender
- 09-08 06:40 UTCOffer observed at 199.00 USD · cure recorded
- 09-11 06:40 UTCBelow MAP again · new episode, recurrence noted
What this is, and is not
The product reports and applies. People decide.
MapProtector reports observations and applies the policies you configure. It does not provide legal advice, it does not determine that a seller has broken an agreement, and it does not send a notice nobody approved. Enforcement is your programme; the product makes it consistent, documented and defensible.
Enforcement starts on Growth.
Starter includes the workflow as a preview — build a template, see what a seller would receive — and sending begins on Growth.