Local businesses rarely lose customers because they're bad at what they do. They lose them because the phone rings while they're mid-cut, mid-massage or up a ladder, and by the time they call back, that customer has booked with the next name on Google.
That's the problem subba is built for. It's an AI receptionist and booking system for local businesses: it answers website chats and contact forms in seconds (and phone calls, with the phone add-on), books people into the real diary and takes the deposit, in the owner's own voice.
We launched here a couple of weeks ago. Since then we've shipped ready-made setups for 54 trades, class timetables and a referral programme. Here are five things building it has taught me.
1. Nobody wants "an AI". They want the interruption gone.
subba is the AI receptionist and booking system for local businesses. It answers every enquiry in seconds, books customers into your diary, and takes payment, in your voice. We can even build your booking website and domain, live in 5 working days.
The web was built for human eyes. Now the "customer" is increasingly an AI agent that can't read your layout, guesses at your forms, and renders a whole page just to find one price.
Google AP2 (Agent Payments Protocol) - mandate-based, 60+ partners (Mastercard, PayPal, Amex), now handed to the FIDO Alliance.
If you run a store, this should feel familiar. It's the "build a separate app for every assistant" trap. IE vs Netscape. A native app per platform. Do you now integrate ACP and AP2 and MCP and whatever Amazon ships next quarter - and re-do it every time a new agent shows up?
