Build a nurture sequence

What you'll get

• A ready-to-review workflow in your GHL account: texts, emails, and waits in the right order, every message written out.
• Stop-on-reply built in, so nobody gets a robot follow-up after a human conversation has started.
• Quiet hours, so the sequence never texts somebody at two in the morning because a wait timer landed there.
• A matching exit workflow: when someone replies, they leave the nurture, get tagged, and you get notified.

Quick start

Build a 7-day nurture for new leads: text right away, email an hour later, then follow up daily until they reply.

Only let this workflow send between 8am and 9pm.

Show me the full plan first. Do not build anything until I approve it.

The pro prompt

Build a nurture workflow in my [Radiance Med Spa] account called "New Lead Nurture 7 Day". Trigger: when the tag [new-lead] is added.
The sequence: (1) Immediately, text: "Hi {{first name}}, this is [Dana] from [Radiance Med Spa]. Thanks for reaching out about our [body contouring special]! Want me to grab you a free consult this week?" (2) Wait 1 hour, then send an email, subject "Your consult is waiting", friendly, three short paragraphs, one button to my booking link. (3) Wait 1 day, then text a soft check-in. (4) Wait 2 days, then email a before-and-after story from a real client. (5) Wait 3 days, then text a last-call message about the special ending.
Set quiet hours on this workflow: it may only send between [8am] and [9pm], [every day]. Nothing goes out outside that window.
Stop the sequence the moment they reply on any channel. Also build the exit workflow: when they reply, remove them from the nurture, tag them [warm-lead], add a note with what they said, and notify me.
Before you build anything: show me every message written out for my approval, and verify my account's real pipeline, tag, and calendar IDs so nothing fails silently.

Everything in [brackets] is yours to change. The last paragraph is the safety net: it makes Claude plan first and check your account's real setup before touching it.

What Claude builds

What happens when you ask

1. Claude shows you the full plan: every message written out, every wait, in order. Nothing is built yet.
2. You edit in plain English: "make step 3 warmer", "move the last text to day 5". Then approve.
3. Claude checks your account's real pipelines, tags, and calendars first, then builds the workflow and the exit workflow, and hands you the link to review in GHL.

Good to know

• Ask for quiet hours on anything that sends texts. Wait timers do not care what time it is: a one-day wait started at 11pm fires at 11pm. A window of 8am to 9pm is the common answer, and it is set per workflow, so every sequence that texts needs its own.
• Quiet hours are the only place a sending window lives. There is no time-of-day setting inside the AI agent builders, so if a bot hands off to a workflow, this is what protects the handoff.
• Once set, quiet hours stay set. Edit a message or add a step later and the window comes through untouched.
• GHL's editor struggles past about 40 steps in one workflow. Claude knows this and splits long sequences automatically.
• Messages come out in your voice if you give Claude a sample first: paste one text you would actually send and say "write like this".
• The nurture and its exit workflow are a pair. If you ever remove one, ask Claude to update the other, so nothing points at a workflow that is gone.
• If a step in your sequence moves a deal to a new stage, it needs to find that deal first. Say "look up the opportunity, then move it" and Claude wires both. A move on its own saves cleanly and then does nothing.

Where people go wrong

Related guides

• Add an exit workflow
• Audit your workflows