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

Memberships

Manychat Masterclass (Free)

1.4k members • Free

AI Automation Society

202.7k members • Free

Brendan's AI Community

21.6k members • Free

AI Automation Agency Hub

272.5k members • Free

Sell & Scale (Free)

6.5k members • Free

Creators

16k members • Free

Kern Inner Circle

862 members • $397/m

5 contributions to Brendan's AI Community
This Voice Agent Took Every Call for 2 Years
We've had an AI Voice Agent running live in production for a client for the past 2 years. It's handled over 2,500 calls, saved hundreds of hours, and generated an ROI of over $48,000. In this video, I'm giving you a complete breakdown of this AI receptionist system. I'll show you the real-world data, the tangible business benefits, and a step-by-step walkthrough of how we built it using Retell AI and Make.com. This is a must-watch if you are a business owner tired of handling inbound calls, or an aspiring AI builder who wants to sell these systems to clients.
2 likes • 20h
This is a great video. I'll watch it again and try to replicate it using n8n. Thanks for sharing your experience. It's actually good to see a real working Agent
What are you focused on learning?
Which of these three AI deployments are you most interested/focused on learning?
Poll
156 members have voted
1 like • 20h
I chose AI Voice Agents, but without leaving n8n behind. That would be my main focus, but I believe that AI Chatbots still a lot of potential behind the basic webpage chat bot we all see. Yesterday I watch a tech webinar about managing memory patterns for chatbots that many people, myself included, don't know much about that shows how to improve the performance of chatbots depending on the use case.
Intro
Starting this journey with the goal of setting up an AI Voice Agency to help small and medium business owners that will allow me to run the business from different parts of the world. More like a lifestyle business than looking to grow a multimillion dollar one. I'm also interested in RAG systems as I think those have still huge potential. I hope to be soon sharing my growth experience here. I wish everyone the best in your own journeys
Client fired their $8k/month automation team. I replaced their entire operation with a 19-minute workflow.
Client fired their $8k/month automation team. I replaced their entire operation with a 19-minute workflow. The numbers will blow your mind: THE BACKSTORY SaaS founder, David: "I'm paying a team $8k/month and nothing works" Me: "What are they supposed to be automating?" David: "Lead nurturing, trial management, customer onboarding" Me: "How long have they been working on it?" David: "14 months. Still in 'development phase'" 🚩 Red flag: 14 months for basic SaaS workflows THE EXISTING NIGHTMARE What his "automation specialists" delivered: - 23 separate tools duct-taped together - 156 manual handoffs between systems - 4-person team managing the chaos - Monthly costs: $8,000 team + $2,300 tools = $10,300 - Success rate: 31% (most leads fell through cracks) - Customer complaints: Daily David: "They keep saying it's 'almost ready'" Translation: They have no idea what they're doing. THE BREAKING POINT Last straw: 347 trial users got stuck in limbo - No welcome emails sent - No trial access granted - No follow-up sequences triggered - Support tickets flooding in David's exact words: "I'm spending $10k/month to create more problems." THE 19-MINUTE SOLUTION Discovery call ended, I opened Skada.ai: "Build complete SaaS customer lifecycle: lead capture → nurture sequence → trial signup → onboarding → conversion tracking → customer success handoff" 19 minutes later: ✅ Lead scoring and routing ✅ Automated nurture campaigns ✅ Trial provisioning system ✅ Onboarding workflow ✅ Usage tracking and alerts ✅ Conversion optimization ✅ Customer success handoffs THE LIVE TEST David: "Can we test this right now?" Me: "Sign up for your own trial with a test email" He watched in real-time: - Instant welcome email - Trial access granted immediately - Personalized onboarding sequence started - His CRM updated automatically - Usage tracking began - Slack notification to his team David: "This works better than our $10k/month solution" Me: "And it's been 3 minutes since you signed up"
1 like • Sep 22
Congrats! This is next level. My question would be, what are you doing to find these customers? Mail campaigns, cold calling, Meta/Google/Social media campaigns? The other questions, are your solutions n8n only or do you build a front -end and connect it to your n8n/make in the back end?
How to fix this make.com scenario for appoinment booking?
Good morning everyone, Hope you are doing well. I watched and implemented "Ultimate Appointment Booking Voice Agent". I was getting an error in check availability. Can you help me or guide me to fix this issue? Kind regards,
How to fix this make.com scenario for appoinment booking?
3 likes • Aug 21
This is probably coming from Cal.com, not Make, since the 401 Unauthorized implies that the credentials you are using do not belong to you. Check the **credentialId (and/or externalId) you’re passing in the query string. It is most likely owned by a different Cal.com user than the one whose API key you’re using in the Authorization: Bearer … header. You can’t query another user’s calendar with your API key unless their credential is owned by the same user/workspace and allowed for that key. 1. Rotate the key you exposed - Your screenshot shows a live key. In Cal.com: Settings → Developers → API Keys → Revoke that key and create a new Server (secret) API key. - Update the HTTP module with the new key. 2. Verify you’re using the right key type - Use a Server API key (secret). A publishable key will 401 here. 3. Discover the correct calendar credentials for this key - Add a quick HTTP module (GET) before your “Get all the busy hours” call: - The response lists the id (this is credentialId) and externalId for calendars that belong to this API key’s user. 4. Use those values in your busy-times request - Replace the hardcoded numbers with the values from step 3. Whenever it makes sense, avoid hardcoding IDs. In Make, map the credentialId/externalId from the /v2/credentials step so it stays correct if things change. Hope this helps. Cheers!
1-5 of 5
Dennys Nava
2
8points to level up
@dennys-nava-5925
No internet marketing experience. Computer Engineer. 24 years in sales.

Active 16h ago
Joined Aug 2, 2025
Powered by