Automation: Set Up an Automated Lead Follow-Up Drip Sequence
For Roofing Sales Representatives
Tools: Zapier + JobNimbus (or AccuLynx) + Gmail | Time to build: 90–120 minutes | Difficulty: Intermediate-Advanced Prerequisites: Comfortable using ChatGPT to draft emails — see Level 1 guide: "Write a Post-Inspection Follow-Up Email"
What This Builds
You'll connect your roofing CRM (JobNimbus or AccuLynx) to Zapier, which automatically sends a sequence of pre-written follow-up emails to homeowners who haven't responded after your initial proposal. Instead of manually remembering to follow up at Day 1, Day 4, Day 10, and Day 21 — it happens automatically while you're on a roof.
Roofing deals require 5–12 follow-up contacts on average, but most reps give up after 2. This automation keeps following up for you until the lead responds or dies. The first time an automated Day-14 message brings a "dead" lead back to life as a $15K job, the 2 hours you spent building this will feel like the best investment you ever made.
Prerequisites
- Zapier account (zapier.com — free tier works for basic sequences; Starter plan at $20/mo for more zaps)
- A JobNimbus or AccuLynx account with API access (check with your manager)
- Gmail or Outlook account for sending follow-up emails
- Pre-written email templates for each touchpoint (you'll draft these using ChatGPT first)
- Time needed: 90–120 minutes to build; 0 minutes ongoing (runs automatically)
The Concept
Zapier is like a translator between apps — when something happens in one app (like a lead moving to "Proposal Sent" in your CRM), Zapier sees it and automatically does something in another app (like sending a follow-up email the next day). You set it up once; it runs forever.
Think of it like a hotel wake-up call service: you tell the front desk to call you at 7am, 8am, and 9am tomorrow, and they do — without you having to remember. Zapier tells Gmail to email your homeowner at Day 1, Day 4, Day 10, and Day 21 after their proposal is sent — without you having to remember.
Build It Step by Step
Part 1: Write Your Follow-Up Email Templates First
Before touching Zapier, draft your 4 follow-up emails using ChatGPT. Open ChatGPT and ask:
Write 4 follow-up emails for a roofing sales rep to send to a homeowner who hasn't responded after receiving a proposal. The emails should go out at Day 1, Day 4, Day 10, and Day 21.
Day 1: Gentle check-in — did they get the proposal?
Day 4: Add value — share one reason to act before winter (or next storm season)
Day 10: Create mild urgency — crew availability is filling up
Day 21: Last message — closing the loop, offer to re-inspect if things have changed
Keep them short (under 100 words each), warm, professional. Include [HOMEOWNER NAME] and [ADDRESS] as placeholders.
Save these 4 emails in a document. You'll paste them into Zapier in a few minutes.
Part 2: Set Up Your Zapier Account
Go to zapier.com and sign up (free account works to start). Once inside, click "Create Zap" at the top.
What you should see: A blank workflow canvas with a "Trigger" step and an "Action" step.
Part 3: Set Your Trigger (When Does the Automation Start?)
Click on the Trigger block. Search for "JobNimbus" (or "AccuLynx" if that's your CRM).
Select the trigger event: "Job/Lead Updated" or "Status Changed" — you want the automation to fire when a lead moves to "Proposal Sent" or your equivalent stage.
Connect your CRM account: Zapier will ask you to log in to JobNimbus. Follow the prompts. You may need your JobNimbus API key — find it in JobNimbus under Settings → API.
Configure the trigger: Select the pipeline stage that means "proposal sent to homeowner."
What you should see: A test trigger that shows a sample lead from your actual CRM, confirming the connection works.
Part 4: Add a Delay (Wait Until Day 1)
Click the "+" button after your trigger. Search for "Delay by Zapier". Choose "Delay For" and set it to 1 day.
This tells Zapier: "Wait 1 day after the trigger fires, then do the next step."
Part 5: Add Your First Email Action
Click "+" after the delay. Search for "Gmail" (or "Outlook" if that's your email). Choose "Send Email".
Connect your Gmail account. Then configure the email:
- To: Map to the homeowner's email field from your CRM (Zapier pulls this automatically)
- Subject: "Quick check-in — [Address]" (use the address field from your CRM)
- Body: Paste your Day 1 email template here, using Zapier's field mapping for [HOMEOWNER NAME] and [ADDRESS]
What you should see: An email template in Zapier with your copy and mapped fields for personalization.
Part 6: Repeat for Days 4, 10, and 21
Click "+" after the first email action. Add another "Delay For" — this time set it to 3 days (3 more days = Day 4 total). Then add another "Send Email" action with your Day 4 template.
Repeat:
- After Day 4 email → Delay 6 days → Day 10 email
- After Day 10 email → Delay 11 days → Day 21 email
What you should see: A 7-step Zap: Trigger → Delay 1 day → Email → Delay 3 days → Email → Delay 6 days → Email → Delay 11 days → Email.
Part 7: Turn It On and Test It
Click "Publish Zap" (blue button, top right). Your automation is now live.
Test it by moving a test lead in your CRM to "Proposal Sent." Check your email in 1–2 minutes — Zapier should have queued up the first message (it may not send immediately in testing; use Zapier's built-in test feature to verify the connection).
What you should see: Your Zap's task history showing it fired successfully and queued your emails.
Real Example: From Dead Lead to $14,000 Job
Setup: Mike built this automation in 90 minutes in March. He has 28 active leads in "Proposal Sent" status.
What happened automatically:
- Day 1: Homeowner at 88 Cedar Ave got "Hi Janet, just following up on the proposal I sent yesterday — did you have a chance to look it over? Happy to walk you through it."
- Day 4: "Hi Janet, wanted to share — winter storm season typically causes ice dams that can double the damage on roofs already weakened by hail. Worth acting on your current damage before then."
- Day 10: No response. Automated email: "Hi Janet, we have two crews opening up in your area next month — wanted to reach out before they fill up."
- Day 21: "Hi Janet, I'll take this as a sign you're not ready right now — completely understand. If things change, my number is always the same. Best of luck."
Janet responded to the Day 21 email: "Actually, I just filed my claim — can you come back out?"
Result: $14,200 job that would have been a lost lead without the automated follow-up.
Time Mike spent on follow-up: 0 minutes.
What to Do When It Breaks
- Emails aren't sending → Check your Gmail connection in Zapier — Google OAuth tokens occasionally expire and need to be reconnected.
- Wrong homeowner is getting the email → Check your field mapping in the Send Email step. Make sure the "To" field pulls from the lead's email, not a fixed address.
- Automation fires even after homeowner signs → Add a Zapier filter between the trigger and the delay: "Only continue if pipeline stage does NOT equal Contract Signed." This stops the sequence when the deal closes.
- Homeowner gets all 4 emails even after responding → Zapier doesn't know someone replied. Add a condition: check if the lead status changed to "Closed" or "Contract Signed" before each email step.
Variations
- Simpler version: Skip Zapier and just set calendar reminders in your phone at Day 1, 4, 10, and 21 for each lead. Manually send the email from your template. Takes 3 minutes per touch but no automation setup required.
- Extended version: Add a Day 3 text message (via Zapier + Twilio or OpenPhone) between the Day 1 and Day 4 emails. Texts have 98% open rates vs. ~20% for emails.
What to Do Next
- This week: Build the automation and activate it for your current active proposals
- This month: Track how many previously-cold leads re-engage through the automated sequence
- Advanced: Add a Day 3 SMS touchpoint via Twilio integration, and connect the sequence to stop automatically when the lead status changes to "Contract Signed"
Advanced guide for roofing sales representative professionals. Zapier Starter plan required for multi-step zaps ($20/month). CRM API access may require manager authorization.