Activity
Mon
Wed
Fri
Sun
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
What is this?
Less
More
21 contributions to Brendan's AI Community
How I use n8n + Claude + KnockKnock + GHL together — missed-call-to-booking flow
This community is about Claude Code and n8n, so I figured it’d be worth sharing exactly how I’m using both in a production automation system. Setup: KnockKnock (AI SMS) + GHL (CRM/calendar) + n8n (orchestration) + Claude (intent classification) Here’s the full flow: Trigger (GHL): Missed call or form submit → GHL fires a webhook to n8n. First n8n check: query GHL to see if an active conversation already exists on this contact’s number. If yes → stop. Prevents double-threading when a lead calls twice. First message (KnockKnock): KK sends an SMS within 60 seconds. “Hey [Name] — saw you reached out about [service type]. Is that still something you’re looking into?” Short. Human. No pitch. Intent classification (Claude via n8n): When the lead replies, n8n passes the text to Claude with a simple system prompt: “Classify this SMS reply as HOT, WARM, or COLD. HOT = clear interest or booking signal. WARM = soft interest. COLD = not interested or wrong person.” Claude returns a single word. n8n routes via switch node. HOT branch: Send GHL booking link → appointment auto-creates in GHL calendar → pipeline stage updates → owner notification fires. WARM branch: Contact enters GHL 48-72hr nurture sequence. If they re-engage → back into HOT routing. COLD branch: Tag in GHL. Remove from active flow. Long-term drip. Write-back to GHL (every branch): n8n updates the GHL contact record: • Last intent: hot/warm/cold • Service mentioned: extracted from Claude’s output • Execution ID: [YYYY-MM]-[workflow-name]-[version] • Last message timestamp The Execution ID matters: query it at the start of every n8n run to detect duplicates. When debugging a specific contact, it gives you the exact execution to pull up. Stack summary: GHL → trigger, CRM, calendar, pipeline, notifications n8n → all logic: routing, Claude calls, duplicate detection, write-back KnockKnock → AI SMS layer Claude → intent classification (one clean word output = easy switch node routing)
0 likes • 4d
@Zubair Aqeel Exactly the right architecture. GHL tag as the intent signal means n8n never has to re-classify — it just reads state and applies the matching cap. Clean separation of concerns. The extension I’d add: tag transitions. Storm-damage-inbound → qualified → booked as progressive tags, and the n8n check at each retry looks at where the lead is in the progression, not just the initial intent. A storm damage lead already in contact gets a different follow-up cap than a fresh storm damage inbound. Are you querying the GHL contact lookup in n8n to pull the tag, or do you get it in the initial webhook payload?
0 likes • 3d
@Zubair Aqeel Exactly the goal — the full journey readable from one contact record without jumping between tools. Let me know how the tag transitions work in your next build. Would love to see how you wire the handoff between stages.
Voice AI handled 47 inbound calls while the business owner was on a job site. Here's the exact flow.
Built this for a trades client who was losing a lead every time his hands were dirty. The setup: 📞 Call comes in → AI picks up in 2 rings, introduces itself as the scheduling assistant 🗣️ Intake questions: → "What service are you looking for today?" → "Whereabouts are you based?" → "How urgent is this?" Based on answers: → Urgent → offers next available slot, confirms booking → Not urgent → sends SMS booking link → Out of area → apologises + gives alternative contact 📱 Owner gets SMS summary after every call: name, number, what they need, what action was taken. Went from missing 60% of calls to missing 0%. Stack: voice AI layer → webhook → n8n for routing → CRM for logging and booking. Anyone else building voice intake for trades/service businesses? Would love to compare routing logic.
0 likes • 7d
That's a genuinely smart prompt — adding that to the intake script. The open-ended handoff question surfaces things callers wouldn't think to mention upfront (job address, gate codes, specific symptoms). For trades clients especially, that intel helps the owner show up prepped rather than reactive. Will test it on the HVAC deployment this week and report back.
0 likes • 7d
The urgency branching point is something most builders overlook — and you're right that storm damage changes the psychology completely. When someone's roof is leaking they're not shopping, they're committing to the first credible responder. On the non-urgent SMS path: we run an automated follow-up sequence — second touch at 60 min, third at 24h, final at 72h before marking unresponsive and dropping to email nurture. The 2-hour window is when recovery is still high-probability; after 24h you're fighting inertia. How do you trigger the storm vs routine split in intake — keyword detection or a direct branching question early in the voice flow?
Voice AI + GHL combo that's working right now (12 bookings in 48hrs)
Voice AI + GHL combo that's working right now: Step 1: Missed call triggers workflow Step 2: AI sends personalized SMS in 60 seconds Step 3: If no reply → AI voice call follows up Step 4: Lead qualifies → calendar auto-booked Built this in GHL + n8n. Result for one client this week: 12 booked calls from leads they were already getting. No new ads. No cold outreach. Just faster follow-up with AI. Anyone else combining voice AI with SMS follow-up? What's your stack?
0 likes • 16d
The 24h no-show voice follow-up is exactly what I layered in after the first week — already seeing ~18% of no-shows rebook when the AI calls back at the right time window. For voice I'm running GHL's native Voice AI, trained on each client's FAQs and linked directly to the calendar. The full loop: 📲 Missed call → 60s SMS qualify 📅 Book → confirmation SMS 🎙️ No-show → 24h voice follow-up 💬 48h SMS recovery for anything voice didn't close Stacking the touchpoints is where the extra 15-20% comes from. Appreciate the gold, Brendan AI 🙌
AI Voice Agents + GHL + website intelligence = the complete system
If you're building voice agents (like many in this community), here's a layer you might be missing: Knock Knock App adds visitor intelligence to the equation. Before your AI even picks up the phone, Knock Knock has already: → Identified who they are → Scored their intent → Pulled their GHL record → Decided whether to chat, call, or WhatsApp them So when your voice agent answers, it already knows the context. All memory shared. All logged to GHL. This is the missing piece between website traffic and voice AI. knockknockapp.ai — built to work with GHL natively. Building voice + CRM workflows? Would love to connect and swap ideas 👇
0 likes • 17d
@Brendan Jowett The handoff logic runs on intent score thresholds set in GHL. Low intent (browsed 1-2 pages, no key actions) → WhatsApp nurture drip. Mid intent (visited pricing, checked services multiple times) → AI SMS conversation to qualify. High intent (hit pricing + contact page, or triggered a specific event like watching the demo video) → AI voice agent calls within 60 seconds. GHL routes them via workflow branches based on the tag the website intelligence layer passes over. The pre-call context is the key — the voice agent knows what they looked at, so it opens with relevance instead of starting from zero. Huge conversion lift.
I deployed an AI Voice Agent for home service businesses — $31k in 72hrs from dead leads (full breakdown)
Since this community is all about AI Voice Agents — here's a real deployment with real numbers. Use case: Home service businesses (HVAC, cleaning, plumbing, roofing) Problem: They have hundreds of old leads doing nothing in their CRM The Voice Agent Stack: 🤖 GHL AI Voice Agent (Inbound) → Answers every call 24/7, qualifies the lead, books the appointment automatically 📤 GHL AI Voice Agent (Outbound) → Auto-dials dormant leads on a 30-day rotation 💬 SMS AI → Fires within 2 minutes on every unanswered call 🚷 KnockKnock App → Captures door-to-door field leads directly into CRM in real time 🔄 Reactivation Workflow → n8n triggers monthly outbound calling campaigns The Agent Logic Flow: New lead captured → Voice agent dials in <60 seconds → No answer → SMS fires → SMS reply → Booking flow → Appointment confirmed → Reminder sequence For dead leads: Monthly n8n trigger → Pulls contacts tagged 'cold' older than 30 days → Queues outbound voice campaign → Agent calls → Interested → Routes to booking Result from one client deployment: 🔸 847 dormant leads fed into reactivation 🔸 23 booked calls 🔸 9 closed deals 🔸 $31,000 in revenue 🔸 72 hours Voice provider: Retell AI via GHL Voice AI Workflow engine: n8n (on-prem) CRM: GoHighLevel Field capture: KnockKnock This is exactly the kind of real-world agentic deployment this community is about. Happy to share the Retell agent config or the n8n workflow — drop "🎙️" below.
0 likes • 17d
It’s been field-tested — that’s the only thing that actually earns the label.
0 likes • 17d
Appreciate that — if you want to see it running on a real account, autoxinity.com has it live right now.
1-10 of 21
Liton Sarker
5
273 points to level up
@liton-sarker-4404
I turn dead leads and cold site visitors into booked calls — for any business. AI + GHL. autoxinity.com

Active 18h ago
Joined Aug 16, 2026
Powered by