Activity
Mon
Wed
Fri
Sun
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
What is this?
Less
More
40 contributions to Brendan's AI Community
Before you sell a plumber an AI receptionist, read this thread
I spent some time on a plumbing forum to see how owners actually talk about missed calls. One thread stuck with me. A guy running a 3-person shop posted 47 missed calls in a month, only 5 voicemails. He'd already tried his wife on the phone and a part-time receptionist at $1,500 a month. The plumbers who answered weren't impressed. One misses 5 to 10 calls a day and says most are price shoppers. Another said to tag every missed call for 2 or 3 weeks before buying anything, and when his shop did that, most of the calls were junk. From now on, when I talk to an owner, my first question will be how many of his missed calls were real jobs, before I mention the agent at all. If he doesn't know, that's the first thing we find out together. How do you handle owners who say "most of those calls are garbage anyway"?
Before you sell a plumber an AI receptionist, read this thread
Diploma at 12, AI agents at 16. Finally sharing the backstory
Hey everyone, Haris here, from Canada (originally Cameroon). Some of you might remember Sentinelle, the property-maintenance agent that took first place in the Retell hackathon here. I've been building quietly since then. Today I posted my backstory on LinkedIn for the first time: I got my American high school diploma at 12, studying online from Cameroon after my regular school day, on a connection that kept dropping. The diploma is in the slides. Now I run DICSIO, where I build AI agents for small businesses. Right now I'm focused on phone agents for plumbing and HVAC businesses. I'm going to keep posting what I build there, including what breaks. Here it is: https://lnkd.in/p/g4ptBXrB It's my very first post there, so if it resonates, a like or a comment would honestly help a lot. And a real question for the builders here: what made you start posting about your work, and did it actually bring you clients?
0 likes • 3d
@Brendan Jowett The "show what breaks" part is what I'm doing next. Tomorrow's post is about 23 texts my automations sent that never arrived, while n8n showed every one of them as sent. Took me months to notice.
0 likes • 12h
@Cheryl Tibbs Good to hear it actually brought clients, even if slower. I'm sticking with the what-broke posts, the SMS one went up this week. How long did it take before the first client came from posting?
If your voice agent sends a follow-up text, check this
Quick one for anyone whose agent texts the owner or the caller after a call. In my Twilio logs I found 23 texts that never went out between February and June, while my n8n workflow showed them as sent. All of them failed with error 30044. My account was still a trial, and trial accounts refuse texts that are too long. 10 of them also had a long dash, and one character like that makes each part of the text hold 67 characters instead of 153. For an agent whose whole job is to text the owner about an urgent call, a text that fails without anyone noticing is about the worst bug it can have. So my templates use plain characters only now, and I check the delivery status in Twilio rather than trusting the workflow. Has anyone else found failures like this long after they happened?
If your voice agent sends a follow-up text, check this
0 likes • 12h
@Daniel Gauerke Curly quotes are a good catch, especially when the model writes part of the text. A plain-character swap right before sending is a lot more reliable than asking the model to avoid them.
0 likes • 12h
@Brendan Jowett Thanks! The delivery check is going into every workflow that sends a text from now on.
My demo agent would have asked a gas leak caller for their address first
I build phone agents for plumbing and HVAC shops, and last month I found a hole in my own demo prompt. The flow was intake first: name, address, callback number, what's going on. Then fixed keywords like "gas smell" or "sewage backing up" would trigger an urgent text to the owner. Then I was reading through an open-source intake template for contractors and saw they put one step before everything else. If the caller mentions a gas smell or a CO alarm, or anything electrical that's sparking or wet, the agent drops the intake and tells them to get out and call 911. Before it even asks for a name. Mine didn't have that. Someone smelling gas would have been asked to spell their street name. I added it as step 0 and checked the live prompt through the Retell API after the update to make sure it was really there. What safety rules do you put in your agents before the intake starts?
0 likes • 2d
@Brendan Jowett Active fires wasn't on my list, so that one is going in. Good to know about prompts not updating properly, I'll keep checking through the API after every edit.
How I Got 1M Views in 24 Hours (Claude + Instagram)
This video shows you how to build a multi-agent Claude system that finds viral topics, writes scripts, edits Instagram Reels with captions and motion graphics, and posts them as trial reels automatically. Step by step tutorial using Claude Code and Treg MCP to connect to Instagram's official API without touching the Meta developer setup. You'll learn how to A/B test multiple hooks and editing styles by uploading dozens of variations as trial reels, then use ManyChat to auto DM links to commenters. This is the exact same system that got me 1 million views on Instagram in 24 hours. Check it out!! 👇
0 likes • 3d
The trial reels part is what I want to try. Did you ever test reels with no face at all, just motion graphics and text, against your face-cam ones? I make my videos fully in code and I'm curious if trial reels give them a fair shot.
1-10 of 40
Haris Folas
5
221 points to level up
@haris-folas-7445
Finished high school at 13. Won a Retell AI hackathon at 15. Now founder of DICSIO, Head of AI Systems at Autaline. Building, not learning.

Active 6h ago
Joined Dec 1, 2025
Powered by