Build a nurture sequence
A follow-up machine that texts, emails, waits, and stops the second someone replies.
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.
- 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.
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. 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
- Claude shows you the full plan: every message written out, every wait, in order. Nothing is built yet.
- You edit in plain English: "make step 3 warmer", "move the last text to day 5". Then approve.
- 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
- 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.
Where people go wrong
| What happened | The fix |
|---|---|
| "It built the workflow but nothing ever sends." | Say "audit this workflow". GHL fails silently when something inside is misconfigured; the audit finds it in seconds. |
| "The messages sound generic." | Give Claude your voice before building: paste a real text you have sent and say "write like this". |
| "I want to change one message." | Say "update step 3's text to..." and never rebuild from scratch. Updates keep everything connected. |
Related guides
- add-an-exit-workflow
- audit-your-workflows
This guide ships inside GHL Command and updates with the product. Not installed yet? Get it free. Stuck? Email [email protected] and a human answers.