# KAHAYA × Super Realty campaign handoff

Prepared 21 September 2026. Proposed implementation, not installed or sent.

## Deliverables

index.html: client review with desktop/mobile email previews and downloads.
super-realty.html: proposed email landing page, no lead capture.
emails/email-01.html to email-03.html: table-based HTML import drafts.
emails/email-01.txt to email-03.txt: matching plain-text drafts.
emails/preview-*.html: local browser previews, not CRM import files.
follow-up-copy.txt: two acknowledgements, SMS and gentle follow-up.

## Evidence and unresolved facts

Based on the 17 September meeting transcript, the supplied Matt Towner email version 2, existing brand guidelines, and the existing KAHAYA V2 design. Client-review drafts are not approved campaign copy. Matt must approve first-person statements and all three emails being signed by him. No current stock count, prices, yield, construction status or completion claim has been added. Existing documents conflict on construction progress, so the draft deliberately omits that claim. Confirm project details with Ginny.

The existing V2 form is demo-only. No new lead-routing connection, calendar integration or email deployment is represented as complete. Final film is not in the local asset library. Do not use a fake player. Add the approved film with captions and a transcript once provided.

## Configuration required

1. David/Julian provide access to the exact Super Realty GoHighLevel subaccount.
2. Confirm from-name, authenticated sending domain, from-address, monitored reply-to, company postal address, unsubscribe mechanism and tracking domain. The transcript's domain spelling is not configuration evidence.
3. Verify first-name, location and unsubscribe merge syntax in this account. Define a first-name fallback. Preview templates contain unresolved merge fields intentionally.
4. Replace the review landing-page URLs with the approved campaign destination before sending. Preserve UTM source=super_realty, medium=email, campaign=kahaya_intro and content=email_01/02/03. Replace the preview asset host if the production asset host differs.
5. Agree enquiry ownership, adviser notification recipients, business hours and booking destination. Use Super Realty routing; do not substitute the existing Zenvara WhatsApp route.
6. Configure applicable email/SMS consent and suppression rules. Sending infrastructure and legal/tax content require their own verification before launch.

## Nurture workflow

Entry: approved pilot cohort, marketing eligibility confirmed, no DND/opt-out/hard bounce, no active enquiry or sales conversation. Use a campaign enrolment marker to prevent duplicate entry.

Send email 1. Wait 7–10 days from each individual's first send. Re-check suppression, replies, enquiry and sales status. Send email 2 only if still eligible. Wait until day 18–24 after that individual's first send. Re-check conditions and send email 3 if eligible. End sequence; no indefinite repeat.

Global exit: unsubscribe, hard bounce, applicable DND, enquiry, booking, reply requiring a human response, active adviser conversation or sale. A click alone may add an interest tag; it must not be treated as consent, a booking or a form submission. Opens are supporting metrics only.

Pilot: proposed 5,000 eligible contacts. If the reported 2,000/day account limit is confirmed, first touch needs at least three sending days with no other traffic. Reserve capacity for acknowledgements, other campaigns and workflow sends. Verify provider/account limits and reputation rather than assuming an upgrade removes the restriction.

## Enquiry workflow

Capture: name, email, optional phone/country, villa interest, information/call preference, source, UTM data and applicable consent evidence. Reconcile existing contacts without discarding prior source history. Persist initial and latest source separately if supported.

On valid enquiry: exit nurture; create/update one opportunity without duplicates; assign the agreed Super Realty adviser; notify them; create a follow-up task; send the matching acknowledgement. Persist villa choice and request type. Do not claim a calendar booking until an actual booking event exists.

Optional SMS: only call requests with appropriate SMS consent and a usable phone number; respect contact hours and STOP suppression. Information-only requests must not automatically trigger SMS or calls.

No reply: proposed email after two business days, cancelled by reply, appointment, opt-out or active sales activity. Adviser response timing must be agreed, not promised in campaign copy.

## Tracking and QA

Report sent/delivered/bounced, unsubscribes, unique clicks, enquiries, call requests, appointments and active opportunities by email and cohort. Separate website events from CRM outcomes.

Before launch: approve copy and Matt attribution; verify all merge fields using seeded test contacts including missing names; send tests to Gmail/Outlook and mobile; verify unsubscribe and reply routing; test consent and source fields; test one contact through each enquiry branch; verify deduplication; verify stop-on-reply/enquiry/unsubscribe; confirm booking events; check every image and CTA; confirm the published landing page no longer uses demo-only capture.

## Deployment and rollback

This pack is an additive static campaign-review directory. It does not change the existing V2 home page. Retain it in the VPS source public directory for future builds and in the running app's public/dist-client locations for the current image. Remove only this directory to roll back the review addition. No CRM or outbound messaging changes occur.