Second Victim Tripwire
When two customers report the same scam, freeze the source and warn the rest.
The job
Stops phishing through a hacked partner account before a third customer pays, using the first two victims' reports as the trigger. Gives compliance a record ready for the regulator.
The moment
50 minutes apart, two guests of the same hotel, writing in different languages, report messages asking them to re-verify their card.
The second report turns the case red. A comparison links it to two other hotels hit by the same wording last week.
The trust and safety lead approves, and 143 upcoming guests get a warning in six languages before a third guest pays.
The board then counts 14 quiet days at that hotel.
What it does
- Approve freeze of property messaging
- Warn upcoming guests
- Notify partner manager
- Log case / merge variant
- Send monthly fraud report
What you see
Grey-until-second-report tripwire board with a freeze-and-warn pipeline, a script similarity network, and a monthly regulator-ready report
What it moves
Victims per affected property after the second report, with a target of zero, the minutes from the second report to freezing the source, and the estimated losses avoided as a dollar range.
Built for
- Risk & fraud
- CX leaders & VoC
- QA, training & knowledge
- Compliance, complaints & legal
