> ## Documentation Index
> Fetch the complete documentation index at: https://docs.myfundingmachine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# GHL Nurture Without First Reply

> Operator runbook for updating the prospecting workflow so 24h and multi-day SMS/email follow-ups fire without waiting for an inbound reply.

# GHL Nurture Without First Reply

Funding Machine enrolls delivered leads into the GHL workflow **`1. New FM Prospecting Leads`**. Day-1 SMS/email is sent on enrollment. Follow-up branches must **not** wait for a contact reply before sending day-2+ messages.

## Why this is GHL-side

Convex only **enrolls** contacts via `addContactToWorkflow` during lead delivery ([`convex/prospecting/deliverLead.ts`](https://github.com/myfundingmachine/ghl-marketplace-app-fundingmachine/blob/main/convex/prospecting/deliverLead.ts)). Branch timing, wait steps, and reply gates live inside the GHL workflow builder in the outreach-team snapshot location.

## Update checklist

<Steps>
  <Step title="1. Open the template workflow">
    In the **outreach team** GHL location, open **Automation → Workflows → `1. New FM Prospecting Leads`**.
  </Step>

  <Step title="2. Remove reply gates on follow-up branches">
    For day-2, 24h, and 5-day nurture paths:

    * Delete or bypass **Wait for reply** / **Contact replied** conditions before SMS or email actions.
    * Keep the initial day-1 send unchanged.
    * Ensure TI follow-up workflow enrollment does not require an inbound message first.
  </Step>

  <Step title="3. Re-sync partner locations">
    After saving the snapshot workflow, run the same custom-value / workflow link sync used in PR #785 across active partner sub-accounts so enrollment IDs and funding links stay aligned.
  </Step>

  <Step title="4. Acceptance test">
    Enroll a test contact with a realistic phone/email. Do **not** reply inbound. Confirm:

    * Day-1 message sends on enrollment.
    * 24h follow-up sends without a reply.
    * Multi-day drip continues on schedule.
  </Step>
</Steps>

## App verification only

If nurture still fails after GHL changes, confirm delivery logs show `addContactToWorkflow` success for the partner's `ghlWorkflowId` in Convex `prospectingActivity` / delivery log — enrollment problems are app-side; silent follow-ups are almost always workflow builder conditions.