All templates

Automated SASSIE Rejected Shop Reassignment

Every hour, WebRun opens SASSIE, finds shop submissions an editor rejected, logs the shop, client, and rejection reason to a Google Sheet, and posts a Slack alert to your scheduling team so a reshop gets queued before the client's deadline slips.

Deploy this workflow Browse all templates
Runs on WebRun · Strict Lockdown policy
Every hour WebRunorchestrates each step
1 SASSIE find newly rejected submissions
2 Google Sheets log the reshop queue
3 Slack alert scheduling to queue a reshop
In short

How do I route a rejected mystery shop back out for a reshop?

WebRun checks SASSIE every hour for shop submissions an editor rejected, logs each one with its client, location, and rejection reason to a Google Sheet, and posts a Slack alert to your scheduling team so a reshop gets queued in time. WebRun never reassigns a shop itself, scheduling makes that call.

  • Rejected shops get queued for a reshop within the hour, not days later
  • Scheduling sees the rejection reason without digging through SASSIE
  • No shop silently falls through after failing QA

Built for mystery shopping companies · scheduling coordinators · QA editors · field audit agencies

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens sassieshop.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    SASSIE - find newly rejected submissions
    sassieshop.com
    WebRun in SASSIE: find newly rejected submissions
    WebRun opens SASSIE to find newly rejected submissions.
    • Open SASSIE and list shop submissions marked Rejected in the last hour
    • Read the editor's rejection reason for each
    • Capture the client, location, original shopper, due date, and rejection reason

    Done when Every newly rejected submission is identified with its rejection reason.

  3. 2
    Google Sheets - log the reshop queue
    google.com
    WebRun in Google Sheets: log the reshop queue
    WebRun opens Google Sheets to log the reshop queue.
    • Open the Reshop Queue sheet
    • Add a row per rejected shop with the client, location, reason, and original due date
    • Mark whether the client's deadline still allows time for a reshop
    • Remove a row once scheduling confirms a new shopper is assigned

    Done when The reshop queue lists every rejected shop and whether time remains to redo it.

  4. 3
    Slack - alert scheduling to queue a reshop
    slack.com
    WebRun in Slack: alert scheduling to queue a reshop
    WebRun opens Slack to alert scheduling to queue a reshop.
    • Post an alert to the scheduling channel for each newly rejected shop
    • Include the rejection reason and how much time remains before the client deadline
    • Leave the reassignment decision to the scheduling team. WebRun does not reassign shops itself

    Done when Scheduling has a live alert for every shop that needs a reshop.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
sassieshop.com
ScheduleRuns automatically on this cadence
Every hour
DeliveryHow each run's result reaches you
Reshop queue · Slack
OutputWhat each run produces - A Google Sheet reshop queue plus a Slack alert for every newly rejected shop needing reassignment.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Does it reassign the reshop to a new shopper itself?

No. WebRun only logs the rejection and alerts scheduling. Your team picks and assigns the shopper who does the reshop in SASSIE.

How does it know a submission was rejected?

It reads the live status in SASSIE each hour, so any submission an editor marks Rejected is picked up and logged with the stated reason within the hour.

What if the client deadline has already passed?

It is still logged and flagged in the queue so scheduling can decide whether to request an extension or close it out, rather than the shop silently disappearing.

Keep going

Related templates

Automated SASSIE Client Results Report Drafts
Every Monday, WebRun pulls the past week's completed and approved shops for each client program from SASSIE, compiles the scores and flagged issues into a Google Sheet, and drafts a summary email in Gmail for your account manager to review and send.
SASSIE›Google Sheets›Gmail
Automated SASSIE Completion Rate Digest
Every night, WebRun tallies each client program's shop completion rate in SASSIE, compares it against the pace needed to hit the target date, and posts a Slack digest so management can see which programs are falling behind before the client does.
SASSIE›Slack
Automated SASSIE Geo Verification Fraud Flags
WebRun checks each submitted shop in SASSIE for GPS coordinates that do not match the shop location or a visit duration that looks implausible, logs anything suspicious to a Google Sheet, and alerts your QA team in Slack to investigate before it reaches a client.
SASSIE›Google Sheets›Slack

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.

Deploy this workflow Talk to us