How I Built a WhatsApp AI Assistant for a SA Salon - And What It Taught Me About

<p><strong>TL;DR:</strong> I run WhatsApp automation workflows for 50+ businesses on shared infrastructure using n8n (queue mode), WAHA (unofficial WhatsApp Web API), Supabase,

<p>Most developers underestimate how hard voice AI actually is.</p> <p>To build a production-ready calling agent, you need to integrate:</p> <p>– SIP signalling</p> <p>– Real-time

<p>A website chatbot can answer questions, but what happens after the conversation ends?</p> <p>Does the business know who was interested? Can the team review what the visitor

<p>Most booking systems for salons look the same: pick a date, pick a time, pick a service, fill in your name, confirm. Five steps minimum.<br /> I wanted to build something

<p>I build WhatsApp automation for small businesses, and in 2026 the first thing you notice about the market is how similar every offer looks. A dozen vendors, the same promises —

<!-- SC_OFF --><div class="md"><p>Everyone told us it was a bad idea.</p> <p>“Customers want instant booking. They don’t want to chat. You’ll lose them.”</p> <p>We tested it

<p>We shipped our first AI features in late 2025, long after many other companies who built RAG chatbots starting in early 2023. That sounds late, but I don't think it is. It's a

<h1> Here's the thing nobody tells you about WhatsApp automation: the hard part was never the AI, and it was never the German. It was WhatsApp itself. </h1> <p>I wanted something