Arnav Sharma (@arnavshr09) header
Arnav Sharma (@arnavshr09) profile picture

Software Engineer building AI agents and automations. I share what actually works, including what doesn't. Stay tuned :)

Joined September 2021
the sms piece is where 3 days turns into 3 weeks. a2p registration, carrier filtering, opt-outs. the code is the easy part, the carriers aren't. that's honestly the main thing i'd still pay a platform for
Wife: at a conference Son: at the grandparents Me, alone for the first time since March: ✅ Built a custom CRM ✅ Built an underwriting tool that scary good ✅ Built a voice AI agent ✅ Replaced my SMS platform with a custom solution 3 days. I was supposed to be relaxing.
7 brands to 20 in 3 years means 20 phone setups and 20 ways of handling a missed call. i build forecasting for cleaning franchises and the multi-location mess is real. highlevel's field services beta is pitched at exactly this, curious if anyone's run it across brands yet
Permira agreed to buy a majority stake in Flint Group from General Atlantic for more than $1.5B. Flint does residential HVAC, plumbing and electrical in the US, 20 regional brands across 15 states. When General Atlantic bought in during 2023 it was 7 brands in 5 states. So the roll-up almost tripled in about 3 years and the next buyer is a bigger fund. Sponsors were 60.5% of residential services M&A through late July, per Dealroom. 20 brands usually means a lot of different dispatch, scheduling, CRM and billing setups that need to sit on something shared before the next diligence team looks. We've done roofing lead conversion projects and HVAC ecom for parts and mechanics. CRMs hide various leaks and teams tend to lack the clarity and direction they need. And for a restoration hold co, integrating 20+ brands led to trimming support, content, maintenance by 70% across the board, plus running a franchise-like model instead, with faster velocity cycles and faster systems as well. The roll up and franchise game is something we've done since the Audi project in 2014 building a network of 400 DACH partners under the same roof for the VW group and then 160+ escape room franchise system after. The same principles are valid today (and we still work with the latter). dealroom.co/news/169970-perm…
Before you pay for an AI receptionist, run one test. It takes 2 minutes. Call the business number from your own phone. Let it ring out. Hang up. Then watch what actually happens. Does a text come back, and how fast? Mine took 41 seconds. Does a contact show up in the CRM, or nowhere? If it says it "books appointments", is there an event in the calendar, or did it just text a link? Who on the team sees it, and when? Most of the people posting about this are selling the tool. The test is free. What happened when you tried yours?
1
1
same risk one level down for anyone building client automations. a highlevel api key or a twilio token in a repo is a client's whole phone line. the check i'd run before every push: search the diff for "key", "token" and "sk-"
Tap "Yes, and don't ask again" in Claude Code and it saves that approval in a file inside your project. If the command had a password in it, the password is saved too. Claude Code's docs say the file is meant to stay local. But the rule that keeps it out of git lives on your computer, not in the project, so a fresh clone or a fork treats it like any other file. Apiiro, a security firm, says it found 1,122 public copies on GitHub holding real secrets, and in 539 of the repos it traced, Claude co-authored the commit that changed the file. Then there's William Baude, a law professor who asked Claude to update page numbers in old lecture notes and went to lunch. He came back to a year of notes and his syllabus deleted. Dropbox had copies. Making agents behave in moments like these was one of the stated aims of Microsoft's AI Frontiers lab. It became part of Microsoft AI in September, and this week John Langford, who worked there, posted "The End of AI Frontiers." Neither Claude story looks like it needs a smarter model to fix. Both need the plain work around the model. "Don't ask again" was meant to save a click, and this week showed what it costs when nobody asks. What would you all like to learn about next? Reply with a number or ask your own question: 1. How do secret scanners spot a leaked password, and why do ones typed into a command slip past them? 2. Is committing a local settings file user error, or should coding agents ship safer defaults? 3. Before AI agents, how did passwords end up in public GitHub repos, and how fast are they found? 4. What would a real undo button for AI agents need to cover, from files to email to payments? 5. Why do big AI companies bet on scaling today's models over funding research into other ideas?
1
5
where it isn't that easy for me: client automations. it can build a missed-call flow in minutes. it can't know the flow fires on the owner's own test calls until someone actually rings the number. the fast part is real, the checking part is still yours
Claude Code few-shots anything I can think of (software, process automation, docs, design, marketing content, literally anything…better than any employees I ever had. My gut-feeling says it can’t be so easy, Either I’m just dreaming and I’ll wake up or data centers get bombed or governments shut down citizen ai or idk, this can’t be real
1
A developer posted his year under a thread about AI slop. January, 80% of his code written by hand. July, 99% by AI. September, 100%. November, 2 months into fixing the slop. AI made shipping free. It didn't make fixing free. Same with client automations. A workflow takes 20 minutes to build now. The text that goes to the wrong person costs you the client. Do you still ship fast and fix later, or has AI made you slower on purpose?
12
Every missed-call text-back post this week says the same thing: speed is the whole product. Speed is step one. My first HighLevel build taught me a few more. The trigger doesn't exist until you buy a number inside HighLevel. $1.15 a month, and no error if you skip it. The words matter. My clever version read like a bot. "Sorry we missed your call, this is [business]. What can we help with?" reads like someone who was busy. It fires on your own test calls. An owner checking their own line gets texted by their own business. And it's worth nothing if the reply lands somewhere nobody looks. 41 seconds from hang-up to text in my test. What does yours say?
1
11
for a home service call the valuable moment is the read-back. the time window, the address, the rough price. the caller hears it, says yes, and nobody's standing at the wrong door on tuesday. a prettier voice doesn't do that
Last month, we had 30,000+ hours of conversation. Yes, 30 thousand. I’m the only engineer working on voice ai at @boardyai and here's what I'm noticing across the industry. In the race for faster responses and more natural voices, I think we’re losing sight of what makes a conversation actually valuable. Helping someone understand. Sometimes that takes more than words. It takes something you can see, point at, question, and explore together. That’s where I see conversational ai heading, and where I’m taking voice at Boardy.
16
the test your replies already raised is the real one. 2am in january, furnace out. does it book the job, page the on-call tech, or just take a message? the cloned voice is the fun part. the after-hours routing is what the business pays for
unavailable
9
HighLevel's $497 Agency Pro plan is now the Founder plan. Their blog made it official today. If you were on $497, here's what comes with the new name, going by what they've announced: SaaS Mode and rebilling, with no cap on your resale markup. Your own logo, domain and custom menus, so clients log into your platform, not theirs. Built-in ticketing, project management and video meetings. Coaching, a founder community, and growth perks like AdFuel. And per their pricing docs, AI Employee at $20 per sub-account, only on Founder. I'm still on the learning side of HighLevel, so the thing I'd check first is whether existing $497 accounts move over automatically. Anyone on $497 seen what changed in their account?
3
2
33
Tonight's most shared AI posts: a prompt that builds "an entire team of AI agents" before bed, and levelsio joking that Web4 is closing your laptop and going outside. Meanwhile the automation that actually makes a cleaning business money is the most boring one there is. A missed call, a text within seconds, a reply that lands in one inbox. No agent team. 3 blocks and a phone number. What's the most boring automation that's made you the most money?
13
If you run HighLevel for a business in Vancouver, Edmonton, Winnipeg or Casablanca, its bookings could be an hour off right now. HighLevel added the new Canada and Morocco time zones today. Vancouver is now permanent UTC-7, Edmonton UTC-6, Winnipeg UTC-5, Casablanca UTC+0. The catch: nothing switches by itself. Existing contacts and settings stay on the US zones they were using, because US businesses use those zones too. So someone has to move 2 things by hand. The business profile time zone for each location. The time zone on every contact still sitting on a US stand-in like America/Los_Angeles. Same drop: Conversation AI can now be connected to an AI Studio site's live chat from settings, and AI Studio Payments lost its 100-product cap. Got any Canadian clients on HighLevel?
1
1
2
59
the part i'd want covered in any "voice ai sales team" session: the call the ai can't close. who it hands to, how fast, and whether that person sees what was already said. from what i've seen that handoff is where the lead goes cold
1
19
levelsio says he's blocking about 50 AI reply accounts a day. Same hour, Greg Isenberg posted how he runs Grok Bot: one bot per job, daily routines, a chief of staff on top. I run my scouting the second way. A bot finds fresh HighLevel posts and watches the changelog for launches. Nothing goes out under my name without me reading it first. The spam is what you get when one bot does everything, including the talking. Would you let an AI reply under your name, or only let it find things for you?
10
for a local business the "ai profit machine" usually starts smaller than people think. my first build was a missed-call text-back, 3 blocks and a $1.15 number. a lot of the profit is just the calls nobody was answering
7
Most AI receptionists are being set up as the first thing a caller hears. I think that's the wrong place to start. A regular at a salon wants the person who knows them. A bot doesn't know that Sarah always books the 4pm slot, or that the owner stepped out for 5 minutes. Where it earns its place is overflow: After hours. Mid-job, when nobody can pick up. When the line's busy. "Are you open Sunday?" at 9pm. And the simplest version isn't even a voice agent. It's a missed-call text back: "Sorry we missed you, what do you need?" The reply lands in one inbox and someone calls back within the hour. Would you rather a bot answer first, or only when nobody else can?
1
12
what i'd want benchmarked next, from the small business side: does it hand off to a human cleanly, does the booking actually land in the calendar, and does it hold up when the caller's on speaker in a van
Introducing Cekura Bench: the world’s leading Voice AI Benchmarks We benchmarked 50+ models from openAi, Google, Nvidia, xAI, Inworld, Gradium, Assembly, Fish audio and more Now you can: → Compare naturalness, performance and cost → See how the best voice agents are being built. → Find the best fit for what you are building. Our tests cover Speech-to-Speech models, Speech-to-Text models, Text-to-Speech Models, and Voice Agent platforms. We recorded real humans doing tasks in different domains and created the most representative voice benchmark out there! Explore the benchmarks: benchmarks.cekura.ai We would love to collaborate with more teams on these benchmarks. Reach out if you are interested.
6
none of these is what a cleaning or hvac owner buys directly. they buy whatever their agency or highlevel runs. of the 3 tests, "never talks over the caller" is the one i'd weight most on a missed-call line. people calling a tradesman are usually already annoyed
VOICE AI SOUNDS GREAT IN DEMOS, BUT FALLS APART WHEN A REAL PERSON CALLS Cekura benchmarked 10 voice agent platforms against real human conversations and in 1000+ scenarios. same agent. same calls for every platform. PolyAI came out on top. → most reliable: @PolyAI → never talks over the caller: @retellai → fastest to answer, most natural voice: @elevenlabsio every recording is public, check the scores in the video.
6
Most AI receptionists are being set up as the first thing a caller hears. I think that's the wrong place to start. A regular at a salon wants the person who knows them. A bot doesn't know that Sarah always books the 4pm slot, or that the owner stepped out for 5 minutes. Where it earns its place is overflow: After hours. Mid-job, when nobody can pick up. When the line's busy. "Are you open Sunday?" at 9pm. And the simplest version isn't even a voice agent. It's a missed-call text back: "Sorry we missed you, what do you need?" The reply lands in one inbox and someone calls back within the hour. Would you rather a bot answer first, or only when nobody else can?
1
1
16
what i'd want benchmarked next, from the small business side: does it hand off to a human cleanly, does the booking actually land in the calendar, and does it hold up when the caller's on speaker in a van
Introducing Cekura Bench: the world’s leading Voice AI Benchmarks We benchmarked 50+ models from openAi, Google, Nvidia, xAI, Inworld, Gradium, Assembly, Fish audio and more Now you can: → Compare naturalness, performance and cost → See how the best voice agents are being built. → Find the best fit for what you are building. Our tests cover Speech-to-Speech models, Speech-to-Text models, Text-to-Speech Models, and Voice Agent platforms. We recorded real humans doing tasks in different domains and created the most representative voice benchmark out there! Explore the benchmarks: benchmarks.cekura.ai We would love to collaborate with more teams on these benchmarks. Reach out if you are interested.
10