Skip to main content

Prospecting Outreach Email Templates

Purpose: Ready-to-use email templates for the GHL Prospecting outreach cadence. All templates are plain text (no HTML formatting, no image headers) and use GHL merge fields for personalization.

Sending Channel: Lead Connector only. Never send prospecting emails via Google Workspace. See Prospecting Email Outreach Strategy for rationale.


How to Use These Templates​

  1. Select the right template based on the prospect's audit findings (see selection guide below)
  2. Personalize -- replace bracketed placeholders [like this] with specific findings from the audit report
  3. Verify merge fields -- {{contact.first_name}} and {{contact.company_name}} must exist on the contact record
  4. Send via Lead Connector from the prospect's record in GHL
  5. Log the send -- GHL does this automatically when sent from the platform

Template Selection Guide​

These are the touches of an email-first cadence. The first email hands over the report; every later touch builds on that delivered value. A call, when it happens, is a warm follow-up to the report, not the opener. Touch numbers below refer to the outreach cadence.

TemplateWhen to UseCadence touch
First Email - Offer (Template 20)Default first email, when the contact has a rating of 4.0+ and 10 to 150 reviews. Sent by 02.send first email. Carries the report link and the Results-First offer. The email-only version: callers do not trigger sends (see Template 20)First email
First Email - Audit Only (Template 19)The fallback first email, when the contact has no rating or review count. Sent by 02.send first emailFirst email
After Call - Report and Offer (Template 21)A call reached the prospect and they gave an email or asked for the report. Archived: callers do not send it—
After Voicemail - Report and Offer (Template 22)Was the paired email for a voicemail. Archived: nothing is sent after a voicemail—
Audit-First Cold Intro (Template 8)A manual touch 1 when an operator is sending by hand and already has a finding. No longer the automated openerTouch 1 (manual)
Review Response Cold Intro (Template 9)Touch 1 of the Review Response Play, when the finding is unanswered Google reviewsTouch 1, day 0
Review Response Follow-Up, Video (Template 10)Touch 2 of the same play. Carries the demo video instead of a calendar linkTouch 2, day 3
Review Engine Cold Intro (Template 11)Touch 1 of Bucket 1, when the finding is too few Google reviews rather than unanswered ones. Touch 2 is Template 15Touch 1, day 0
Missed Call Cold Intro (Template 12)Touch 1 of Bucket 3, when the number cannot receive texts or there is no after-hours pathTouch 1, day 0
Contact Path Cold Intro (Template 13)Touch 1 of Bucket 4, when there is no form and no chat on the siteTouch 1, day 0
Online Booking Cold Intro (Template 14)Touch 1 of Bucket 5, when an appointment-shaped trade has no schedulerTouch 1, day 0
Audit Delivery (Template 7)A call or voicemail preceded the email and promised the report (the call-first path, still valid when a call happened first)Within 30 min of that call or voicemail
Cold Intro -- General Pain Points (1)Alternate touch 1 when the report should not go out yet (audit too weak to hand over, or being refreshed); describes findings, asks for a meetingTouch 1 (alternate)
Website Performance Focus (2)Same as Template 1; website-led findingsTouch 1 (alternate)
Reputation / Reviews Focus (3)Same as Template 1; review-led findingsTouch 1 (alternate)
Audit Walkthrough Follow-Up, Video (Template 15)Default touch 2 for every bucket. Carries the report-walkthrough video instead of a calendar askTouch 2, day 3
Audit Open Follow-Up (Template 16)Inserted touch for engaged prospects only. Fires off the prospecting-audit-email-opened tag, one business day later. Asks for a reply, carries no linkInserted, ~day 1-2
Follow-Up 1 (4)Fallback touch 2, used only while the walkthrough video does not yet existTouch 2, day 3
Follow-Up 2 / Final Touch (5)No response by day 10Touch 4, day 10
Re-Engagement (6)60-90 days after the cadence ends, audit refreshed firstTouch 5, day 60-90
Nine-word re-activationAlternative to Template 6. See belowTouch 5

Handing over the report is the default. The audit-first posture works because the prospect gets the value before any ask. Template 8 gives the report link in the first email; the cold-intro variants (1-3) hold it back and are the exception, not the rule. If a call promised the report to a prospect with no email on file, the caller takes the address with the S1 close and adds prospecting-values-added, and the first email goes by rule.

Signature rule. Every template signs Rohit, whoever operates the send. The sub-account sends under his name and the emails say "I run Symphony Core", so an operator substituting their own name makes the first line false. The signature is not a placeholder.

Consistency rule. The email must lead with the same finding used on the call, recorded in Audit Finding Used. Two different findings across two touches reads as a mail merge, which is exactly the impression the whole approach exists to avoid.

Nine-word re-activation (touch 6 alternative)​

A reactivation tool, never a first touch. Subject line is the prospect's first name. No signature block, no links, no company name in the body.

Subject: {{contact.first_name}}

Still worth fixing how you show up on Google?

Use this instead of Template 6 when the prospect never responded at all. Use Template 6 when they engaged once and then went quiet.

Rule: Choose ONE cold intro template (Template 1, 2, or 3) based on the strongest audit finding. Do not send multiple cold intro variants to the same prospect.


Template 1: Cold Intro -- General Pain Points​

Use when: Audit reveals 2+ areas with clear gaps (e.g., weak GBP + low review count + missing listings)

Subject line: Quick question about {{contact.company_name}}'s online presence

Hi `{{contact.first_name}}`,

I was looking into `{{contact.company_name}}`'s online presence and noticed a couple of things that might be costing you customers:

- [Finding 1 from audit -- be specific, e.g., "Your Google Business Profile is missing 4 of the recommended photo categories"]
- [Finding 2 from audit -- e.g., "I found inconsistent business information across 3 major directories"]

These are the kinds of issues that quietly push potential customers to competitors -- not because your service is worse, but because they can't find you as easily.

I help local businesses like yours fix exactly this. Would a quick 15-minute call be worth your time to see what's possible?

Here's my calendar if you'd like to pick a time: https://symphonycore.com/schedule-my-demo

Rohit
Symphony Core LLC

Personalization notes:

  • Replace both [Finding] placeholders with real audit data
  • Be specific -- "4 of the recommended photo categories" is better than "missing photos"
  • Do not reference scores or percentages the prospect can't verify themselves

Template 2: Website Performance Focus​

Use when: Website Performance score is below 60%, or site has clear technical issues (no SSL, poor mobile experience, very slow load times)

Subject line: {{contact.company_name}}'s website might be turning visitors away

Hi `{{contact.first_name}}`,

I took a look at `{{contact.company_name}}`'s website and wanted to share something that might be affecting your business.

[Describe the specific issue -- e.g., "Your site is taking over 6 seconds to load on mobile. Google's research shows that 53% of mobile visitors leave a site that takes longer than 3 seconds."]

[Optional second finding -- e.g., "I also noticed the site doesn't have an SSL certificate, which means visitors see a 'Not Secure' warning in their browser."]

The good news is that these are fixable. I work with local businesses on exactly these kinds of improvements.

Would it be worth 15 minutes to walk through what I found? You can grab a time here: https://symphonycore.com/schedule-my-demo

Rohit
Symphony Core LLC

Personalization notes:

  • Use specific numbers (load time in seconds, not just "slow")
  • Reference the business impact (lost visitors, search ranking, trust signals)
  • Only include the SSL finding if it's actually missing -- this is easy for the prospect to verify

Template 3: Reputation / Reviews Focus​

Use when: Unresponded Google reviews, response rate below 50%, review count significantly below competitors, or declining rating trend

Subject line: A quick note about {{contact.company_name}}'s reviews

Hi `{{contact.first_name}}`,

I was reading through `{{contact.company_name}}`'s Google reviews and noticed something that might be an easy win for you.

[Describe the specific finding -- e.g., "You have 12 Google reviews, but 7 of them don't have an owner response. Responding to reviews -- even the positive ones -- signals to both Google and potential customers that you're engaged and care about feedback."]

[Optional second finding -- e.g., "Your nearest competitor has 45 reviews with a 4.7 rating. Closing that gap is very doable with a simple review request process."]

I help businesses set up systems that make review management automatic -- requests go out after each job, and you get notified when a new review comes in so you can respond quickly.

Interested in seeing how it works? Here's a link to book a quick call: https://symphonycore.com/schedule-my-demo

Rohit
Symphony Core LLC

Personalization notes:

  • Actual review counts and response numbers are verifiable -- be accurate
  • Competitor comparisons are powerful but must be factual
  • Never criticize the prospect's existing reviews -- frame as opportunity, not failure

Template 4: Follow-Up 1​

Use when: No response 3 days after the initial email

Subject line: Re: [Original subject line]

Hi `{{contact.first_name}}`,

Just circling back on my note from a few days ago about `{{contact.company_name}}`'s online presence.

I know you're busy running your business -- that's exactly why I think a quick conversation could be valuable. The issues I flagged are the kind that compound over time if left unaddressed.

If 15 minutes works for you, here's my calendar: https://symphonycore.com/schedule-my-demo

Either way, no pressure. Happy to answer any questions by email if that's easier.

Rohit
Symphony Core LLC

Personalization notes:

  • Keep it short -- this is a nudge, not a re-pitch
  • Reference "my note from a few days ago" to connect to the original email
  • Reply to the original thread (same subject line with "Re:") so it appears as a conversation

Template 5: Follow-Up 2 / Final Touch​

Use when: No response 7 days after the initial email (4 days after Follow-Up 1)

Subject line: Re: [Original subject line]

Hi `{{contact.first_name}}`,

This will be my last note on this -- I don't want to fill up your inbox.

If the timing isn't right, I completely understand. The findings I shared about `{{contact.company_name}}` aren't going anywhere, and I'm happy to revisit whenever it makes sense for you.

If you'd like to connect down the road, my calendar link still works: https://symphonycore.com/schedule-my-demo

Wishing you and the team a great [season/month].

Rohit
Symphony Core LLC

Personalization notes:

  • This is a graceful close -- no hard sell
  • "This will be my last note" signals respect for their time
  • Leave the door open without being pushy
  • Replace [season/month] with the current season or month

Template 6: Re-Engagement​

Use when: 60-90 days have passed since the initial cadence ended with no response

Subject line: Checking in -- {{contact.company_name}}

Hi `{{contact.first_name}}`,

I reached out a couple of months ago about some things I noticed with `{{contact.company_name}}`'s online presence. Wanted to check in and see if anything has changed on your end.

[If you refreshed the report, reference one updated finding -- e.g., "I took another look and noticed you've added some new Google reviews since we last connected -- great to see. There are still a few areas where I think you could be getting more visibility, though."]

If you've got 15 minutes, I'd love to walk you through what I see: https://symphonycore.com/schedule-my-demo

No worries if the timing still isn't right. Just wanted to make sure the offer was still on the table.

Rohit
Symphony Core LLC

Personalization notes:

  • Refresh the audit report before sending this email (see Audit Accuracy SOP)
  • If the prospect has improved in any area, acknowledge it -- shows you're paying attention
  • Keep the tone casual and low-pressure

Template 7: Audit Delivery​

Use when: Touch 2, within 30 minutes of a voicemail (or after a live conversation where the report was promised). This is the canonical audit_delivery template in the cadence config.

Subject line: The report I mentioned -- {{contact.company_name}}

Hi `{{contact.first_name}}`,

Just left you a voicemail. As promised, here is the full report on how `{{contact.company_name}}` shows up online:

`{{contact.audit_pdf_url}}`

It covers your Google presence, reviews, website and local search, and now also whether AI assistants like ChatGPT can find and read your business. The part worth two minutes of your time is `{{contact.audit_finding_used}}`.

No form to fill out, no meeting required -- the report is yours either way.

If you would like a hand with any of it, just reply to this email.

Rohit
Symphony Core LLC

Personalization notes:

  • One link only, and it is the report link -- no calendar link in this email. The promise was "no meeting required"; honoring it literally is what makes the reply ask credible. Later touches carry the calendar. The rule protects that promise rather than the link count, and the one email that does not make it may carry both.
  • {{contact.audit_pdf_url}} is the platform's shareable audit-report link, stored on the contact (existing field, folder C-021.Prospecting). Open it in a private browser window before first use to confirm it loads without login.
  • Write audit_finding_used as a short noun phrase that reads inside a sentence -- e.g., "how you rank on Google Maps searches for plumbers near Southbury" -- because the call task and this email both merge it verbatim (the consistency rule above).
  • If the email follows a live conversation instead of a voicemail, swap the first line: "Good speaking with you just now."
  • For a booked or warm lead, use the Marketing Audit Delivery Email Template instead -- that sibling assumes a scheduled meeting and an attached, operator-corrected PDF.

Template 8: Audit-First Cold Intro​

Use when: Touch 1 of the email-first cadence, the default opener. No call precedes it; the email itself hands over the report.

Subject line: I put together a report on {{contact.company_name}}

Hi `{{contact.first_name}}`,

I run Symphony Core, a marketing systems company in Connecticut. While looking at businesses around `{{contact.city}}`, I put together a report on how `{{contact.company_name}}` shows up online, and I figured you should have it:

`{{contact.audit_pdf_url}}`

It covers your Google presence, reviews, website and local search, and now also whether AI assistants like ChatGPT can find and read your business. The part worth two minutes of your time is `{{contact.audit_finding_used}}`.

There is no form and nothing to sign up for. The report is yours either way.

If you would like a hand with any of it, just reply to this email.

Rohit
Symphony Core LLC

Personalization notes:

  • One link only, and it is the report link. No calendar link in this email; the reply ask is the CTA, and later touches carry the calendar. Same rule as Template 7, including its stated exception.
  • {{contact.city}} merges from the contact's native City field, populated by the prospecting agent on every record. The geo-anchor is what signals a real local business rather than a scam, so it stays; it anchors on Connecticut and on the prospect's own town, never on a town SC does not occupy.
  • Open {{contact.audit_pdf_url}} in a private browser window before sending to confirm it loads without login.
  • Write audit_finding_used as a short noun phrase that reads inside a sentence (the consistency rule): any later call or email leads with the same finding.
  • Verify First name holds a person's name, not the business name, before sending -- the prospecting agent writes the business name into it.

Template 9: Review Response Cold Intro​

Use when: Touch 1 of the Review Response Play. The finding is unanswered Google reviews, hand-verified on the live profile before sending.

Subject line: Your last few Google reviews

Hi `{{contact.first_name}}`,

I run Symphony Core, a marketing systems company in Connecticut. I was looking at businesses around `{{contact.city}}` and put together a report on how `{{contact.company_name}}` shows up online:

`{{contact.audit_pdf_url}}`

The part worth two minutes: `{{contact.audit_finding_used}}`.

That matters more than it sounds. People read the owner's response before they read the review, and silence reads as nobody being home.

There is no form and nothing to sign up for. The report is yours either way.

If you would like a hand with it, please just reply.

Rohit
Symphony Core LLC

Personalization notes:

  • The finding must be hand-counted on the live Google Business Profile before sending. Never take the response-rate number from the audit widget: recent responses may not be reflected yet, and an owner who replied last week will check in twenty seconds and conclude the whole report is careless. The gate is in the Review Response Play.
  • Write audit_finding_used as a short noun phrase carrying the real number, so it reads inside the sentence. For example: four reviews from the last three months with no reply, the most recent from August 12.
  • One link only, and it is the report link. The reply ask is the CTA.
  • {{contact.city}} merges from the contact's native City field. Nothing to fill by hand.
  • Verify First name holds a person's name, not the business name.

Template 10: Review Response Follow-Up, Video​

Use when: Touch 2 (day 3) of the Review Response Play, when Template 9 got no response.

Subject line: Re: Your last few Google reviews

This template replaces the calendar ask with a video. Asking for 15 minutes from someone who has not replied is the weakest CTA in the cadence. A 90-second video costs the prospect less than a meeting and shows the fix instead of describing it.

Hi `{{contact.first_name}}`,

Following up on the report I sent a few days ago.

Rather than write out how the fix works, here is ninety seconds of it running on a live account:

[video link]

It answers every new review within 48 hours, in your voice, with anything under three stars held for a person to write. Once your Google profile is connected it runs on its own.

If it looks useful, please reply and I will set it up on yours.

Rohit
Symphony Core LLC

Personalization notes:

  • One link only, and it is the video. No calendar link, matching the touch-1 posture.
  • The video is the single generic asset in the Review Response Demo Video Script. It is not re-recorded per prospect.
  • Reply to the original thread so it reads as a conversation.
  • Do not state the guarantee here. It has terms, and an email cannot carry them. The guarantee belongs in touch 4 and on the call. See SC Review Response Guarantee.
  • No promotion line in this email. Touch 2 carries the mechanism, and the discount would compete with it.

Template 11: Review Engine Cold Intro​

Use when: Touch 1 of Bucket 1. The prospect is rated 4.0 or better and has fewer than 15 Google reviews, both hand-counted on the live profile before sending.

Subject line: The reviews on your site and on Google

Hi `{{contact.first_name}}`,

I run Symphony Core, a marketing systems company in Connecticut. I was looking at businesses around `{{contact.city}}` and put together a report on how `{{contact.company_name}}` shows up online:

`{{contact.audit_pdf_url}}`

The part worth two minutes: `{{contact.audit_finding_used}}`.

That gap is usually a timing problem rather than a service problem. The customer who would happily leave a review is pleased when the job ends and busy by that evening, so the ask has to reach them inside that window, and it has to reach all of them rather than the few someone remembers to ask.

There is no form and nothing to sign up for. The report is yours either way.

If you would like a hand with it, please just reply.

Rohit
Symphony Core LLC

Personalization notes:

  • Count the rating and the reviews by hand on the live Google Business Profile before sending. The report's Reputation score is a triage input and never appears in the email. Step 4 of the Slotting Checklist.
  • Write audit_finding_used as a short noun phrase carrying the real count plus the single strongest contrast. Two shapes work, and the stronger one wins:
    • Against their own site, when they are visibly already trying: one Google review, against five written testimonials on your own homepage
    • Against the local pack, when the competitive gap is the starker number: eleven Google reviews, against sixty and eighty for the two firms above you on the map
  • Never imply filtering. SC asks every customer and every customer goes to Google. The sentence about reaching all of them rather than a chosen few is doing that work deliberately, and it must not be softened into a screening step. Policy is in the Manual Google Review Request SOP.
  • Do not promise a number of reviews, a rating, or a ranking. This bucket carries no guarantee. The only guarantee SC has is scoped to Bucket 2 and is still in draft.
  • One link only, and it is the report link. The reply ask is the CTA.
  • {{contact.city}} merges from the contact's native City field. Nothing to fill by hand.
  • Verify First name holds a person's name, and that the person still runs the business. Founder names outlive founders; step 8 of the slotting checklist exists because of it.

Template 12: Missed Call Cold Intro​

Use when: Touch 1 of Bucket 3. The listed number is not SMS-capable, or there is no after-hours path, and the trade is emergency-shaped.

Subject line: When someone texts your business number

Hi `{{contact.first_name}}`,

I run Symphony Core, a marketing systems company in Connecticut. I was looking at businesses around `{{contact.city}}` and put together a report on how `{{contact.company_name}}` shows up online:

`{{contact.audit_pdf_url}}`

The part worth two minutes: `{{contact.audit_finding_used}}`.

Somebody who texts that number gets no reply and no error message, so they move to the next name on the list and you never find out it happened. The fix is not answering more calls. It is that a missed call sends a text back on its own within a few seconds, so the conversation starts while they are still deciding who to use.

Worth saying plainly, because it affects whether this is any use to you: carrier registration for business texting takes a week or two. It is not a same-day change.

There is no form and nothing to sign up for. The report is yours either way.

If you would like a hand with it, please just reply.

Rohit
Symphony Core LLC

Personalization notes:

  • The registration paragraph stays in. A2P approval genuinely takes 7-10 business days and an owner who is told "tomorrow" and waits two weeks has been misled at the first touch. Naming the delay before they ask is also the most credible sentence in the email.
  • Never estimate what they are losing. No "you are missing 40% of your leads." It is unknowable, and an owner who knows his own call volume will catch it.
  • Write audit_finding_used as what you observed, not what you inferred: a business number that cannot receive text messages, or no after-hours path except voicemail, on a trade people call at night.
  • One link only, and it is the report link. The reply ask is the CTA.
  • {{contact.city}} merges from the contact's native City field. Nothing to fill by hand.
  • This bucket also maps to Text Back Pro at $99/month as a standalone entry, which is the lowest-friction thing SC sells. Do not put pricing in this email; it belongs on the reply.

Template 13: Contact Path Cold Intro​

Use when: Touch 1 of Bucket 4. No contact form and no chat widget anywhere on the site, verified by hand rather than from the report's technology detection.

Subject line: The only way to reach you is a phone call

Hi `{{contact.first_name}}`,

I run Symphony Core, a marketing systems company in Connecticut. I was looking at businesses around `{{contact.city}}` and put together a report on how `{{contact.company_name}}` shows up online:

`{{contact.audit_pdf_url}}`

The part worth two minutes: `{{contact.audit_finding_used}}`.

Somebody reading your site at nine in the evening, ready to hire, has one option, which is to remember to call you tomorrow. Some of them do. A short form and a chat box, both landing in one inbox, mean an enquiry that arrives out of hours is still sitting there in the morning with a name and a number attached to it.

Nothing to sign up for, and the report is yours either way.

If you would like a hand with it, please just reply.

Rohit
Symphony Core LLC

Personalization notes:

  • The closing line is deliberately not the usual one. Every other template says "there is no form and nothing to sign up for." In an email whose entire subject is the absence of a form, that sentence reads as a joke. Do not paste the standard version back in.
  • Verify by hand, on the live site, after waiting ten seconds. The report's chat-widget and scheduling detection produces false negatives on delayed loads and embedded iframes. A button that only scrolls the page is not a form.
  • Never estimate lost enquiries. "Some of them do" is deliberate understatement and it is the honest shape of the claim.
  • Write audit_finding_used as the observation: no contact form and no chat on the site, so every enquiry has to start with a phone call.
  • One link only, and it is the report link. {{contact.city}} merges from the native City field.

Template 14: Online Booking Cold Intro​

Use when: Touch 1 of Bucket 5. No scheduler on the site, and the trade is appointment-shaped rather than emergency-shaped.

Subject line: Booking a job on your website

Hi `{{contact.first_name}}`,

I run Symphony Core, a marketing systems company in Connecticut. I was looking at businesses around `{{contact.city}}` and put together a report on how `{{contact.company_name}}` shows up online:

`{{contact.audit_pdf_url}}`

The part worth two minutes: `{{contact.audit_finding_used}}`.

For work that gets scheduled rather than dispatched, the phone call is the part customers put off, and putting it off is how a job quietly becomes somebody else's. Letting them pick a slot themselves moves that decision outside your business hours, and it tends to fill the awkward gaps in a week that are hard to fill by phone.

There is no form and nothing to sign up for. The report is yours either way.

If you would like a hand with it, please just reply.

Rohit
Symphony Core LLC

Personalization notes:

  • Check the trade shape first. This is the weakest of the five openers and it fails outright on emergency work, where nobody books a burst pipe three days out. The trade shape table decides it, and emergency beats appointment when a trade is both.
  • Do not claim online booking suits every business. Plenty of owners have decided against it on purpose. If they say so on the reply, that is a fair answer and not an objection to overcome.
  • Write audit_finding_used as the observation: no way to book on the site, so every appointment starts with a call during business hours.
  • One link only, and it is the report link. {{contact.city}} merges from the native City field.

Template 15: Audit Walkthrough Follow-Up, Video​

Use when: Touch 2, day 3, for every bucket, when touch 1 got no response. This is the default follow-up; Template 4 is the fallback only while the video does not exist.

Subject line: Re: [touch-1 subject line]

Hi `{{contact.first_name}}`,

Following up on the report I sent a few days ago.

Rather than ask you to read twelve pages, here is ninety seconds on how to read it, and on checking the one thing in it I pointed you at:

[video link]

It covers which parts of that report come straight from Google and are worth acting on, and which parts I would ignore. The number I mentioned is one you can check yourself in about twenty seconds.

If it holds up and you would like a hand with it, please just reply.

Rohit
Symphony Core LLC

Personalization notes:

  • Reply to the original thread so it reads as a conversation. The subject is the touch-1 subject with Re: in front, whichever bucket that was.
  • One link only, and it is the video. No calendar link, matching the touch-1 posture.
  • The video is the single generic asset in the Audit Report Walkthrough Video Script. It is not re-recorded per prospect, and it is the same link for every bucket.
  • Do not restate the finding. Touch 1 already named it and the consistency rule holds. This email points at the method for checking it, which is the part touch 1 could not carry.
  • No guarantee, no promotion line. Touch 2 carries the mechanism; the discount would compete with it and the guarantee has terms an email cannot state.
  • Until the video is recorded this template cannot be sent. Use Template 4 at touch 2 in the meantime. Do not send a mail containing [video link].
  • Bucket 2 may use Template 10 instead once that video exists, since a fix demo beats a report walkthrough for a prospect who already understands the problem. Until then this template covers B2 as well.

Template 16: Audit Open Follow-Up​

Use when: a prospect picks up prospecting-audit-email-opened from workflow WF-3. Send one business day after the tag, and only to prospects still inside the initial cadence. It replaces nothing: it is an inserted touch for the engaged subset, and it counts against the three-email cap like any other.

Subject line: Re: Running an audit on how {{contact.company_name}} shows up online

16a — when First name is populated:

Hi `{{contact.first_name}}`,

Did that report reach you alright?

No agenda here. If you opened it and it was useless, tell me and I will stop. If one of the sections looked worth a conversation, tell me which and I will answer it by email, no meeting needed.

Either reply is genuinely useful to me.

Rohit
Symphony Core LLC

16b — when First name is empty: identical, opening Hello, instead. Matches the WF-1 branch pair in the C-021 spec §3.1, so this template survives being automated later without a rewrite.

Personalization notes:

  • ⚠️ Never state or imply that they opened it. Not "I saw you opened it", not "noticed you had a look". The open event fires on Apple Mail image prefetch with no human involved, and the report link's view count is a single shared counter across every contact, so the claim is unsupported. It is also the fastest way to make a stranger feel watched. Same never-say as call scripts §10. "Did that reach you alright?" carries the same intent and is true either way.
  • Reply to the original thread. The subject is the touch-1 subject with Re: in front.
  • No links at all. Not the report, not the calendar. The prospect already has the report link, and an engaged prospect being asked to click again is a step backwards — the ask here is a reply, and every link competes with it.
  • No finding. Touch 1 carried no finding either (nobody had read the report yet), so there is nothing to be consistent with. Do not invent one to fill the space.
  • No promotion, no guarantee. Both compete with the reply ask.
  • "If it was useless, tell me and I will stop" is doing real work. It is a permission-to-decline that reliably produces replies, and a no is a genuinely useful outcome: it ends the cadence cleanly rather than burning two more touches.
  • Automation-safe as written. No bracketed placeholders, no video link, and every merge resolves from a field the branch guarantees. Unlike Templates 10 and 15, this one can go into the platform today.

Template 17: Touch 1 Report Announcement (superseded)​

Superseded 2026-10-30 by Template 19. The announce-then-deliver pair is retired: a promise in one email and the artifact in another is a step that can fail silently, and three prospects were left holding the promise. Kept for reference and for the archived platform asset; do not send it.

Use when: touch 1, day 0, of the automated cadence. Sent by WF-1 with no human in the loop. It announces the report; it does not carry it.

Platform: C-021.Prospecting - Touch 1 - Report Announcement (6ac895462991e7ab4260cb44), folder C-021.Prospecting. One template, not a pair — the greeting variant was archived on 2026-10-09 when the Default Text fallback replaced it.

Subject line: Running an audit on how {{contact.company_name}} shows up online Pre-header: Your Google presence, reviews, website and local search

Hi `{{contact.first_name}}`,

I run Symphony Core, a marketing systems company in Connecticut. I am running an audit on how `{{contact.company_name}}` shows up online: your Google presence, reviews, website, and local search visibility.

I will send the report across in my next email. It takes about two minutes to skim, there is nothing to sign up for, and it is yours either way.

If you would rather just talk it through, pick a time here:

https://symphonycore.com/meet-with-rohit

Best,

Rohit
Symphony Core LLC

Personalization notes:

  • "I am running an audit… I will send the report" is deliberate, and it under-promises. Earlier versions of this note said the opposite — that the email must claim the report already exists, because the workflow generates it before sending. The guard now added to WF-1 (audit_pdf_url is not empty) means the email cannot send unless the report exists, so the risk the old rule guarded against, promising something that failed to generate, is closed at the node rather than in the copy. Present tense is the safe direction: it claims less than is true, never more.
  • One link, and it is the calendar. There is no report link yet; that is the point. The only first-party thing worth clicking is the booking page, which keeps the first cold touch free of the third-party prod.analyzemy.business host entirely.
  • No finding, and none is possible. Nobody has read the report when this sends. Template 18 and the bucket templates carry the finding, which is the whole reason the touch was split.
  • No PS, no promotion. Touch 1 is an introduction; a discount competes with it and the PS belongs on the email that delivers something.
  • One greeting, with a fallback. {{contact.first_name}} carries Default Text there, set per insertion in the template editor, so a contact with no first name reads "Hi there," rather than "Hi ,". This replaced the paired-template arrangement entirely. ⚠️ The default is set in the UI and this document cannot verify it. If it is ever cleared, or lost to an API write that does not preserve it, the majority of sends render "Hi ," — 12 of the 13 most recent enrolments had no first name. Check it before any batch.

Template 18: Touch 2 Report Delivery (superseded)​

Superseded 2026-10-30 by Template 19. Kept for reference and for the archived platform asset; do not send it. Note its map paragraph was also withdrawn from Template 19 on 2026-10-30 — the local heat-map fails to generate for a large share of prospects, so the claim is not reliably true. Do not copy that paragraph forward.

Use when: touch 2, day 3, for a prospect nobody has slotted. A slotted prospect gets their bucket's template instead (9, 11-14), which carries the hand-counted finding.

Platform: C-021.Prospecting - Touch 2 - Report Delivery (6a227d3d696b0d6ccba3a695), since rewritten as Template 19 and renamed First Email - Audit Only. Renamed 2026-10-09 from C-021.Prospecting - No Bucket - Audit First: the old name described a cold intro the template no longer holds, and an operator looking for touch 2 in the folder could not find it. Its greeting twin (6ab104c77270d29cad9ce8ae) is archived.

Subject line: The audit on {{contact.company_name}} Pre-header: Your Google presence, reviews, website and local search

Hi `{{contact.first_name}}`,

Here it is, as promised:

`{{trigger_link.nKZdNo5w0Cynuk1FiVGt}}`

It covers your Google presence, reviews, website, and local search. The part most people skip to is the map section. It shows which businesses Google ranks around you for what you do, with their ratings and review counts. That is who Google currently treats as your competition, and it is usually not who you would expect.

If anything in it looks worth fixing, pick a time below, or reply to this email and tell me what works.

https://symphonycore.com/meet-with-rohit

Best,

Rohit
Symphony Core LLC

Personalization notes:

  • "Here it is, as promised" only works if touch 1 went out. This template must never be sent as a first touch. If a prospect somehow reaches day 3 without the announcement, send Template 8 instead.
  • The map paragraph is a verified claim, not a flourish ✅ 2026-10-09. The widget report does carry a ranked competitor table with ratings and review counts, and the grid centres on the prospect's own address — confirmed by reading the heatmap data for an Illinois prospect (grid 779 miles from Southbury, competitors all in Crystal Lake) and a Connecticut one. The C-021 spec §3.1 carries the evidence. If the Prospect AI agent's anchor ever changes the grid centre, this paragraph comes out the same day.
  • The claim is true of the widget report, which is what the link opens. It is not true of the SC-authored PDF, which drops Local Rank Tracker by Production PRD §7. Never make this claim in an email that attaches the PDF.
  • Two links, report and booking, under the CTA exception in the outreach strategy. This email makes no "no meeting required" promise, so a booking link contradicts nothing.
  • No {{contact.audit_finding_used}}. It is empty on an unattended send, and removing it is what makes this template automation-safe enough for WF-1's safety-net branch to send it.

Template 19: Audit Report Delivery — the single send​

The fallback first email, from 2026-11-05. Platform name C-021.Prospecting - First Email - Audit Only. 02.send first email sends it when a verified contact has no rating or review count, so the offer email's opener can't be written. Unchanged copy: it makes no claim the report can't back. It was not sent between 2026-11-04 and 2026-11-05.

Use when: was the only automated prospecting email, sent the moment a prospect was tagged and the report link confirmed present. Replaced Templates 17 and 18, which split one message into a promise and a delivery.

Platform: C-021.Prospecting - First Email - Audit Only (6a227d3d696b0d6ccba3a695). Templates 17 and 18 are archived, not deleted.

Subject line: The audit on {{contact.company_name}} Pre-header: Your Google presence, reviews, website and local search

Hi `{{contact.first_name}}`,

I run Symphony Core, a marketing systems company in Connecticut. I put together a report on how `{{contact.company_name}}` shows up online, and I figured you should have it:

`{{trigger_link.nKZdNo5w0Cynuk1FiVGt}}`

It covers how you show up on Google, what your reviews look like next to the other businesses in your trade, and what your website does with the visitors it already gets. It now also shows whether AI assistants like ChatGPT can find and read your business. It takes about two minutes to skim, there is nothing to sign up for, and it is yours either way.

If anything in it looks worth fixing, reply and tell me which part and I will tell you what it would take. Or pick a time here:

https://symphonycore.com/meet-with-rohit

Best,

Rohit
Symphony Core LLC

Why it reads this way

  • It opens by saying who is writing and why, because with no prior email there is nothing to refer back to. Template 18's "Here it is, as promised" only worked as the second half of a pair, and sending it cold would have confused every recipient.
  • The report link sits in the third line. It is the only reason the email exists.
  • The ask is a reply first, the calendar second. The old pair drew zero replies on every send, while 26.9% of announcement recipients clicked through to the booking page and nobody booked. An email that asks for a sentence is answerable by someone who will not surrender a calendar slot to a stranger.
  • No PS. The AUDIT50 promotion expired 2026-10-31, and the scripts doc bars promotions from calls so a discount never arrives before value. Email now matches.
  • No {{contact.audit_finding_used}}. It is empty on an unattended send. That omission is what makes this template safe to send without a human.
  • Two links, report and booking, under the CTA exception in the outreach strategy.
  • It promises nothing the report cannot always deliver. Templates 18 and 19 originally told the reader to skip to the map section. The local heat-map fails to generate for a large share of prospects — some audits return 0%, some return nothing at all, and as of 2026-10-30 there is no reliable fix. Pointing every recipient at a section that is frequently empty is the fastest way to make a cold email look automated. The paragraph now names only what the report always contains.
  • The AI search line names a section, not a finding. It says the report covers AI search, not what the assistants say and not a score, so it holds for every report that carries the section. The section is a vendor Labs feature with general release about 2026-12-01: apply the line in the platform only once a C-021 report is confirmed to show it (AV2-01 in the launch backlog).
  • This is a copy guard, not a fix. The audit's heat-map failure is a platform problem and is tracked separately. Until it is resolved, the workflow must also guard on it: an audit with no heat-map is a report-quality failure, and the prospect is parked and flagged rather than sent a thin report.

It was sent immediately, not overnight. The gap existed so an announcement could be honoured later; with one email there is nothing to honour. Template 20 keeps S3 alive the same way.

⚠️ Gated on the trigger-link test. Across ten sends of Template 18 the report link was clicked zero times, and per-contact link resolution has never been tested. Do not send this at volume until one click from a real inbox is confirmed to open that contact's own report.


Template 20: Offer Before the Call (Email 1A)​

⚠️ Two platform templates since 2026-11-05. Callers do not trigger sends, so the live one is C-021.Prospecting - First Email - Offer (6aeae5d70dbfa27d811e861a), the email-only version. It differs from the copy below in three places:

  • Subject: A short report on {{contact.company_name}}
  • The call paragraph ("Someone from my team will give you a quick call…") is replaced by: "If it's worth twenty minutes to talk it through, pick a time that suits you here: symphonycore.com/meet-with-rohit" and "Or just reply to this email and I'll get back to you myself."
  • Who sends it: 02.send first email sends it by the routing rule in the C-021 workflow spec, once the report is verified. No call follows.

The copy below is the caller version, kept as C-021.Prospecting - First Email - Offer Before Call (6aec77d25ca36a018021b4f0, archived). It goes with S3, "send, then call", which stays retired with a caller in seat. If S3 is ever restored, unarchive it and point 02's Offer branch at it. Nothing needs re-typing.

Use when: the caller is about to dial a prospect with an email on file, inside calling hours. The caller fills rating, reviewCount and trade from the live Google profile and adds the tag prospecting-values-added; workflow C-021.Prospecting - 02.send email sends this, and the caller dials 5 to 10 minutes later (call situation S3). The default first email for every prospect who passes the pre-dial check. Never send it by hand after a call or a voicemail: it promises a call in the next few minutes.

Platform: C-021.Prospecting - First Email - Offer Before Call (6aec77d25ca36a018021b4f0, archived), plain text, folder C-021.Prospecting.

Subject line: Quick note before we call, {{contact.first_name}} Pre-header: {{contact.rating}} stars from {{contact.reviewcount}} reviews, and the calls that slip past

Hi `{{contact.first_name}}`,

`{{contact.company_name}}` has `{{contact.rating}}` stars from `{{contact.reviewcount}}` Google reviews, so people clearly like the work. Where shops like yours usually lose jobs is the call that rings out while everyone is on site. That customer rings the next number on the list.

We help with that in two ways. You get a business number that rings your phone, and any call you can't answer gets a text back within a minute. After each job, your customer gets a short text asking for a Google review.

It's $99 to start, and nothing monthly until it gets you a job or gets your reviews moving.

I also put together a short report on how `{{contact.company_name}}` shows up online. It's yours either way:

`{{trigger_link.nKZdNo5w0Cynuk1FiVGt}}`

Someone from my team will give you a quick call in the next few minutes. If now isn't a good time, just reply with one that suits you better.

Best,

Rohit
Symphony Core LLC

Why it reads this way

  • It opens on something true and good about them. The rating line is only true at 4.0 and above, which is why the send is guarded on it.
  • The offer is in the email's own words, once. "Nothing monthly until it gets you a job or gets your reviews moving" is the whole of the Results-First offer a prospect sees in writing before the walkthrough. The time window and the terms are not in the copy; they are in the signed terms.
  • trade is not merged. The dropdown values ("Other", "General Contractor") do not read as a sentence.
  • The report is kept, but second. It is the free value, and the call opens on one finding from it.

The send guard, as specified for 02.send email: audit_pdf_url is not empty, rating ≥ 4, reviewCount ≥ 10 and ≤ 150, email is not empty, and the contact does not carry prospecting-offer-email-sent, which the workflow adds after sending. When the guard fails, the assigned user gets an internal notification instead. ⚠️ Workflow definitions cannot be read over the API, so the guard as built is unverified.


Template 21: Offer After the Call (Email 1B)​

Use when: a call reached the prospect and they gave an email address, or asked for the report (the S1 close, and the "send me something" answer). Sent by hand within the hour. Replaces the report-only snippet for anyone inside the offer.

Platform: C-021.Prospecting - After Call - Report and Offer (6aeb11c4647be026b0f2ff51, archived; callers do not send it), plain text, folder C-021.Prospecting.

Subject line: The report on {{contact.company_name}}, as promised Pre-header: The report, and the short version of what we talked about

Hi `{{contact.first_name}}`,

Thanks for the time on the phone today. Here's the report on how `{{contact.company_name}}` shows up online, as promised:

`{{trigger_link.nKZdNo5w0Cynuk1FiVGt}}`

The short version of what we talked about: you get a business number that rings your phone, and any call you can't answer gets a text back within a minute. After each job, your customer gets a short text asking for a Google review.

It's $99 to start, and nothing monthly until it gets you a job or gets your reviews moving.

If it's worth twenty minutes, pick a time that suits you here: https://symphonycore.com/meet-with-rohit

Best,

Rohit
Symphony Core LLC

Before sending: a contact created during the call has no audit_pdf_url until the report is generated, and the link then resolves to nothing. Check the field first.


Template 22: Offer After a Voicemail (Email 1C)​

Use when: the paired email for a voicemail left on any call other than an S3 call (after an S3 voicemail, Email 1A is already the pairing). Sent by hand within thirty minutes of the voicemail.

Platform: C-021.Prospecting - After Voicemail - Report and Offer (6aeb11c9b1c356c16e4210ef, archived; callers do not send it), plain text, folder C-021.Prospecting.

Subject line: The report on {{contact.company_name}} Pre-header: We tried you today, so here's the report

Identical to Template 21 except two lines. The first line:

We tried you today and missed you, so here's the report on how `{{contact.company_name}}` shows up online:

and, because no conversation happened, the offer paragraph opens The short version of what we'd do about it: instead of The short version of what we talked about:.


Template Registry​

The cadence config in the Prospecting Outreach Automation PRD names templates by id. Those ids resolve here (PRD FR-013). When a template is added, renamed, or retired, update this table and the corresponding platform email template in the same change.

Cadence template idCanonical assetChannel
offer_before_callTemplate 20: Offer Before the Call, Email 1A (this doc)Email
offer_after_callTemplate 21: Offer After the Call, Email 1B (this doc)Email
offer_after_voicemailTemplate 22: Offer After a Voicemail, Email 1C (this doc)Email
audit_report_deliveryTemplate 19: Audit Report Delivery (this doc). Manual only since 2026-11-04Email
touch1_announcementTemplate 17 — superseded 2026-10-30, retained archived—
touch2_deliveryTemplate 18 — superseded 2026-10-30, retained archived—
audit_first_introTemplate 8: Audit-First Cold Intro (this doc), manual sends onlyEmail
review_response_introTemplate 9: Review Response Cold Intro (this doc)Email
review_response_followupTemplate 10: Review Response Follow-Up, Video (this doc)Email
review_engine_introTemplate 11: Review Engine Cold Intro (this doc)Email
missed_call_introTemplate 12: Missed Call Cold Intro (this doc)Email
contact_path_introTemplate 13: Contact Path Cold Intro (this doc)Email
booking_introTemplate 14: Online Booking Cold Intro (this doc)Email
audit_walkthrough_followupTemplate 15: Audit Walkthrough Follow-Up, Video (this doc)Email
opener_A / opener_B / opener_CCold Call Scripts, Section 3, Openers A / B / CSpoken
audit_deliveryTemplate 7: Audit Delivery (this doc)Email
followup_1Template 4: Follow-Up 1 (this doc)Email
followup_callCold Call Scripts, Section 3, S2: the follow-upSpoken
vm2Cold Call Scripts, Section 6, Voicemail 2. Its paired email is Template 22 for a prospect inside the offer, Template 4 otherwiseSpoken + email
audit_open_followupTemplate 16: Audit Open Follow-Up (this doc)Email
final_touchTemplate 5: Follow-Up 2 / Final TouchEmail
nine_word_reactivationNine-word re-activation (this doc, selection guide)Email

Touch 1's voicemail (Voicemail 1, Cold Call Scripts Section 6) carries no id in the config because it is part of the call touch, not a scheduled template.

Where these live in the platform​

Synced 2026-09-16. The touch-1 set exists as plain-text templates in the C-021.Prospecting email folder on the Symphony Core sub-account. Names are bucket-forward so they match the Prospect Bucket value the operator already has in front of them.

Registry idPlatform template
touch1_announcementC-021.Prospecting - Touch 1 - Report Announcement (6ac895462991e7ab4260cb44), archived
touch2_deliveryC-021.Prospecting - First Email - Audit Only (6a227d3d696b0d6ccba3a695)
audit_first_introNo platform template. The slot that held it was renamed and now holds Template 18
review_response_introC-021.Prospecting - Follow-up - B2 Review Response
review_engine_introC-021.Prospecting - Follow-up - B1 Review Engine
missed_call_introC-021.Prospecting - Follow-up - B3 Missed Calls
contact_path_introC-021.Prospecting - Follow-up - B4 No Contact Path
booking_introC-021.Prospecting - Follow-up - B5 No Booking
offer_before_callLive: C-021.Prospecting - First Email - Offer (6aeae5d70dbfa27d811e861a), the email-only version, sent by C-021.Prospecting - 02.send first email. Caller version: C-021.Prospecting - First Email - Offer Before Call (6aec77d25ca36a018021b4f0), archived
offer_after_callC-021.Prospecting - After Call - Report and Offer (6aeb11c4647be026b0f2ff51), archived
offer_after_voicemailC-021.Prospecting - After Voicemail - Report and Offer (6aeb11c9b1c356c16e4210ef), archived
audit_open_followupNot yet created. Automation-safe as written — build it as C-021.Prospecting - Audit Open Follow-Up when WF-3 gains a send node

review_response_followup and audit_walkthrough_followup are deliberately absent from the platform: both carry a video link that does not exist yet, and a template holding a broken placeholder is worse than no template.

Every prospecting email is now a saved template in this folder. Until 2026-10-09 the automated report delivery was composed inline on its workflow node, and this section said it never could be anything else, because the report link reached it through machinery a saved template could not reproduce. That stopped being true in September, when the body moved onto a trigger link and off the workflow action's output. Folder 6a227cefac3e7c57f95caaa0 now holds all nine.

The report link is a trigger link, not a raw URL. C-021.Prospecting - Audit Report (nKZdNo5w0Cynuk1FiVGt) redirects to {{contact.audit_pdf_url}}, so one branded link serves every contact their own report. That keeps an unfamiliar third-party report host out of a cold email and makes the click a workflow event. Templates 18 and the C-025 inbound delivery both use it; the six bucket templates merge {{contact.audit_pdf_url}} directly and are unaffected. ⚠️ One trigger link is shared between the cold prospecting lane and the inbound C-025 lane, which neither document flagged until now — a change to its destination moves both.

The naming rule now exists. It was authored on 2026-10-09 as GHL Naming Standard §6D, after this paragraph had spent a month recording that no rule existed and one would have to be written. Names are C-021.Prospecting - <scope> - <descriptor>, where scope is a bucket code for a bucket-specific email and a touch token for one that applies to every bucket. The six bucket templates already complied. ⚠️ The - no first name variant suffix the rule originally defined is now unused: per-insertion Default Text on {{contact.first_name}} handles the empty case inside a single template, so the greeting pairs were archived on 2026-10-09 and no template needs the suffix. The rule keeps it for any future variant that genuinely differs in one line only.


Manual vs Automated Sends​

These templates serve both modes:

  • Manual sends (today): hand-fill every [bracketed placeholder], verify merge fields on the contact, send via Lead Connector from the prospect's record.
  • Automated sends (per the C-024 workflow spec): the workflow merges only fields the cadence entry guard proves non-empty (first_name, company_name, audit_pdf_url, audit_finding_used). Only Template 7 and the nine-word re-activation are automation-safe as written. Template 15 carries a bracketed subject placeholder and the [video link], so it is manual-only until the video URL replaces the placeholder. Templates 8, 9 and 11 to 14 carry no bracketed placeholders at all and are automation-safe as written: every value merges from a field the agent populates; Templates 4 and 5 carry bracketed subject/closing placeholders (Re: [Original subject line], [season/month]) that need fixed-subject automation variants at build time; Templates 1-3 and 6 keep bracketed prose placeholders and remain manual-only.

Merge Field Reference​

Merge FieldSourceNotes
{{contact.first_name}}Contact recordMust exist on the contact; falls back to empty string
{{contact.company_name}}Contact recordMust exist on the contact; critical for all templates
{{contact.audit_pdf_url}}Contact custom field audit_pdf_url (existing, C-021.Prospecting)The shareable audit-report link. Templates 7, 8, 9 and 11. Cadence entry is guarded on it being non-empty
{{contact.rating}}Contact custom field rating (NUMERICAL, C-021.Prospecting)Template 20. Google star rating, filled by the caller from the live profile before the send
{{contact.reviewcount}}Contact custom field reviewCount (NUMERICAL, C-021.Prospecting)Template 20. Google review count, filled by the caller. The merge key is lowercase
{{contact.audit_finding_used}}Contact custom field audit_finding_usedShort noun phrase set at verification time; merged verbatim into the call task and Templates 7, 8, 9 and 11

Before sending: Verify every merged field is populated on the prospect's contact record in GHL. If any is missing, update the contact record first -- a blank merge is a broken email (the static-safe rule in the B-011 journey map).



Document History​

VersionDateChanges
2.122026-11-12The report gained an AI search visibility section. Templates 7 and 8 extend the covers line to name it, and Template 19 gains one sentence. All three name the section only, never what an assistant says or a score. Previous wording of the Template 7 and 8 line: "It covers your Google presence, reviews, website, and local search visibility." Platform copies change only after AV2-01 confirms C-021 reports carry the section
2.112026-11-10"While no one is calling" becomes "callers do not trigger sends": a caller is now in seat and the first email still goes by rule. Templates 21 and 22 stay archived; the selection-guide rule to send Template 7 after a call that promised the report now points to the S1 close. The never-say link follows the call scripts' new §10
2.102026-11-09The sending workflow's new name, 02.send first email, in the selection guide, the Template 19 and 20 banners and the registry
2.92026-11-05The platform templates are renamed First Email -, After Call -, Follow-up -, and the first email is chosen by a rule. Template 20 is now two platform templates: First Email - Offer (email-only, live) and First Email - Offer Before Call (caller version, archived). Template 19 becomes the fallback first email, First Email - Audit Only, sent when a contact has no rating or review count. Templates 21 and 22 are archived while no one is calling. Registry and selection guide follow
2.82026-11-05Email 1A goes email-only while no one is calling. The platform template was edited in place: new subject, the call promise replaced by the booking link and a reply invitation, and renamed Offer and Report. Template 20 keeps the caller copy, with a banner recording the live version and how to restore it
2.72026-11-04The first email now carries the Results-First offer, and the caller sends it. Template 20 (Email 1A) is sent by C-021.Prospecting - 02.send email when the caller adds prospecting-values-added, minutes before an S3 call; it merges rating and reviewCount, which join the merge-field reference. Templates 21 (1B, after a call, 6aeb11c4…) and 22 (1C, after a voicemail, 6aeb11c9…) carry the same offer for prospects who did not get 1A before the call. Template 19 is no longer sent automatically: prospecting-audit-verified now only generates the report. The selection guide's stale Template 17 and 18 rows are replaced, and the registry gains three ids
2.42026-10-09Copy fixes on both automated templates, and the greeting pairs are gone. Template 17's subject was an ungrammatical fragment, Put together a report on …, and is now Running an audit on how {{contact.company_name}} shows up online; the body opens "I am running an audit" rather than claiming the report is already done. The note demanding the opposite is rewritten: WF-1's new audit_pdf_url is not empty guard closes the risk that rule existed for, and present tense under-promises, which is the safe direction. Template 16's Re: subject tracks the new one — it is defined as the touch-1 subject and would otherwise have broken threading. Template 8's identical fragment is fixed separately and stays a distinct string. The hyphen used as a sentence dash is removed from both emails, per email-writing-style; a colon in 17, a full stop in 18. Template 18's platform template is renamed C-021.Prospecting - Touch 2 - Report Delivery — the old No Bucket - Audit First described a cold intro it no longer holds, and an operator looking for touch 2 could not find it in the folder. Both - no first name twins are archived: GHL's merge-field editor offers per-insertion Default Text, so one template with a there fallback replaces each pair. That also disproves the long-standing claim that the merge field has no default
2.32026-10-09The automated first touch splits into Template 17 (announce, day 0) and Template 18 (deliver, day 3), both live as saved templates. The claim that one prospecting email could never be a saved template is removed — it rested on a saved template being unable to resolve a workflow action output, which stopped applying in September when the body moved onto trigger link nKZdNo5w0Cynuk1FiVGt; C-025.Audit Lead Magnet - send email had been sending a saved template with that link the whole time. Template 8 is demoted to manual sends and loses its platform slot, which Template 18 now occupies. The map/competitor claim in Template 18 is carried with its verification: the heatmap grid centres on the prospect's own address, not the Prospect AI agent's 06488 anchor, confirmed against an Illinois prospect whose grid sits 779 miles from Southbury. Booking link moves to meet-with-rohit. An email-template naming rule exists for the first time (naming standard §6D), and the - no first name suffix is regularised. Also records a coupling neither document had flagged: the cold lane and the inbound C-025 lane share one trigger link. Trailing Document Information block corrected — it had read Version: 1.2 since August
2.22026-09-23Template 16, Audit Open Follow-Up, added for the engaged subset — it fires off the prospecting-audit-email-opened tag that workflow WF-3 now applies, one business day later. Two greeting variants matching the WF-1 branch pair, so it survives automation. It carries no links at all, including the calendar: the ask is a reply and every link competes with it. Registered in the selection guide and both registry tables. It is the first follow-up template that is automation-safe as written — Templates 10 and 15 are still held back by a video that does not exist. Also records the never-say inherited from the call scripts: do not tell a prospect they opened the report, because Apple Mail prefetch fires the event without a human and the link's view count is one shared counter
2.12026-09-18The automated report-delivery email now links through trigger link C-021.Prospecting - Audit Report rather than a raw report URL, so a cold email stops pointing at an unfamiliar third-party host. The other six templates merge {{contact.audit_pdf_url}} directly and are unchanged
2.02026-09-17Records the one prospecting email that is not a platform template: the C-021 workflow's automated report delivery merges a workflow action output, which a saved template cannot resolve, so it is composed inline on the email node and its copy is canon in the workflow spec. It is also the one email carrying a booking link beside the report link, under an exception now stated in the outreach strategy; the Template 7 and 8 notes point at it
1.92026-09-16Platform mapping recorded: the six touch-1 templates now exist in the C-021.Prospecting folder and match this document. Before the sync the live B1 and B2 each carried six deviations - a calendar link beside the report link, a report score quoted to the prospect, {{contact.trade}}, no geo-anchor, a pitch line absent from canon, and a truncated PS. Note for anyone editing these in the platform: GHL stores plain-text templates as HTML paragraphs, so newline characters do not survive an API write
1.82026-09-16[trade] removed from every template. It was a manual-entry field populated on 7 of 20 sampled records, in inconsistent free text ('land services', 'roofing and siding'), and it blocked a send when empty. The opener now reads "businesses around {{contact.city}}", which merges from the native City field - populated on 20 of 20. Consequence: Templates 8, 9 and 11 to 14 now carry no bracketed placeholders and are automation-safe as written. The trade field itself is not deleted; it belongs to the Meta lead form and stays
1.72026-09-11Added Template 15: Audit Walkthrough Follow-Up (audit_walkthrough_followup), the default touch 2 for every bucket. Replaces Template 4's calendar ask with the report-walkthrough video, on the same reasoning Template 10 already used: asking for fifteen minutes from someone who has not replied is the weakest CTA in the cadence. Template 4 demoted to the fallback until the video is recorded
1.62026-09-10Templates 12, 13 and 14 (missed_call_intro, contact_path_intro, booking_intro) complete the bucket set, so every bucket has a touch-1 asset and no operator has to improvise one. Signature rule added: every template signs Rohit, whoever operates the send, because the emails open "I run Symphony Core" and the account sends under his name. The 11 [Your First Name] placeholders that invited the wrong substitution are gone
1.52026-09-10Closed D-3: Template 8's geo-anchor no longer claims a Southbury office. It now anchors on Connecticut plus the prospect's own [town], matching Template 9. Added Template 11: Review Engine Cold Intro (review_engine_intro), touch 1 of Bucket 1 in the Prospecting Bucket Taxonomy - the finding is too few Google reviews rather than unanswered ones, which the Review Response Play previously disqualified with no alternative. Merge Field Reference corrected: audit_pdf_url and audit_finding_used are used by Templates 7, 8, 9 and 11, not Template 7 alone
1.42026-08-27Email-first cadence switch: added Template 8 Audit-First Cold Intro (default touch 1, hands over the report link, reply CTA, audit_first_intro registry id); selection guide re-framed email-first with Templates 1-3 as hold-the-report alternates; Template 7 repositioned for the call-preceded path
2.62026-10-30The map paragraph comes out of Template 19. It told every recipient to skip to the map section; the 2026-10-29 one-to-one records that the local heat-map fails to generate for most prospects contacted, with some audits returning 0% and some nothing at all. The email's strongest claim was one the report frequently could not honour, which is the fastest way to make a cold email look automated. Replaced with what the report always contains. Caught before the template was built in the platform, so nothing went out carrying it
2.52026-10-30Templates 17 and 18 merge into Template 19, one send. The pair promised a report in one email and delivered it in another; three prospects were left holding the promise with no report, which a single send makes impossible. The merged email opens by saying who is writing, carries the report link in the third line, and asks for a reply before the calendar — the old pair drew 26.9% click-through to the booking page, zero bookings and zero replies. Sent immediately rather than overnight, which keeps call situation S3 alive. Every AUDIT50 line is removed from every template, eight PS blocks and two prose variants: the promotion expires 2026-10-31 and calls already bar promotions, so email now matches
1.32026-08-27AUDIT50 promotion woven in (see sc-audit50-promo): Template 7 gains a link-free PS, Template 4 a closing incentive line, Template 5 the code. Nine-word re-activation deliberately untouched (the nine-word no-link format is the mechanism). Promo lines are removable on expiry
1.22026-08-22Added Template 7: Audit Delivery (the canonical audit_delivery asset -- link-based, honors the call's "no form, no meeting" promise), the Template Registry binding cadence template ids to assets, the Manual vs Automated Sends split, and audit_report_url / audit_finding_used merge fields. Cold-intro variants repositioned as email-only-prospect templates
1.12026-08-18Repositioned as the written touches of a call-first cadence. Selection guide now keyed to touch numbers rather than standalone days. Added the nine-word re-activation template and the finding-consistency rule
1.02026-03-02Initial version -- 6 email templates (3 cold intro variants, 2 follow-ups, 1 re-engagement)

Document Information

  • Version: 2.4
  • Created: 2026-03-02
  • Updated: 2026-10-09
  • Location: 03-sales/prospecting/prospecting-outreach-email-templates.md