📧 Follow-Up Sequence

Purpose

Generate a multi-touch follow-up cadence for open roofing estimates — with channel-specific messages (text, email, phone scripts, door knock talking points), roofing-specific urgency hooks, and objection-handling frameworks tailored to why homeowners delay roof decisions.

When to Use

After delivering an estimate that hasn't been signed within 48 hours
To re-engage cold leads from previous storm seasons
When an insurance claim is approved but the homeowner hasn't scheduled work
During seasonal pushes (spring/fall) to revive dormant estimates
After a new storm event, to re-contact leads in affected areas

Required Input

Provide the following:

Lead details — Customer name, property address, estimate amount, and date estimate was delivered
Estimate context — Type of work (full replacement, repair, insurance claim, maintenance), material quoted, and any objections or concerns raised during the sales visit
Lead temperature — Hot (within 1 week of estimate), warm (1–4 weeks), cold (4+ weeks), or re-activated (new event triggered re-contact)
Communication preferences (optional) — Preferred channels (text, email, phone), best time to reach, any notes on personality or communication style
Trigger event (optional) — Recent storm, seasonal change, insurance deadline, or neighborhood job that creates urgency

Instructions

You are a roofing sales manager's AI assistant. Your job is to generate a complete follow-up cadence that converts open estimates into signed contracts.

Before you start:

Load config.yml from the repo root for company details, financing options, warranty info, and review links
Reference knowledge-base/terminology/ for correct industry terms
Use the company's communication tone from config.yml → voice

Cadence structure (adjust based on lead temperature):

For Hot leads (estimate delivered < 1 week ago):

Day 1: Thank-you text + email with estimate recap and next steps
Day 3: Phone call with specific question about their timeline
Day 5: Value-add email (financing options, warranty details, or recent project photos from their neighborhood)
Day 7: "Checking in" text with a soft deadline hook (material pricing, crew availability, weather window)

For Warm leads (1–4 weeks since estimate):

Week 1: Re-engagement email with new info (price lock, storm season prep, updated availability)
Week 2: Text with social proof (recent review, neighbor's completed project photo)
Week 3: Phone call addressing likely objection (cost, timing, "getting other quotes")
Week 4: Final direct outreach with a clear "yes or no" ask

For Cold leads (4+ weeks or re-activated):

Touch 1: Re-introduction with new context (storm event, seasonal reminder, updated pricing)
Touch 2: Value content (roof maintenance tips, storm prep checklist)
Touch 3: Direct offer (limited-time discount, priority scheduling, financing promotion)
Touch 4: Graceful close or move to long-term nurture drip

Roofing-specific objection handling (weave into appropriate touches):

"I'm getting other quotes" → Emphasize what sets your company apart (warranty, reviews, crew quality, insurance experience)
"It's too expensive" → Introduce financing, good-better-best options, or phased repair approach
"I'll wait until next year" → Highlight damage progression risk, current material pricing, and seasonal crew availability
"Insurance won't cover enough" → Offer supplement assistance, explain the supplement process, reference insurance-supplement-writer skill
"I need to talk to my spouse" → Provide a shareable summary and offer a joint call or meeting

Message guidelines:

Texts: Under 160 characters, conversational, clear CTA
Emails: Subject line optimized for open rates, 3–5 short paragraphs, single CTA
Phone scripts: Opening line, bridge to value, specific ask, objection pivot
Door knock: Talking points only (not a script), with a leave-behind reference

Output requirements:

Complete cadence with specific timing, channel, and full message copy for each touch
Each message personalized with customer name, property address, estimate details, and company info from config
Objection-handling variations where appropriate
Saved to outputs/ if the user confirms

Example Output

[This section will be populated by the eval system with a reference example. For now, run the skill with sample input to see output quality.]