Automated SASSIE Geo Verification Fraud Flags
Every hour, WebRun opens SASSIE, checks each newly submitted shop's GPS coordinates against its expected location and its visit duration against a plausible range, logs anything suspicious to a Google Sheet with the specific mismatch, and posts a Slack alert to your QA team to investigate before it reaches a client.
How do I catch mystery shop submissions with suspicious location or timing data?
WebRun checks every SASSIE submission each hour for GPS coordinates that do not match the shop's location or a visit duration that looks implausible, logs the specific mismatch to a Google Sheet, and alerts your QA team in Slack to investigate. WebRun only flags the mismatch, a human always makes the fraud call.
- Suspicious submissions get flagged within the hour for a human to check
- QA sees the exact mismatch instead of re-checking every report by hand
- No shopper is accused or paid differently without a person reviewing the flag
Built for mystery shopping companies · QA and integrity teams · field audit agencies · client compliance programs
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
sassieshop.comin a real browser with your saved login - no setup, no API keys. -
1
SASSIE - check submissions for location and timing mismatches
sassieshop.com
WebRun opens SASSIE to check submissions for location and timing mismatches. - Open SASSIE and list shop reports submitted in the last hour
- Compare each submission's GPS coordinates against the shop's registered location
- Compare the recorded visit duration against a plausible range for that shop type
- Capture the specific mismatch found, location or duration, for each flagged submission
Done when Every new submission has been checked for a location or timing mismatch.
-
2
Google Sheets - log flagged submissions
google.com
WebRun opens Google Sheets to log flagged submissions. - Open the Fraud Review sheet
- Add a row per flagged submission with the shopper, shop, and the specific mismatch found
- Leave clean submissions off the sheet so QA only sees what needs a second look
Done when The review sheet lists every submission with a location or timing mismatch.
-
3
Slack - alert QA to investigate
slack.com
WebRun opens Slack to alert QA to investigate. - Post an alert to the QA channel for each newly flagged submission
- Name the shopper, shop, and the specific mismatch so QA knows what to check first
- Leave the fraud determination to a human reviewer. WebRun only flags the mismatch, it never accuses or bans a shopper
Done when QA has a live alert for every submission that needs a second look.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it decide a shopper committed fraud?
No. WebRun only flags a GPS or timing mismatch for a human to look at. Your QA team makes the actual determination and any action that follows.
What counts as a suspicious mismatch?
GPS coordinates that fall outside the shop's registered location, or a recorded visit duration far shorter or longer than plausible for that shop type. Both are checked on every submission.
Will a shopper's payment be affected automatically?
No. Flagging a submission does not touch payment or shopper status. That stays a manual decision your QA team makes after reviewing the flagged report.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.