Lead Generation & Automation

Quo Follow-Up Sequences

The SMS/text follow-up sequences that turn a new lead into a booked call.

Business: AZ Palm Tree Lights Phone: (480) 631-7754 Platform: Quo (OpenPhone) CRM: Jobber Automation: n8n (your n8n instance) Last updated: 2026-05-04

Overview & Architecture
Sequence 1: New Lead (Meta/Google/Website)
Sequence 2: Survey Hot Lead (CX Survey)
Sequence 3: Past Lead Reactivation
Sequence 4: Post-Install Review Request
n8n Workflow Architecture
Quo API Integration Notes
Google Sheets Tracking
TCPA Compliance Notes
Template Variables Reference
Performance Metrics & Targets
Photo & Media Recommendations

Overview & Architecture

System Map

Lead Source                  Trigger                    n8n Workflow              Quo
─────────────────────────────────────────────────────────────────────────────────────
Meta Lead Ad         ──────> Webhook (Meta Lead Ads) ──> Sequence 1 Workflow ──> SMS via Quo API
Google Ads call      ──────> Jobber new contact        ──> Sequence 1 Workflow ──> SMS via Quo API
Website form         ──────> Webhook (Fillout/Tally)   ──> Sequence 1 Workflow ──> SMS via Quo API
Fillout CX Survey    ──────> Webhook (Fillout)         ──> Sequence 2 Workflow ──> SMS via Quo API
Manual trigger       ──────> n8n Manual/Scheduled      ──> Sequence 3 Workflow ──> SMS via Quo API
Jobber job complete  ──────> Jobber webhook             ──> Sequence 4 Workflow ──> SMS via Quo API

Reply Detection Strategy

Quo sends inbound message webhooks to a designated endpoint. The n8n reply-listener workflow:

Receives the inbound Quo webhook
Matches the sender's phone number to an active sequence enrollment
Marks the enrollment as replied = true in the Google Sheet tracking log
Sets a flag on the Jobber contact (tag: quo-replied) via Jobber API
All subsequent sequence steps check the Google Sheet before sending — if replied = true, the step is skipped

This is the exit condition for all sequences that exit on reply.

Sequence 1: New Lead

Target: Cold leads from Meta lead ads, Google Ads calls, or website form submissions Tone: Warm, personal, no pressure Goal: Get the lead on a 5-minute call with Jack

Message Templates

Text 1 — Immediate (within 2 minutes of lead entry)

Hey [first_name], it's Jack from AZ Palm Tree Lights! Thanks for reaching out. I'd love to learn about your property and put together a free quote. When's a good time for a quick 5-min call? - Jack (480) 631-7754

Character count: ~192 (1 SMS segment) Send as: SMS

Text 2 — +4 hours (if no reply to Text 1)

Hey [first_name], just following up! I've got some availability [today/tomorrow] if you'd like to chat about lighting up your palms. No pressure either way.

Character count: ~155 (1 SMS segment) Send as: SMS Note: "today/tomorrow" should be dynamically replaced — use today if sent before 3pm AZ time, "tomorrow" if after 3pm

Text 3 — +24 hours from lead entry (if no reply)

Here's one we just finished in [neighborhood]. Would love to do something similar for your place. Got 5 minutes? - Jack

Send as: MMS with install photo See Photo Recommendations section for image selection guidance Note: [neighborhood] = Scottsdale or Paradise Valley based on lead's zip code if available, otherwise default to "Scottsdale"

Text 4 — +3 days from lead entry (if no reply)

Hey [first_name], last text from me! If palm tree lighting is still on your radar, I'm here whenever you're ready. You can also check out our work at azpalmtreelights.com/gallery. - Jack

Character count: ~180 (1 SMS segment) Send as: SMS

Exit Conditions:

Lead replies to any message
Lead is tagged quo-replied in Jobber
Lead is marked "Won" or "Archived" in Jobber
Sequence reaches Text 4 and sends (completes naturally)

n8n Workflow: Sequence 1

See n8n Workflow Architecture section for full node diagram.

Sequence 2: Survey Hot Lead

Target: Existing Trimlight customers who responded "Yes, I'd love a free quote" on the customer experience survey Tone: Warm, VIP, relationship-first — these people already know and trust Jack Goal: Convert warm interest into a booked quote call

Critical note: These are Trimlight customers. AZ Palm Tree Lights and Trimlight must remain brand-separate in all systems. This sequence comes from the AZ Palm Tree Lights Quo number (480) 631-7754, not from any Trimlight-associated number. The message copy acknowledges the Trimlight relationship conversationally but does not present itself as Trimlight outreach.

Message Templates

Text 1 — Immediate (within 5 minutes of survey submission)

Hey [first_name], it's Jack! Thanks for filling out the survey — excited you're interested in palm tree lighting. Since you're already a Trimlight customer, I'd love to give you a VIP quote. When works for a quick call?

Character count: ~212 (1 SMS segment) Send as: SMS

Text 2 — +24 hours (if no reply)

Hey [first_name], just bumping this up. As a thank you for the survey, you've got $100 off any new lighting project. Want to lock that in?

Character count: ~141 (1 SMS segment) Send as: SMS Note: The $100 discount is a real commitment — log the offer in Jobber notes when this message sends so Jack can honor it

Text 3 — +4 days from survey submission (if no reply)

Here's what palm tree lighting looks like on a home similar to yours. I can put together a custom quote in about 10 minutes. Just text back a good time! - Jack

Send as: MMS with before/after photo See Photo Recommendations section — use upscale Scottsdale/PV home photos that match Trimlight customer demographics

Exit Conditions:

Lead replies to any message
Sequence reaches Text 3 and sends (completes naturally)

Sequence 3: Past Lead Reactivation

Target: Leads who were quoted 30+ days ago but never booked (pulled from Jobber "Quoted" status, age 30+ days) Tone: Low-pressure check-in, acknowledges time has passed Goal: Revive dormant interest, create urgency with booking window and discount Trigger: Manual — run this quarterly or at the start of booking season (August/September push recommended)

Message Templates

Text 1 — Day 1

Hey [first_name], it's Jack from AZ Palm Tree Lights. We chatted [time_reference] about lighting up your palms. Wanted to check in — is that still something you're interested in? We've got some new install photos I'd love to share.

Character count: ~220 (1 SMS segment) Send as: SMS Note: [time_reference] = "a while back" as default, or "in [month_name]" if quote date is known and within the current year

Text 2 — +3 days (if no reply)

No worries if the timing wasn't right before. We're booking installs for [next_month] now. If you want to get on the schedule before peak season, just text back and I'll send over an updated quote.

Character count: ~189 (1 SMS segment) Send as: SMS Note: [next_month] = calendar month name one month ahead of send date

Text 3 — +7 days from Text 1 (if no reply)

Last one from me, [first_name]! Just wanted to let you know we're offering $200 off for customers who book before [cutoff_date]. If you're interested, I'm here. If not, totally understand. - Jack

Character count: ~187 (1 SMS segment) Send as: SMS Note: [cutoff_date] = set manually when triggering the sequence batch, typically end of current month or 2 weeks out. Log the offer date in the tracking sheet.

Exit Conditions:

Lead replies to any message
Sequence reaches Text 3 and sends (completes naturally)

Enrollment process: Jack or ops team pulls a Jobber report of "Quoted" jobs older than 30 days, exports a CSV with name + phone, uploads to n8n manual trigger or pastes into a Google Sheet intake tab. Workflow reads the sheet and enrolls each contact.

Sequence 4: Post-Install Review Request

Target: Completed Jobber jobs (status = "Completed") Tone: Friendly, grateful, assumes success Goal: Get Google reviews, plant referral seed Trigger: Jobber webhook fires on job status change to "Completed" — n8n listens and waits 3 days before sending Text 1

Message Templates

Text 1 — +3 days post-install

Hey [first_name], it's Jack! Hope you're loving the new palm tree lighting. How's everything looking? Any questions about the app or color settings?

Character count: ~148 (1 SMS segment) Send as: SMS Purpose: Opens the loop with a service check-in before asking for a review. Gives the customer a chance to raise any issues privately.

Text 2 — +7 days post-install

Send regardless of whether Text 1 received a reply. If they replied positively, this flows naturally. If no reply, the tone still works.

So glad to hear it! Would you mind leaving us a quick Google review? It really helps other homeowners find us. Here's the link: [google_review_url]. Thanks so much!

Character count: ~183 (1 SMS segment) Send as: SMS Note: [google_review_url] = AZ Palm Tree Lights Google Business Profile review link. Get the short link from Google Business Profile dashboard: https://business.google.com > Your Profile > Ask for reviews > copy the short URL. Hardcode this into the n8n workflow config once.

Exception: If Text 1 received a complaint or issue reply, DO NOT auto-send Text 2. The n8n workflow must check for a negative-sentiment flag set manually by Jack, or simply pause and send Jack a notification to handle manually.

Text 3 — +14 days post-install

Hey [first_name], one more thing — if you know anyone who'd love their palms lit up, we offer a $100 referral bonus for every friend who books. Just have them mention your name!

Character count: ~175 (1 SMS segment) Send as: SMS

Exit Conditions:

Sequence reaches Text 3 and sends (completes naturally)
Jack flags the contact as "issue reported" — halts sequence and notifies Jack

n8n Workflow Architecture

Global Nodes (Shared Across All Sequences)

Reply Listener Workflow (always-on, separate workflow)

[Quo Inbound Webhook]
        |
[Extract phone number + message body]
        |
[Google Sheets: lookup phone in "Active Enrollments" tab]
        |
[If phone found in active enrollment]
        |
        ├── [Update enrollment row: replied = TRUE, reply_text = message, reply_time = now]
        |
        └── [Jobber API: add tag "quo-replied" to contact]

This webhook URL gets registered once in Quo's settings (Settings > Integrations > Webhooks > Inbound SMS).

Sequence 1 Workflow

Trigger options (pick the applicable one per source):

Meta Lead Ads: Use Meta's n8n node or a Zapier-style webhook from Meta Lead Center
Google Ads: Jobber webhook on new contact creation (tagged "google-ads")
Website form: Fillout webhook on form submission

[Trigger: New lead webhook]
        |
[Extract: first_name, phone, source, neighborhood/zip]
        |
[Normalize phone to E.164 format: +1XXXXXXXXXX]
        |
[Check Google Sheet "Active Enrollments": is phone already enrolled?]
        |
   [If already enrolled] ──> [Stop — do not double-enroll]
        |
   [If new]
        |
[Google Sheets: Add row to Active Enrollments]
  {phone, first_name, sequence=1, enrolled_at, source, replied=FALSE}
        |
[Quo API: Send Text 1 — immediate]
        |
[Google Sheets: Log to Sent Log tab]
        |
[Wait 4 hours]
        |
[Check Active Enrollments: replied = TRUE?]
        |
   [If replied] ──> [Exit sequence, log exit_reason="replied", done]
        |
   [If not replied]
        |
[Resolve today/tomorrow variable based on AZ time]
        |
[Quo API: Send Text 2]
        |
[Google Sheets: Log to Sent Log tab]
        |
[Wait until 24 hours from enrollment time]
        |
[Check Active Enrollments: replied = TRUE?]
        |
   [If replied] ──> [Exit sequence]
        |
   [If not replied]
        |
[Resolve neighborhood variable from zip code]
        |
[Quo API: Send Text 3 — MMS with photo URL]
        |
[Google Sheets: Log to Sent Log tab]
        |
[Wait until 72 hours from enrollment time]
        |
[Check Active Enrollments: replied = TRUE?]
        |
   [If replied] ──> [Exit sequence]
        |
   [If not replied]
        |
[Quo API: Send Text 4]
        |
[Google Sheets: Log to Sent Log tab]
        |
[Update Active Enrollments: status = "completed"]

n8n nodes used: Webhook, Code (for phone normalization), Google Sheets (read + write), HTTP Request (Quo API), Wait, IF

Sequence 2 Workflow

[Trigger: Fillout webhook — survey submission]
        |
[Check: Q2 answer = "Yes, I'd love a free quote"]
        |
   [If No] ──> [Stop — not a hot lead]
        |
   [If Yes]
        |
[Extract: first_name, phone, email]
        |
[Normalize phone]
        |
[Google Sheets: Add row to Active Enrollments]
  {phone, first_name, sequence=2, enrolled_at, source="cx-survey", replied=FALSE}
        |
[Quo API: Send Text 1 — immediate]
        |
[Jobber API: Add note to contact — "$100 discount offered via survey sequence, [date]"]
        |
[Google Sheets: Log]
        |
[Wait 24 hours]
        |
[Check replied]
        |
   [If replied] ──> [Exit]
        |
   [If not replied]
        |
[Quo API: Send Text 2]
        |
[Google Sheets: Log]
        |
[Wait until 96 hours from enrollment]
        |
[Check replied]
        |
   [If replied] ──> [Exit]
        |
   [If not replied]
        |
[Quo API: Send Text 3 — MMS with before/after photo]
        |
[Google Sheets: Log]
        |
[Update enrollment: status = "completed"]

Sequence 3 Workflow

[Trigger: Manual — Google Sheets intake tab populated by Jack/ops]
   OR
[Trigger: Scheduled — weekly, reads Jobber "Quoted" jobs > 30 days old via Jobber API]
        |
[For each contact in batch]
        |
[Check Active Enrollments: already enrolled in Seq 3?]
        |
   [If yes] ──> [Skip]
        |
   [If no]
        |
[Normalize phone]
        |
[Resolve time_reference from quote_date field]
        |
[Google Sheets: Add enrollment row]
  {phone, first_name, sequence=3, enrolled_at, jobber_quote_id, replied=FALSE}
        |
[Quo API: Send Text 1]
        |
[Google Sheets: Log]
        |
[Wait 3 days]
        |
[Check replied]
        |
   [If replied] ──> [Exit]
        |
   [If not replied]
        |
[Resolve next_month variable]
        |
[Quo API: Send Text 2]
        |
[Google Sheets: Log]
        |
[Wait until 7 days from enrollment]
        |
[Check replied]
        |
   [If replied] ──> [Exit]
        |
   [If not replied]
        |
[Read cutoff_date from workflow config variable]
        |
[Quo API: Send Text 3]
        |
[Google Sheets: Log]
        |
[Update enrollment: status = "completed"]

Workflow config variable: Set cutoff_date as a static variable in the workflow before running a batch. Update it each time you run a reactivation campaign.

Sequence 4 Workflow

[Trigger: Jobber webhook — job status changed to "Completed"]
        |
[Extract: job_id, client_first_name, client_phone, completed_at]
        |
[Check: is this an AZ Palm Tree Lights job? (check job tag or assigned brand field)]
        |
   [If Trimlight job] ──> [Stop — wrong brand]
        |
   [If AZPTL job]
        |
[Normalize phone]
        |
[Google Sheets: Add enrollment row]
  {phone, first_name, sequence=4, enrolled_at, jobber_job_id, replied=FALSE, issue_flag=FALSE}
        |
[Wait 3 days from completed_at]
        |
[Quo API: Send Text 1 — check-in]
        |
[Google Sheets: Log]
        |
[Wait until 7 days from completed_at]
        |
[Check issue_flag = TRUE (set manually by Jack if complaint received)]
        |
   [If issue_flag = TRUE]
        |
        └── [Send Slack/email notification to Jack: "Manual follow-up needed for [name]"]
            [Stop sequence]
        |
   [If issue_flag = FALSE]
        |
[Quo API: Send Text 2 — review request with Google URL]
        |
[Google Sheets: Log]
        |
[Wait until 14 days from completed_at]
        |
[Check issue_flag]
        |
   [If issue_flag = TRUE] ──> [Stop]
        |
   [If FALSE]
        |
[Quo API: Send Text 3 — referral offer]
        |
[Google Sheets: Log]
        |
[Update enrollment: status = "completed"]

Quo API Integration Notes

API Access

Quo (OpenPhone) provides a REST API. Documentation: https://www.openphone.com/docs/api-reference

Base URL: https://api.openphone.com/v1

Authentication: Bearer token (API key from Quo workspace settings) Settings > My Account > API Keys > Create API Key

Required scopes: messages:read, messages:write, phone-numbers:read

Sending an SMS via API

POST https://api.openphone.com/v1/messages
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

{
  "from": "+14806317754",
  "to": ["+1XXXXXXXXXX"],
  "content": "Hey [first_name], it's Jack..."
}

Sending an MMS via API

POST https://api.openphone.com/v1/messages
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

{
  "from": "+14806317754",
  "to": ["+1XXXXXXXXXX"],
  "content": "Here's one we just finished in Scottsdale...",
  "mediaUrls": ["https://azpalmtreelights.com/assets/install-1.jpg"]
}

Note: Media must be served via a publicly accessible HTTPS URL. Host photos on AZ Palm Tree Lights website or an S3 bucket. Do not use Google Drive links — they are not reliably served as raw media.

Inbound Message Webhook

Settings > Integrations > Webhooks > Add Webhook

URL: your n8n webhook
Events: message.received

Quo will POST a JSON payload for every inbound SMS/MMS. The Reply Listener workflow receives this.

Checking for Quo API Limitations

Rate limit: Check current docs — typically 10 requests/second
Message scheduling: Quo API does not natively schedule messages. All scheduling is handled by n8n Wait nodes.
Quo's built-in sequences (if available in your plan): Quo offers "Auto Replies" and some flow features in the app. However, for multi-step sequences with conditional logic and Jobber integration, n8n is the right layer. Do not try to run these in Quo's native tools — they won't support the exit conditions.

Fallback: Manual Process (if API isn't available on current plan)

If Jack's Quo plan does not include API access, the fallback is:

n8n handles all timing, delay, and exit-condition logic
Instead of calling the Quo API directly, n8n sends Jack a notification (email or Slack DM) with the pre-filled message text and the recipient's phone number
Jack copies the message and sends it manually from the Quo app
Jack manually logs the reply in the Google Sheet (or a simple Tally form)

This is slower but still systematizes the process. Upgrade to a Quo plan with API access as soon as volume justifies it.

Google Sheets Tracking

Workbook Structure

File name: AZ Palm Tree Lights — Quo Sequence Tracking Location: Google Drive, in the AZ Palm Tree Lights folder

Tab 1: Active Enrollments

Tracks every contact currently in a sequence.

Column	Type	Notes
phone	Text	E.164 format (+1XXXXXXXXXX) — primary key
first_name	Text
sequence	Number	1, 2, 3, or 4
enrolled_at	Timestamp	ISO 8601
source	Text	meta, google, website, cx-survey, manual, jobber-complete
replied	Boolean	TRUE/FALSE — updated by Reply Listener workflow
reply_text	Text	First reply message body
reply_time	Timestamp
issue_flag	Boolean	For Seq 4 — Jack sets manually if complaint
status	Text	active, completed, exited-reply, exited-manual
jobber_contact_id	Text	For linking back to Jobber
jobber_job_id	Text	Seq 4 only

Tab 2: Sent Log

Append-only log of every message sent.

Column	Type	Notes
sent_at	Timestamp
phone	Text
first_name	Text
sequence	Number
step	Number	1, 2, 3, or 4
message_type	Text	sms or mms
message_preview	Text	First 80 chars of message
quo_message_id	Text	From Quo API response
status	Text	sent, failed

Tab 3: Reply Log

All inbound replies captured by the Reply Listener workflow.

Column	Type	Notes
received_at	Timestamp
phone	Text
first_name	Text
sequence	Number	Active sequence at time of reply
step_when_replied	Number	Which step they had received
reply_text	Text	Full message body
converted	Boolean	Did this lead become a booked job? — fill in manually
notes	Text	Jack's notes

Tab 4: Campaign Summary (Auto-calculated)

Use COUNTIF/QUERY formulas to summarize:

Metric	Formula approach
Enrollments by sequence	COUNTIF(Active Enrollments!C:C, "1")
Reply rate by sequence	Replies / Enrollments
Conversion rate	Converted / Enrollments
Avg messages sent before reply	AVERAGEIF on Sent Log
Discount offers outstanding	COUNTIF sent log for Seq 2 Text 2 + Seq 3 Text 3

Tab 5: Seq 3 Intake

Used to batch-enroll reactivation leads manually.

Column	Notes
first_name
phone	Raw format OK — n8n normalizes
quote_date	From Jobber
jobber_quote_id
neighborhood	Scottsdale / PV / Arcadia / Other
processed	n8n marks TRUE after enrollment

Jack or ops pastes Jobber CSV export here. The Sequence 3 workflow polls this tab on a schedule.

TCPA Compliance Notes

Important: This section is informational, not legal advice. Consult an attorney familiar with TCPA if you have questions.

The Core Rule

The Telephone Consumer Protection Act (TCPA) requires prior express written consent before sending marketing texts using an autodialer or automated system. Violations carry statutory damages of $500–$1,500 per message.

Sequence Classification

Sequence	Classification	Consent Requirement
Seq 1 (New Lead — inbound)	Transactional/informational — the lead contacted you first	Implied consent via inbound inquiry. Still best practice to include opt-out.
Seq 2 (CX Survey)	Marketing — reaching out to existing customers	Need prior consent. The survey form must include a consent checkbox.
Seq 3 (Reactivation)	Marketing — outbound to cold leads	Need prior written consent captured at original lead form.
Seq 4 (Post-Install)	Mixed — part service (app questions), part marketing (review, referral)	Text 1 is transactional. Texts 2–3 are marketing. Consent from service agreement/intake form covers this for existing customers.

Consent Capture Recommendations

Website form / Meta Lead Ad / Google Ads landing page: Add checkbox: "I agree to receive text messages from AZ Palm Tree Lights about my inquiry and related offers. Message and data rates may apply. Reply STOP to opt out."
CX Survey (Fillout): Add consent language above the phone field: "By providing your number, you consent to receive text messages from AZ Palm Tree Lights. Reply STOP to unsubscribe."
Jobber intake / service agreement: Add a checkbox to the client intake form or quote acceptance confirming text consent.

Required Opt-Out Mechanism

Every sequence must honor STOP replies. The Reply Listener workflow should:

Detect if the inbound message body is exactly "STOP", "UNSUBSCRIBE", "CANCEL", "QUIT", or "END" (case-insensitive)
If detected: mark the contact opted_out = TRUE in the Active Enrollments sheet, exit all active sequences for that number, and log to an Opt-Out tab
Never send further messages to opted-out numbers

Quo may handle STOP replies automatically at the platform level — verify this in your Quo settings. Even if Quo handles it, maintain your own opt-out list in Google Sheets as a backup.

Recommended Footer (optional for shorter texts)

For any message where character count allows, append: "Reply STOP to opt out."

Time-of-Day Rules

Under TCPA, marketing texts should only be sent between 8 AM and 9 PM in the recipient's local time zone. All recipients are in Arizona (MST, no daylight saving). n8n Wait nodes should check the send time and delay until 8 AM AZ time if a scheduled message would otherwise send outside that window.

AZ time: UTC-7 year-round (Arizona does not observe DST, except the Navajo Nation).

Template Variables Reference

Required for All Sequences

Variable	Source	Notes
`[first_name]`	Lead form / Jobber contact	Required — do not send if missing. Use "there" as fallback only for Seq 1 Text 1.
`phone` (recipient)	Lead form / Jobber contact	Must be a US mobile number. Landlines cannot receive SMS. Normalize to E.164.

Sequence-Specific Variables

Variable	Sequence	Source	Fallback
`[today/tomorrow]`	Seq 1 Text 2	n8n time node (AZ time)	"soon"
`[neighborhood]`	Seq 1 Text 3	Lead zip code lookup table	"Scottsdale"
`[time_reference]`	Seq 3 Text 1	Jobber quote_date	"a while back"
`[next_month]`	Seq 3 Text 2	n8n date node (+1 month)	"next month"
`[cutoff_date]`	Seq 3 Text 3	Workflow config variable	Set before each campaign run
`[google_review_url]`	Seq 4 Text 2	Static — hardcoded once	No fallback — must be set

Zip Code to Neighborhood Mapping (for Seq 1 Text 3)

Build a small lookup table in Google Sheets or as a JSON object in n8n:

85250, 85251, 85252, 85253, 85254, 85255, 85257, 85258, 85259, 85260, 85261, 85262, 85266, 85268 → "Scottsdale"
85253 → "Paradise Valley"
85018, 85012, 85016 → "Arcadia"
default → "Scottsdale"

Performance Metrics & Targets

Sequence 1: New Lead

Metric	Target	Notes
Reply rate (any step)	30–40%	Industry average for warm inbound SMS is 25–45%
Reply rate within Text 1	15–25%	Speed of first text is the biggest driver
Conversion to booked call	20–30% of enrollments
Conversion to booked job	10–15% of enrollments	Depends on quote-to-close rate
Best performing step	Text 1	60–70% of all replies will come on Text 1

Key lever: Text 1 must send within 2 minutes. Every minute of delay reduces reply probability significantly. If n8n can't guarantee 2-minute delivery, build in a Slack alert to Jack for immediate manual backup.

Sequence 2: Survey Hot Lead

Metric	Target	Notes
Reply rate	40–55%	These are warm, existing customers — expect higher engagement
Conversion to booked quote	30–40%
$100 discount redemption rate	Track in Google Sheet	Log every time Jack honors this offer

Sequence 3: Past Lead Reactivation

Metric	Target	Notes
Reply rate	15–25%	Cold-er — lower expectations
Conversion to booked job	5–10% of batch	Even 5% reactivation is high ROI
$200 discount redemption rate	Track separately	Note the cost per acquisition

Run timing recommendation: Launch Seq 3 batches in August (before peak season) and in February (post-season, catch anyone who deferred).

Sequence 4: Post-Install

Metric	Target	Notes
Google review conversion	20–35%	Average review request → review rate via SMS is 15–30%
Referral leads generated	1 per 10 completions	Track referral source in Jobber
Net Promoter Signal (positive reply to Text 1)	70%+	High positive rate validates install quality

Overall Tracking Cadence

Weekly: Review Sent Log and Reply Log in Google Sheets. Jack should scan reply quality.
Monthly: Update Campaign Summary tab. Check conversion rates per sequence.
Quarterly: Review message copy. Update neighborhood photos, adjust discount amounts if needed, refresh the reactivation batch.

Photo & Media Recommendations

General Guidelines

Format: JPEG for all install photos (smaller file size, faster MMS delivery)
Resolution: 1200x900px minimum, 1600x1200px ideal (4:3 ratio works well for mobile)
File size: Under 500KB per image for reliable MMS delivery across all carriers
Hosting: Serve from azpalmtreelights.com/assets/mms/ or a dedicated S3 bucket. Never use Google Drive, Dropbox, or iCloud links — they redirect and may not render as inline images.
Naming convention: seq1-text3-scottsdale-palms-01.jpg, seq2-text3-pv-before-after.jpg, etc.
Test before launch: Send the MMS to your own phone and two others (Android + iPhone) before activating a sequence.

Sequence 1, Text 3 — Recent Install Photo

Goal: Show aspirational output. Make the lead picture their own home.

Use a photo of a finished install on an upscale home exterior — similar architectural style to Scottsdale/PV properties
Photo taken at dusk or twilight — the lighting looks most dramatic with a dark sky but visible house structure
Include 3–5 lit palms if possible
Avoid photos with cars, visible street numbers, or identifiable faces
Swap photo seasonally: December photo should feel warm/festive, June photo should feel cool and luxurious
Recommended: Have 3–5 different photos ready and rotate them monthly. This prevents repeat contacts from seeing the same image and keeps the content fresh.

Sequence 2, Text 3 — Before/After for Trimlight Customers

Goal: Show transformation. These are homeowners who understand what exterior lighting does for a home.

True before/after split or two-photo sequence (some MMS clients handle two images — test this)
"Before" should be daytime or poorly lit nighttime shot of a house with palms
"After" should be the same home (or very similar) with palm tree lighting active
Homes in the $1M–$3M range aesthetically — this matches Trimlight customer demographic
Lighting color should be warm white or neutral — not overly colorful, which can feel less premium

Sequence 4 — No Photos Needed

Texts in Seq 4 are about relationship and service, not sales. Keep them SMS-only. Adding photos can make it feel like marketing rather than a genuine check-in. The only exception would be if a future iteration includes a "here's what your install looks like in our portfolio" message.

Photo Library Setup

Create a shared Google Drive folder: AZ Palm Tree Lights / MMS Photo Library

Structure:

MMS Photo Library/
├── seq1-new-lead/
│   ├── scottsdale-twilight-01.jpg
│   ├── scottsdale-twilight-02.jpg
│   └── pv-twilight-01.jpg
├── seq2-survey/
│   ├── before-after-01.jpg
│   └── before-after-02.jpg
└── archive/
    └── (retired photos)

In each n8n workflow, reference the photo URLs as workflow-level variables so they can be updated without touching the workflow logic.

Setup Checklist

Before activating any sequence, verify the following:

Quo API key obtained and stored in n8n credentials manager
Quo inbound webhook URL registered in Quo settings, pointing to your n8n webhook
Google Sheets workbook created with all five tabs
Google Sheets connected to n8n via service account credentials
Jobber webhook for "job status changed to Completed" registered, pointing to n8n
Google review link for AZ Palm Tree Lights confirmed and tested
All MMS photos uploaded, sized, and served over HTTPS
Photo URLs added as variables in each relevant n8n workflow
Time-of-day guard (8 AM–9 PM AZ time) added to all Wait nodes
STOP detection logic added to Reply Listener workflow
Consent language added to website form, Meta lead form, and CX survey
Test run completed: each sequence triggered manually with a test phone number
Jack reviewed all message copy and approved
Discount amounts confirmed ($100 for Seq 2, $200 for Seq 3) and logged in Jobber notes process
Cutoff date variable set for Seq 3 before first batch run

Part of your Outdoor Vibes asset library — yours to keep and run.

— Andrew

Quo Follow-Up Sequences

Table of Contents

Overview & Architecture

System Map

Reply Detection Strategy

Sequence 1: New Lead

Message Templates

Sequence 2: Survey Hot Lead

Message Templates

Sequence 3: Past Lead Reactivation

Message Templates

Sequence 4: Post-Install Review Request

Message Templates

n8n Workflow Architecture

Global Nodes (Shared Across All Sequences)

Sequence 1 Workflow

Sequence 2 Workflow

Sequence 3 Workflow

Sequence 4 Workflow

Quo API Integration Notes

API Access

Sending an SMS via API

Sending an MMS via API

Inbound Message Webhook

Checking for Quo API Limitations

Fallback: Manual Process (if API isn't available on current plan)

Google Sheets Tracking

Workbook Structure

Tab 1: Active Enrollments

Tab 2: Sent Log

Tab 3: Reply Log

Tab 4: Campaign Summary (Auto-calculated)

Tab 5: Seq 3 Intake

TCPA Compliance Notes

The Core Rule

Sequence Classification

Consent Capture Recommendations

Required Opt-Out Mechanism

Recommended Footer (optional for shorter texts)

Time-of-Day Rules

Template Variables Reference

Required for All Sequences

Sequence-Specific Variables

Zip Code to Neighborhood Mapping (for Seq 1 Text 3)

Performance Metrics & Targets

Sequence 1: New Lead

Sequence 2: Survey Hot Lead

Sequence 3: Past Lead Reactivation

Sequence 4: Post-Install

Overall Tracking Cadence

Photo & Media Recommendations

General Guidelines

Sequence 1, Text 3 — Recent Install Photo

Sequence 2, Text 3 — Before/After for Trimlight Customers

Sequence 4 — No Photos Needed

Photo Library Setup

Setup Checklist