3
3 Comments

I built a voice AI that answers phone calls and remembers every caller

I got tired of seeing small businesses miss calls, so I built Vokio.

It answers real phone calls, remembers the caller's name and emotional state between calls, and generates a post-call summary with urgency score and required action.

The interesting part is the memory system. Each call queries SQLite by phone number and injects the caller's history into Claude's system prompt. If the caller was frustrated last time, the agent knows and adjusts its tone.

Stack: Python + Flask + Vapi + Claude + SQLite

Post-call analysis runs automatically when the call ends. The business gets: summary, urgency 1-5, sentiment, action required.

Packaged it as a ready-to-deploy template with 6 business sector prompts included (dental clinic, restaurant, hair salon, real estate, auto shop, hostel).

Happy to answer questions about the architecture.

https://kitbot.gumroad.com/l/vokio

on May 11, 2026
  1. 2

    This is a strong product angle.

    The memory layer is the part that makes it more interesting than a basic AI receptionist. If the agent remembers caller history, sentiment, urgency, and adjusts tone on the next call, the product is not just answering phones. It is becoming a customer memory layer for small businesses.

    One thing I’d watch is the name.

    Vokio sounds clean, but it mostly signals voice. The stronger long-term value here is not voice itself. It is remembered context, trust, and better follow-up across customer calls.

    If you turn this from a template into a real SaaS product, a softer trust-based .com like Lyriso.com would probably fit the direction better. It feels more human and service-friendly, which matters for clinics, salons, restaurants, and local businesses.

    1. 2

      Thanks for the feedback on the name — that reframe is interesting. "Customer memory layer" is actually a better description of what makes it useful than "voice AI." The voice part is just the interface. I'll think about how to position that more clearly. For now keeping Vokio since it's already live, but the long-term direction is definitely more about context persistence than call handling.

      1. 1

        That makes sense.

        If Vokio is already live, I wouldn’t force a name change before you’ve proven the motion.

        But I’d definitely start shifting the positioning now.

        “Voice AI” gets you compared to every AI receptionist tool. “Customer memory layer” makes the product feel more durable because it points to what compounds over time: caller history, context, urgency, preferences, and better follow-up.

        Even if the name stays Vokio for now, I’d make the first line carry that broader direction.

        Something like:

        Vokio helps small businesses remember every caller, not just answer every call.

        That feels much closer to the actual value.

Trending on Indie Hackers
I've been building for months and made $0. Here's the honest psychological reason — and it's not what I expected. User Avatar 177 comments 7 years in agency, 200+ B2B campaigns, now building Outbound Glow User Avatar 73 comments This system tells you what’s working in your startup — every week User Avatar 53 comments 11 Weeks Ago I Had 0 Users. Now VIDI Has Reviewed $10M+ in Contracts - and I’m Opening a Small SAFE Round User Avatar 46 comments The "Book a Demo" Button Was Killing My Pipeline. Here's What I Replaced It With. User Avatar 35 comments My AI bill was bleeding me dry, so I built a "Smart Meter" for LLMs User Avatar 18 comments