Controlled communication · Reporting and history
Automated sequencing. Human-controlled sending.
MapProtector prepares the next notice from your policy and your sealed evidence and shows you anything standing in its way. A Brand Admin approves it and releases it. It goes out from your own verified brand identity, in your own words. Then the product watches for the correction.
Readiness checks
Before a notice can go, the page shows in plain words anything that still needs your team’s attention — a missing seller contact, unsealed evidence, a hold your team placed. A notice with anything outstanding cannot be sent, and the screen says what.
- Checks are explained in words, next to the action they affect, and repeated before anything leaves
- Approve and Send are separate, deliberate steps, each confirmed by a Brand Admin — never a casual button
- An approval covers one exact document, and a person looks again if the facts behind it change
- 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 example wording you are asked to review against your own legal and compliance policy before publishing anything from 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 prices, the policy and the references; every sent notice keeps the exact wording it went out with
- Controlled follow-up sequences — a first notice, an escalation, a final notice — each with the time a seller gets to respond, each approved by a person
- Monthly notice allowance by plan
- 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 as what the seller said — a claim to be authorized is a claim, not a standing — and pauses the sequence for a person to read. A breach closes only when the advertised price is confirmed back at policy. A later drop is recorded as a recurrence — so a repeat offender looks like one, and a first offense looks like one.
- A correction is confirmed from the advertised price, never assumed from silence, a hidden price or a promise
- Sent and delivered are shown separately, and a bounce is 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 program; 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.