Activity
Mon
Wed
Fri
Sun
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
What is this?
Less
More

Memberships

Scale with AI

117 members • Free

Ai Automation Business Skool

47 members • $49/month

Business Builders Club

4.3k members • Free

n8n

1.3k members • Free

AI Automations by Kia

21.7k members • $1/month

AndyNoCode

30.1k members • Free

Ai Titus

892 members • Free

AI Automation Mastery

26.4k members • Free

Brendan's AI Community

23.5k members • Free

55 contributions to AI Automation Society
AI Lead Qualification & Routing System (Built End-to-End)
Hey everyone, I recently built an AI-powered lead qualification and routing system designed to automate how inbound leads are evaluated and distributed across a sales pipeline. Here’s what the system does: • Captures inbound leads (from Facebook Ads) via webhook • Normalizes and validates incoming data • Checks historical lead data to identify new vs. returning prospects • Uses AI to score intent and classify each lead • Logs AI decisions for transparency and auditability • Automatically routes leads to Sales, Nurture, or Discard • Updates HubSpot accordingly • Sends real-time Slack notifications for high-intent prospects How It Works Once a lead enters the system, it goes through a structured validation and enrichment layer before being passed into an AI decision engine. The AI evaluates intent and recommends the next best action. Based on that recommendation, the workflow automatically routes the lead to the appropriate pipeline while maintaining clean CRM data and logging all decisions. The architecture is modular and production-ready, meaning it can scale across different lead sources and CRM environments. Benefits • Eliminates manual lead qualification • Improves response time for high-intent leads • Keeps CRM clean and structured • Reduces sales team workload • Scales automatically as lead volume increases If anyone’s interested, here’s a complete overview of the workflow where I walk through the full system architecture: 👉 https://youtu.be/CknV7KcYVWA Happy to answer questions or discuss improvements.
1 like • 2h
@Saad Alam Thanks
0 likes • 2h
@Hicham Char completely agree normalization can get messy very quickly if it’s not handled early in the workflow. That was actually one of the main reasons I built this layer first. Once the data is standardized before hitting HubSpot, everything downstream becomes much easier cleaner records, better segmentation, and far less manual cleanup. Definitely saves a lot of operational time and keeps the CRM reliable.
An observation from a system I just finished building
A lot of people talk about “doing outbound consistently,” but what usually breaks isn’t effort — it’s friction. Recently, I built a LinkedIn outreach system to remove that friction completely. What the system does: - Scrapes targeted LinkedIn leads - Researches each profile - Writes a personalized connection message per lead - Sends the connection request - Automatically sends the 1st and 2nd follow-up What this removes from the process: - Searching and opening profiles - Copy-pasting profile data - Writing messages one by one - Manually remembering and sending follow-ups Realistic time impact: ~20 minutes saved per lead. At ~30 leads/week → ~10 hours saved every week. The bigger outcome: Outbound runs in the background. Messages stay personalized.Follow-ups never fall through .And consistency finally becomes boring (in a good way). If you’re curious and want to see the exact workflow or explore setting something similar up for yourself, feel free to DM me and we can walk through it on a quick call.
0 likes • 27d
@Hicham Char Appreciate that, @Hicham Char You’re spot on the research layer is where most systems fall apart. Getting the context right without sounding robotic took the most iteration, but that’s also what makes the replies feel human.
0 likes • 26d
@Dean Almeida Thanks
UK builders: which phone/SMS provider is best for Vapi?
I’m building an AI voice agent in Vapi and I need a provider that can handle both: ✅ Inbound/Outbound calling (UK numbers) ✅ SMS (send + receive, ideally) ✅ Good reliability in the UK (deliverability + call quality) ✅ Reasonable pricing + easy setup I know Twilio is the common choice and looks cost-effective, but I’ve heard mixed feedback about reliability in the UK. For anyone shipping real client systems in the UK: Which provider has been the most reliable for you? - Twilio? - Vonage / Nexmo? - Telnyx? - MessageBird? - Sinch? - Anything else? If you’ve used it with Vapi specifically, I’d love to know: - call quality experience - SMS deliverability - pricing surprises - any setup gotchas Thanks in advance — want to pick something stable before I roll this out to clients.
0 likes • Dec '25
@Frank van Bokhorst Thanks
0 likes • Dec '25
@Kevin troy Lumandas I will check it, Thanks for the advice.
Need guidance from anyone using Vapi Structured Outputs + Webhooks
Hey everyone 👋 I’m running into something with Vapi’s new Structured Outputs and would love insight from anyone who’s worked with the latest update. Context: - I previously used Vapi’s Summary (now marked deprecated) - It was automatically sent to my Server URL (n8n webhook) via end-of-call-report - This worked perfectly for sending internal call summaries by email What I changed: - Moved the summary logic into Structured Outputs - Structured output is: - Correctly generated - Visible in Vapi Call Logs → Structured Outputs - Linked to the assistant - Storage enabled (HIPAA mode on) The issue: - The structured output does NOT get sent to the webhook - end-of-call-report still fires, but only includes transcript/messages - No analysis / structuredOutputs appear in the webhook payload Question: Has anyone successfully sent Structured Outputs to a webhook in the new Vapi version? - Is there a hidden config / supported event I’m missing? - Or is API pull (GET /calls/{id}) currently the only workaround? Would really appreciate guidance from anyone who’s already solved this 🙏
0 likes • Dec '25
@Frank van Bokhorst Great, I will try it
0 likes • Dec '25
@Frank van Bokhorst Thanks
Lead Scoring Automation That 3x'd Our Close Rate
Built a lead scoring automation that saved my sales team 15 hours per week and tripled our close rate. Here's the exact system: Every inbound lead gets scored 1-100 based on 12 criteria: Company size (from LinkedIn/Clearbit data), industry match (are they in our sweet spot?), budget signals (job postings, tech stack, funding), urgency indicators (language in their message), engagement history (have they visited pricing page? downloaded content?), title/role of the person reaching out, source (referral vs cold vs content), time since first touch, email domain (corporate vs gmail), geographic fit, previous interactions with our brand, and tech stack compatibility. Leads scoring 80+ get routed directly to calendar booking. 50-79 go to a nurture sequence. Under 50 get a polite "not a fit" response. Results: - Close rate: 8% → 23% - Sales time on unqualified leads: Down 70% - Average deal size: Up 40% (better qualified = bigger budgets) Who's still manually qualifying leads? There's a better way.
1 like • Dec '25
Solid Workflow @David Iya
1-10 of 55
Aditya Bisht
5
164points to level up
@aditya-bisht-5245
I'm Aditya Bisht My email is - [email protected]

Active 2h ago
Joined Sep 28, 2025
Powered by