All templates

Automated SASSIE Wave Scheduling Reminders

Every Monday, WebRun opens SASSIE, finds shoppers eligible for the current wave who have not yet claimed a shop, drafts a short SMS reminder in Twilio letting each know the claim window is closing, and logs who was reminded to a Google Sheet so scheduling can track wave fill progress.

Deploy this workflow Browse all templates
Runs on WebRun · Strict Lockdown policy
Every Monday at 8:00 AM WebRunorchestrates each step
1 SASSIE find eligible shoppers who have not claimed a wave shop
2 Twilio draft the claim window reminder
3 Google Sheets log wave fill progress
In short

How do I remind shoppers to claim shops in an open wave before it closes?

WebRun checks SASSIE every Monday for shoppers eligible for the current wave who have not claimed a shop, and drafts a short SMS reminder in Twilio naming the wave and claim deadline for each. Drafts are queued, never sent, and a Google Sheet tracks claim progress, so waves fill faster without unclaimed shops going unnoticed.

  • Wave capacity fills faster with a timely nudge before the claim window closes
  • Scheduling tracks claim progress against total wave capacity in one sheet
  • No SMS reaches a shopper without staff review

Built for mystery shopping companies · scheduling coordinators · field audit agencies · client program managers

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 eligible shoppers who have not claimed a wave shop
    sassieshop.com
    WebRun in SASSIE: find eligible shoppers who have not claimed a wave shop
    WebRun opens SASSIE to find eligible shoppers who have not claimed a wave shop.
    • Open SASSIE and list the current wave's eligible shoppers
    • Keep only shoppers who have not yet claimed a shop in this wave
    • Capture the wave name, claim deadline, and available shop count for the region

    Done when Every eligible shopper who has not claimed a wave shop is identified.

  3. 2
    Twilio - draft the claim window reminder
    twilio.com
    WebRun in Twilio: draft the claim window reminder
    WebRun opens Twilio to draft the claim window reminder.
    • Draft a short SMS to each eligible shopper naming the wave and the claim deadline
    • Queue each message in Twilio without sending it
    • Leave every reminder unsent for staff to review and send. WebRun never texts a shopper on its own

    Done when A reviewed reminder draft is queued for every eligible shopper who has not claimed a shop.

  4. 3
    Google Sheets - log wave fill progress
    google.com
    WebRun in Google Sheets: log wave fill progress
    WebRun opens Google Sheets to log wave fill progress.
    • Open the Wave Fill Tracker sheet
    • Log the wave name, total shops, claimed count, and how many reminders were queued
    • Update the claimed count as shoppers pick up shops through the week

    Done when The tracker shows this wave's claim progress against total capacity.

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 Monday at 8:00 AM
DeliveryHow each run's result reaches you
Wave fill tracker · Google Sheets
OutputWhat each run produces - Queued Twilio SMS drafts for unclaimed wave capacity plus a Google Sheet tracking claim progress.
Drafts
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

Will it text shoppers about a wave without review?

No. Every reminder is queued as a draft in Twilio. A staff member reviews and sends it, so nothing reaches a shopper automatically.

Which shoppers get a reminder?

Only shoppers already eligible for the current wave who have not yet claimed a shop. Anyone who claims one after the reminder is drafted is skipped on the next run.

Does it open or close the wave itself?

No. WebRun only reminds eligible shoppers and tracks how many shops are claimed. Opening, closing, or extending a wave stays a decision your scheduling team makes in SASSIE.

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