Automated SASSIE Submission QA Flags
Every hour, WebRun opens SASSIE, reviews newly submitted shop reports, checks each for missing required fields, thin narrative answers, or a missing receipt image, and logs anything incomplete to a Google Sheet with the specific issue so an editor can fix it before the client sees it.
How do I catch incomplete mystery shop submissions before they go to the client?
WebRun checks SASSIE every hour for newly submitted shop reports, screens each for missing required fields, thin narrative answers, or a missing receipt, and logs anything incomplete to a Google Sheet with the exact issue found. Editors still make every edit and approval call, so nothing reaches a client without human review.
- Incomplete submissions are caught within the hour, not at the end of the week
- Editors see the exact issue instead of re-reading every report cold
- Clean submissions never clutter the QA queue
Built for mystery shopping companies · report editors · field audit QA teams · market research firms
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 - review new shop submissions
sassieshop.com
WebRun opens SASSIE to review new shop submissions. - Open SASSIE and list shop reports submitted in the last hour
- Check each for missing required survey fields, narrative answers under the expected length, and a missing receipt or photo
- Note the specific issue found for each flagged submission
Done when Every new submission has been checked against the completeness criteria.
-
2
Google Sheets - log submissions needing editor review
google.com
WebRun opens Google Sheets to log submissions needing editor review. - Open the QA Queue sheet
- Add a row for each flagged submission with the shopper, shop, client, and the exact issue found
- Leave clean submissions off the queue so editors only see what needs attention
- Remove a row once an editor marks the submission fixed
Done when The QA queue lists every submission that needs an editor's attention, with the reason why.
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 reject or edit the submission itself?
No. WebRun only flags what looks incomplete and logs the reason. An editor still reviews, edits, and approves or rejects every submission in SASSIE.
What counts as an incomplete submission?
A missing required field, a narrative answer far shorter than expected, or no receipt or photo attached where one is required. Each flagged row names the exact issue.
Will a clean submission show up in the queue for no reason?
No. Only submissions with a real completeness issue are logged, so editors are not sifting through reports that already pass.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.