Skip to content

Prompt Chain: Automate Shift Coverage When Employees Call Out

For QSR Assistant Managers ·

Tools:Zapier + 7shifts + Twilio (SMS)
Time to build:1.5-2 hours
Difficulty:Intermediate-Advanced
Prerequisites:Comfortable using ChatGPT for scheduling. See Level 3 guide: "Draft Your Weekly Schedule with ChatGPT"

What This Builds

Instead of spending 30-60 minutes calling and texting every time an employee doesn't show up, this automation does the work for you: when a shift is marked as uncovered in your scheduling app, it automatically texts a targeted list of available employees asking them to claim it. The first person to reply YES gets it, and you're notified. You go from reactive scrambling to a 2-tap resolution.

Prerequisites

  • 7shifts account (free tier or above) at app.7shifts.com
  • Zapier account (free tier at zapier.com, which includes 100 tasks/month)
  • A Twilio account (twilio.com, free trial includes $15 credit, about 500 SMS messages)
  • About 2 hours of uninterrupted setup time (do this on a day off or slow morning)
  • A list of employee phone numbers

The Concept

Think of this automation as a phone tree that works itself. Normally when someone calls out, you manually text 5-10 people one by one, waiting for replies, maybe calling some of them. This workflow does that automatically:

  1. You mark a shift as "open" in 7shifts
  2. Zapier detects the change
  3. Zapier sends a text message to a group of available employees via Twilio
  4. You get notified when someone replies YES
  5. You confirm the pickup in 7shifts

It's like having a coordinator whose only job is covering call-outs, except it costs about $5/month to run.


Build It Step by Step

Part 1: Set Up Your Accounts

Twilio (5 minutes):

  1. Go to twilio.com → click Start for free
  2. Create an account with your email
  3. When prompted for "What are you building?" select SMS / Messaging
  4. Twilio will provision a phone number for you (note it: this is your "from" number for texts)
  5. Go to Account → note your Account SID and Auth Token. You'll need these in Zapier

Zapier (5 minutes):

  1. Go to zapier.com → create a free account
  2. No setup needed yet. You'll use it in Part 2

Part 2: Create Your Zapier Automation

  1. Log into zapier.com → click Create Zap

Trigger: "When a shift becomes uncovered in 7shifts":

  • Search for 7shifts as your trigger app
  • Select trigger event: New Open Shift (or Shift Updated, whichever fires when a shift is open/uncovered)
  • Connect your 7shifts account (Zapier will ask for your 7shifts API key, found in 7shifts under Settings → API)
  • Test the trigger by marking a future shift as open in 7shifts, then verify Zapier detects it

Action: "Send SMS via Twilio":

  • Add a Zap step: search for Twilio
  • Select action: Send SMS Message
  • Connect your Twilio account (use the Account SID and Auth Token from Part 1)
  • Configure the message:
  • From: your Twilio phone number
  • To: for now, set this to your own phone number to test
  • Message body:
Copy and paste this
    [Store Name] — Shift available: [shift date] [shift time]. Reply YES to claim it. First YES gets it. Reply STOP to opt out.
    ```
- Use Zapier's data fields to pull the date and time from the 7shifts trigger data

**Test the full automation:**
- Mark a test shift as open in 7shifts
- Wait 60 seconds
- Check your phone. You should receive the text

If the text arrives: your basic automation is working.

---

### Part 3: Send to Multiple Employees

The free Zapier plan sends one message per trigger. To text multiple employees, use one of these approaches:

**Option A (Easiest, Free):** Create a Twilio Messaging Service
1. In Twilio, go to **Messaging** → **Services** → **Create Messaging Service**
2. Add your employees' phone numbers as recipients
3. In Zapier, change the **To** field to your Messaging Service SID
4. Twilio will send to all numbers in the service

**Option B (More Control, Paid Zapier):** Add a multi-step Zap
- On Zapier's paid plan ($20/mo), you can loop through a list of phone numbers and send individual texts
- This allows more customization (e.g., only text employees with matching availability)

For most QSR locations, **Option A is sufficient**. It's free and broadcasts to all employees.

---

### Part 4: Handle Replies and Assign the Shift

Twilio can receive SMS replies. To handle "YES" replies:

1. In Zapier, create a second Zap:
- **Trigger:** New Twilio Incoming Message
- **Filter:** Only continue if message body contains "YES"
- **Action:** Send yourself an SMS notification: "Reply: [employee name] said YES for [shift details]"

2. Manually confirm the pickup in 7shifts and notify the employee via the app

**What good looks like:** You get a text notification within minutes of marking a shift open. You spend 30 seconds confirming the pickup instead of 45 minutes scrambling.

---

## Real Example: Actual Workflow End-to-End

**Setup:** You've configured the automation with 8 available employees in the Twilio messaging service.

**Input:** At 6:45am, Jamie texts you: "Can't come in today." You open 7shifts on your phone, find Jamie's 11am-7pm shift, and mark it as "Open."

**What happens automatically:**
- Zapier detects the open shift within 60 seconds
- Twilio sends a text to all 8 employees: "[Store Name]. Shift available today 11am-7pm. Reply YES to claim it."
- Marcus replies YES at 7:02am
- You get a notification text: "Marcus replied YES for today's shift"

**Output:** You open 7shifts, assign the shift to Marcus, and confirm. Total your time: 3 minutes. Old total: 45 minutes of calls and texts.

**Time saved:** 40+ minutes per call-out, 3-5 call-outs per week = 2-3 hours of recovered management time per week.

---

## What to Do When It Breaks

- **Zapier says "trigger not found"** → Check that your 7shifts API key is still valid (Settings → API in 7shifts). Re-authenticate the connection in Zapier if needed.
- **Twilio texts not sending** → Check your Twilio account balance, the trial credit can run out. Add $10 to your account ($10 covers ~350 messages).
- **Employees not responding** → The automation can't force people to reply, but you can improve it by sending a follow-up text after 10 minutes of no reply. Add a second Zapier step with a delay + second message.
- **Texts going to spam** → Have employees add the Twilio number to their contacts as "[Store Name] Scheduling"

## Variations

- **Simpler version:** Skip Twilio entirely. Create a Zapier Zap that, when a shift goes open in 7shifts, sends you an automated email or Slack message with a pre-drafted group text to copy and send manually. Less elegant but no Twilio setup.
- **Extended version:** Add a Google Forms link in the text so employees can indicate which shifts they WANT in advance, then Zapier can prioritize based on expressed interest.

## What to Do Next

- **This week:** Test the automation with your own number and verify it works end-to-end before rolling out to staff
- **This month:** Analyze whether coverage time improves by tracking time from "call-out" to "shift filled" before and after
- **Advanced:** Connect the automation to your payroll system so that claimed shifts automatically populate hours tracking

---
*Advanced guide for QSR Assistant Manager professionals. These techniques use more sophisticated AI features that may require paid subscriptions.*