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

Memberships

AI Automation Mastery

22k members • Free

Voice AI Accelerator

6.7k members • Free

AI Automation Society

214.4k members • Free

10 contributions to AI Automation Society
Looking for RetellAI help
Hey folks 👋 I’ve been grinding away at building a Retell AI voice agent and I’m stuck. I first tried a conversational agent, but it just couldn’t handle the complexity I need. I’ve now moved back to a multi-state agent, but I’m running into all sorts of issues - the flow improvises, skips states, calls tools at the wrong time, and generally doesn’t behave how I design it. What I really need is something that can: - Switch smoothly between requests in one call - Handle normal conversational flow without breaking - Call tools/webhooks reliably - Manage more complex logic and branching If you’ve built production-ready Retell agents that balance conversational handling with structured flows, I’d love to chat and possibly bring you on as a consultant. Please DM me 🙏
0 likes • Sep 5
Thanks for your help everyone - much appreciated!
Connecting On LinkedIn
Hey everyone, I’m new here and starting to build my network on LinkedIn. I’m diving into the world of AI automation and documenting the process — but more importantly, I’d love to connect with people who are also interested in tech, entrepreneurship, or just personal growth in general. If you’re open to connecting, drop me a request — I’ll gladly connect back. My LinkedIn: https://www.linkedin.com/in/danielyanchev-automations/
0 likes • Aug 20
Happy to connect! https://www.linkedin.com/in/hayleypsmith/
Spent 3 months building the "perfect" invoice parser. It processed exactly 0 invoices successfully.
Here's the painful journey and what actually worked: MONTH 1: The Regex Nightmare Built custom patterns for every vendor format Code looked like: (?:Invoice\s*#?\s*:?\s*)([A-Z0-9-]+) Accuracy: 60% on good days Broke completely when vendors changed templates MONTH 2: The Framework Phase Added PyPDF2 + Tabula + Tesseract OCR Created a 500-line Python monster Accuracy jumped to 75% Processing time: 2 minutes per invoice Still failed on scanned documents MONTH 3: The API Frankenstein Chained PDF.co → Google Vision → GPT-3.5 Cost: $0.50 per invoice Accuracy: 85% Maintenance: Daily firefighting Then my client said: "This is worse than manual. We're going back to data entry." That hurt. But it forced me to rethink everything. THE SOLUTION (built in one afternoon): 3 nodes in n8n: 1. Email trigger (watches for attachments) 2. PDF Vector parse (handles ANY format - even handwritten) 3. Google Sheets append That's it. No regex. No complex logic. No maintenance. CURRENT STATS: - Processing: 8,000+ invoices/month - Accuracy: 99.2% - Failed documents: ~60/month (mostly corrupted files) - Setup time per client: 45 minutes - Maintenance: Check once a week, fix maybe 1 thing - Revenue: $1,200/month per client The painful lesson: I spent 3 months building what I thought was impressive. Clients just wanted their invoices in a spreadsheet. What overcomplicated monster are you maintaining that could be 3 simple nodes?
2 likes • Aug 20
@Duy Bui Have you encountered any instances of invoices not actually being attached to an email, and instead being sent via a clickable link? If so how did you overcome this?
1 like • Aug 20
@Duy Bui nice, this makes sense. Thanks!
CEO stopped me mid-pitch: "Skip the tech stuff. Show me the money." Here's the napkin math that closed $35k/month in savings
So I pulled out this napkin math that closed the deal in 5 minutes: THEIR CURRENT INVOICE PROCESSING: Staff: - 3 full-time data entry people - $35/hour × 8 hours × 22 days = $6,160/month each - Total salary cost: $18,480/month Errors: - Manual error rate: 3% - 6,000 invoices/month × 3% = 180 errors - Cost per error (corrections, credits, relationships): $50 - Error cost: $9,000/month Speed: - Current: 3-day processing backlog - Late payment penalties: $3,000/month - Lost early payment discounts: $5,000/month Total monthly burn: $35,480 MY PROPOSED AUTOMATION: One-time setup: $2,500 Monthly maintenance: $500 Tool costs (n8n + PDF Vector): $99/month Processing time: 30 minutes daily oversight Error rate: 0.3% (18 errors vs 180) Same-day processing (capture all early discounts) Their monthly cost with automation: $599 Their monthly savings: $34,881 ROI payback period: 2.1 days THE CEO's RESPONSE: "Why the f*** haven't we done this already?" *Signed contract on the spot* THE ACTUAL BUILD: - Gmail → PDF extraction → Validation → QuickBooks - Built in n8n in 4 hours - Been running for 7 months - They've processed 42,000 invoices - Total downtime: 47 minutes They tried to give me a bonus last month because the savings were "embarrassing their previous decisions." The lesson: Nobody cares about your nodes. They care about their numbers. What's the biggest monthly saving you've delivered? Drop the actual numbers 📊
3 likes • Aug 20
Love this. Were there any hurdles around data security that were flagged during implementation - any sensitivities with information from invoices being shared with external tools?
1 like • Aug 20
@Duy Bui Okay this is an elite response. Super helpful thank you!
Best Voice AI
I just got hired to build my first AI Voice BOt using make.com and ghl integration What are the pros and cons of GHL AI Reteller AI Vapi?
0 likes • Aug 20
@Jonathan Drouin I had the same issue, I adjusted the speed setting and also added : When reading out phone numbers or codes, always speak them digit by digit. For example, say: "zero four one two one one one two two two." ✅ Do this every time — never group numbers. Speak naturally and clearly. This seemed to help a lot ^
1-10 of 10
Hayley Smith
3
39points to level up
@hayley-smith-5092
Ai enthusiast

Active 54d ago
Joined Jul 10, 2025
Powered by