Marketplace spam and scam reports

01

Starting point

A buyer reports account 123 for sending repetitive offers and suspicious payment links. The report itself is only one signal: the reviewer also needs account age, prior report volume, listing history, and any previous restrictions before deciding what to do.

02

What must hold

• Treating one unverified allegation as proof of abuse.
• Letting a webhook timeout silently remove an accepted report from the queue.
• Allowing automation to suspend a high-impact seller when evidence is incomplete or contested.

03

Step by step

1. Publish the visual workflow with an authority mode, a passing fixture, an immutable version, and explicit failure paths. Pin that version to the active queue policy before new reports enter it.
2. Accept the report from an embedded form, public page, or authenticated server API and immediately issue a tracking reference.
3. Use the intake-routing agent to classify the allegation and place it in the marketplace spam queue, recording why that queue was selected.
4. Read the queue policy and request only the enrichments it requires: account age, prior reports, and recent listing activity.
5. Let AI summarize low-risk evidence when the queue allows it, but send uncertainty, failed enrichments, repeat offenders, protected users, and material account actions to a human.
6. Record the decision, call the customer action endpoint idempotently, notify the relevant people, and keep any appeal human-decided.

05

Data exchange

The policy requests an account_profile finding. Safest Resolve sends the stable account reference in a signed request. The customer webhook returns the approved age and risk fields. The report keeps the response version and shows timeout or schema failures as review states.

06

Verification

The report records the allegation, relevant context, policy version, evidence source, current owner, reasoning, and allowed actions. The reporter receives an appropriately scoped status. The affected user receives a reason and appeal path when policy requires one.

07

Implementation questions