Saathi: building a Kirana store voice agent in 10 days with Murf Falcon published: true tags: voiceai, python, webdev, beginners
How I built a Hinglish-speaking voice assistant for local grocery stores — and what ten days of #VoiceForBharat taught me about voice AI. The problem and the users Most local Kirana (neighbourhood grocery) stores in India still run on phone calls and memory. The shopkeeper remembers what Ramesh usually orders, but there's no system behind that memory — no record of preferences, no way to check…
A voice assistant was created to help local grocery stores in India called Saathi. These stores rely heavily on phone calls and memory, which can be unreliable for customers who prefer talking over typing. The assistant is designed to accommodate customers who are more comfortable speaking in Hinglish (a mix of Hindi and English) and for store owners who need help managing routine calls without pretending to be human.
The assistant can engage in natural conversations in English, Hindi, or Hinglish, greet returning customers by name, recall their last order, check live stock before promising anything, place orders, confirm them back to the customer, and escalate issues to the store owner when necessary. It also proactively calls customers to confirm orders, handles payment disputes and refunds, and logs outcomes for analytics.
The assistant's core functionality involves real-time speech-to-text conversion, reasoning, and text-to-speech conversion using Deepgram STT and Murf Falcon TTS. It uses Google Gemini LLM as its reasoning engine, equipped with persona, guardrails, and tool-calling logic. The assistant's data is stored in a SQLite database, and it can transfer conversations to a specialist agent when needed.
The assistant is built to work seamlessly over a LiveKit room, accommodating both browser and phone channel inputs. It prioritizes accuracy and transparency in its interactions, ensuring that customers are always aware of when they are talking to an automated system.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.