{"slug":"ghl-conversation-agent-engage-followup","title":"Using GHL Conversation AI to Replace Engage Follow-Up Drips","tags":["ghl","conversation-ai","follow-up","speed-to-lead","automation"],"agent_summary":"How to configure GoHighLevel's native Conversation AI agent to replace static SMS drip sequences for engaged leads, including auto follow-up configuration and system prompt setup.","trigger_phrases":["ghl conversation ai setup","replace drip with conversation agent","go high level bot follow up","conversation ai auto follow up","ghl ai agent for lead follow up","speed to lead conversation agent"],"runnable":true,"markdown":"## GHL Conversation AI to Replace Engage Follow-Up Drips\n\n### Why Replace Static Drips with Conversation AI\n- Static drip sequences are one-way — they send but never listen\n- Conversation AI can respond in seconds (massive speed-to-lead improvement)\n- Can qualify leads and directly book on Scott's calendar\n- Scales past human bandwidth (bot can handle 100+ leads/day)\n- Fully snapshot-shippable to other agency clients\n- Token cost is trivial\n\n### Architecture\n1. **Lead opts in** via quiz funnel\n2. **Immediate:** Bot sends first touch (personalized based on funnel data)\n3. **Auto Follow-ups:** If lead goes silent, bot sends re-engagement messages\n4. **Booking:** Bot asks for first name, email, and books directly\n5. **Parallel:** GHL scheduled workflow populates daily phone call tasks for manual double-dial\n\n### Key Configuration\n\n**Auto Follow-Up Settings:**\n- Enable \"Auto Follow-up\" in Conversation AI settings\n- Set delay between follow-ups (e.g., 15 minutes, 4 hours, 24 hours)\n- Set active/working hours (8am-5pm) to avoid late-night messages\n- Chain multiple follow-ups\n\n**Follow-up Messages (add to system prompt or workflow triggers):**\n1. \"If those times don't work, what's a better time for you?\"\n2. \"Still want me to show you what I built for you?\"\n3-8. Additional re-engagement touches\n\n**System Prompt Must Include:**\n- Context of what the lead saw (e.g., \"They were pitched: Do you want to see the site?\")\n- Business info and services\n- Booking instructions (ask for first name + email, then book)\n- Tone guidelines (human, casual, blue-collar appropriate)\n\n### Important Notes\n- GHL Conversation AI IS proactive via auto follow-up — it's not purely reactive\n- The bot pulls from system prompt when auto follow-up timer fires\n- For static/exact messages, trigger a workflow instead of relying on AI generation\n- GHL cannot send AI-generated media natively\n- \"Workflows with agent triggers must always be published\" — cannot save as draft\n- The GHL AI workflow builder sometimes inserts wrong custom value tags — always verify\n\n### Hybrid Approach (Recommended)\n- Bot handles all SMS: initial response, qualification, follow-ups, booking\n- Scott double-dials as highest-converting channel (supplement, not replace)\n- GHL scheduled workflow creates one phone call task per day per active lead\n- Bot is the safety net for when humans are slow (avg 4 days to first call!)\n\n### Testing\n- Use the GHL bot testing interface (note: it has known bugs)\n- Test with valid contacts, not just the built-in simulator\n- Verify booking actually creates calendar events and sends confirmations\n","html":"<h2>GHL Conversation AI to Replace Engage Follow-Up Drips</h2>\n<h3>Why Replace Static Drips with Conversation AI</h3>\n<ul>\n<li>Static drip sequences are one-way — they send but never listen</li>\n<li>Conversation AI can respond in seconds (massive speed-to-lead improvement)</li>\n<li>Can qualify leads and directly book on Scott's calendar</li>\n<li>Scales past human bandwidth (bot can handle 100+ leads/day)</li>\n<li>Fully snapshot-shippable to other agency clients</li>\n<li>Token cost is trivial</li>\n</ul>\n<h3>Architecture</h3>\n<ol>\n<li><strong>Lead opts in</strong> via quiz funnel</li>\n<li><strong>Immediate:</strong> Bot sends first touch (personalized based on funnel data)</li>\n<li><strong>Auto Follow-ups:</strong> If lead goes silent, bot sends re-engagement messages</li>\n<li><strong>Booking:</strong> Bot asks for first name, email, and books directly</li>\n<li><strong>Parallel:</strong> GHL scheduled workflow populates daily phone call tasks for manual double-dial</li>\n</ol>\n<h3>Key Configuration</h3>\n<p><strong>Auto Follow-Up Settings:</strong></p>\n<ul>\n<li>Enable \"Auto Follow-up\" in Conversation AI settings</li>\n<li>Set delay between follow-ups (e.g., 15 minutes, 4 hours, 24 hours)</li>\n<li>Set active/working hours (8am-5pm) to avoid late-night messages</li>\n<li>Chain multiple follow-ups</li>\n</ul>\n<p><strong>Follow-up Messages (add to system prompt or workflow triggers):</strong></p>\n<ol>\n<li>\"If those times don't work, what's a better time for you?\"</li>\n<li>\"Still want me to show you what I built for you?\"\n3-8. Additional re-engagement touches</li>\n</ol>\n<p><strong>System Prompt Must Include:</strong></p>\n<ul>\n<li>Context of what the lead saw (e.g., \"They were pitched: Do you want to see the site?\")</li>\n<li>Business info and services</li>\n<li>Booking instructions (ask for first name + email, then book)</li>\n<li>Tone guidelines (human, casual, blue-collar appropriate)</li>\n</ul>\n<h3>Important Notes</h3>\n<ul>\n<li>GHL Conversation AI IS proactive via auto follow-up — it's not purely reactive</li>\n<li>The bot pulls from system prompt when auto follow-up timer fires</li>\n<li>For static/exact messages, trigger a workflow instead of relying on AI generation</li>\n<li>GHL cannot send AI-generated media natively</li>\n<li>\"Workflows with agent triggers must always be published\" — cannot save as draft</li>\n<li>The GHL AI workflow builder sometimes inserts wrong custom value tags — always verify</li>\n</ul>\n<h3>Hybrid Approach (Recommended)</h3>\n<ul>\n<li>Bot handles all SMS: initial response, qualification, follow-ups, booking</li>\n<li>Scott double-dials as highest-converting channel (supplement, not replace)</li>\n<li>GHL scheduled workflow creates one phone call task per day per active lead</li>\n<li>Bot is the safety net for when humans are slow (avg 4 days to first call!)</li>\n</ul>\n<h3>Testing</h3>\n<ul>\n<li>Use the GHL bot testing interface (note: it has known bugs)</li>\n<li>Test with valid contacts, not just the built-in simulator</li>\n<li>Verify booking actually creates calendar events and sends confirmations</li>\n</ul>\n"}