<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Venkatesh Prasanna</title>
    <description>The latest articles on Forem by Venkatesh Prasanna (@venkatesh_prasanna_d).</description>
    <link>https://forem.com/venkatesh_prasanna_d</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1594920%2Fe8e50b48-10fa-419d-9f9d-aa363efde284.jpg</url>
      <title>Forem: Venkatesh Prasanna</title>
      <link>https://forem.com/venkatesh_prasanna_d</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/venkatesh_prasanna_d"/>
    <language>en</language>
    <item>
      <title>Silent Spend Tracker – A Non-Conversational Agent for Automatic Daily Expense Totals</title>
      <dc:creator>Venkatesh Prasanna</dc:creator>
      <pubDate>Fri, 09 Jan 2026 04:20:42 +0000</pubDate>
      <link>https://forem.com/venkatesh_prasanna_d/silent-spend-tracker-a-non-conversational-agent-for-automatic-daily-expense-totals-5h43</link>
      <guid>https://forem.com/venkatesh_prasanna_d/silent-spend-tracker-a-non-conversational-agent-for-automatic-daily-expense-totals-5h43</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/algolia"&gt;Algolia Agent Studio Challenge&lt;/a&gt;: Consumer-Facing Non-Conversational Experiences&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;Silent Spend Tracker is a &lt;strong&gt;non-conversational AI agent&lt;/strong&gt; that automatically calculates &lt;strong&gt;day-wise spending totals&lt;/strong&gt; from transaction SMS messages.&lt;/p&gt;

&lt;p&gt;In real life, users receive multiple SMS alerts for every transaction made through PhonePe, Google Pay, Paytm, UPI, or net banking. While these messages contain all the information, it is scattered, unorganized, and difficult to track daily spending without manual effort.&lt;/p&gt;

&lt;p&gt;This agent removes the need for apps, typing, or conversation. It works silently in the background and presents &lt;strong&gt;clear daily totals automatically&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;No prompts.&lt;br&gt;&lt;br&gt;
No chat.&lt;br&gt;&lt;br&gt;
No manual entry.&lt;/p&gt;




&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;Demo / Prototype link:&lt;br&gt;&lt;br&gt;
( add your GitHub, mockup, or placeholder link here )&lt;/p&gt;

&lt;p&gt;Example workflow:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Transaction SMS arrives (UPI / bank / wallet)&lt;/li&gt;
&lt;li&gt;Agent detects sender and amount automatically&lt;/li&gt;
&lt;li&gt;Transaction is parsed and indexed&lt;/li&gt;
&lt;li&gt;Daily totals update instantly&lt;/li&gt;
&lt;li&gt;User opens the dashboard and sees:

&lt;ul&gt;
&lt;li&gt;Today’s total spend&lt;/li&gt;
&lt;li&gt;Yesterday’s spend&lt;/li&gt;
&lt;li&gt;Weekly overview&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;This entire flow happens without user interaction.&lt;/p&gt;




&lt;h2&gt;
  
  
  How I Used Algolia Agent Studio
&lt;/h2&gt;

&lt;p&gt;Algolia Agent Studio is used to orchestrate the &lt;strong&gt;automatic ingestion and retrieval&lt;/strong&gt; of transaction data.&lt;/p&gt;

&lt;p&gt;Parsed SMS data such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Amount&lt;/li&gt;
&lt;li&gt;Date&lt;/li&gt;
&lt;li&gt;Payment source (UPI, bank, wallet)&lt;/li&gt;
&lt;li&gt;Merchant reference&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;is indexed into Algolia.&lt;/p&gt;

&lt;p&gt;Agent Studio triggers retrieval automatically whenever new data arrives. Algolia’s fast search and filtering capabilities allow transactions to be grouped by date and source, enabling instant calculation of daily spending totals without any user query.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why Fast Retrieval Matters
&lt;/h2&gt;

&lt;p&gt;This experience depends on immediacy and clarity. Users expect to open the app and instantly see their spending summary without delay or interaction.&lt;/p&gt;

&lt;p&gt;Algolia’s fast, contextual retrieval ensures:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Instant aggregation of transactions by day&lt;/li&gt;
&lt;li&gt;Smooth updates as new SMS messages arrive&lt;/li&gt;
&lt;li&gt;A frictionless, non-intrusive user experience&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Because retrieval is fast and automatic, the agent feels invisible yet reliable — exactly what a non-conversational assistant should be.&lt;/p&gt;




&lt;p&gt;Thanks for reviewing my submission!&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>algoliachallenge</category>
      <category>ai</category>
      <category>agents</category>
    </item>
    <item>
      <title>Silent Plumbing Assistant – A Non-Conversational Retail Intelligence Agent</title>
      <dc:creator>Venkatesh Prasanna</dc:creator>
      <pubDate>Fri, 09 Jan 2026 03:40:14 +0000</pubDate>
      <link>https://forem.com/venkatesh_prasanna_d/silent-plumbing-assistant-a-non-conversational-retail-intelligence-agent-37j0</link>
      <guid>https://forem.com/venkatesh_prasanna_d/silent-plumbing-assistant-a-non-conversational-retail-intelligence-agent-37j0</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/algolia"&gt;Algolia Agent Studio Challenge&lt;/a&gt;: Consumer-Facing Non-Conversational Experiences&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;Silent Plumbing Assistant is a &lt;strong&gt;non-conversational, visual-first AI agent&lt;/strong&gt; designed for small retail environments such as hardware and plumbing stores.&lt;/p&gt;

&lt;p&gt;In many real-world retail situations, customers cannot describe what they need because they don’t know English or the technical name of a product. They often rely on gestures, partial words, or showing broken parts. Traditional solutions like search bars or chatbots fail because they require language.&lt;/p&gt;

&lt;p&gt;This agent works &lt;strong&gt;silently and proactively&lt;/strong&gt;. When a retailer opens a category like &lt;em&gt;Plumbing&lt;/em&gt;, the agent automatically retrieves and narrows the most relevant products based on context such as material type (e.g., CPVC), common sizes (¾”, 1”), and typical retail demand. Large, clear product images are displayed so customers can simply &lt;strong&gt;point to the correct item&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;No typing.&lt;br&gt;&lt;br&gt;
No chat.&lt;br&gt;&lt;br&gt;
No English required.&lt;/p&gt;




&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;Demo / Prototype link:&lt;br&gt;&lt;br&gt;
( add your link here – GitHub, Figma, or simple hosted page )&lt;/p&gt;

&lt;p&gt;Example demo flow:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Retailer opens the &lt;em&gt;Plumbing&lt;/em&gt; category
&lt;/li&gt;
&lt;li&gt;The agent auto-retrieves valves and fittings
&lt;/li&gt;
&lt;li&gt;Retailer selects &lt;em&gt;CPVC&lt;/em&gt;
&lt;/li&gt;
&lt;li&gt;The agent prioritizes common sizes like ¾” and 1”
&lt;/li&gt;
&lt;li&gt;Visual results appear instantly
&lt;/li&gt;
&lt;li&gt;Customer points to the needed item and completes the purchase
&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Even a basic mockup or static demo illustrates the core intelligence clearly.&lt;/p&gt;




&lt;h2&gt;
  
  
  How I Used Algolia Agent Studio
&lt;/h2&gt;

&lt;p&gt;Algolia Agent Studio is used as the &lt;strong&gt;orchestration layer&lt;/strong&gt; that decides &lt;em&gt;when&lt;/em&gt; and &lt;em&gt;what&lt;/em&gt; information should appear, without requiring explicit user queries.&lt;/p&gt;

&lt;p&gt;Product data such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Category (plumbing, valves, fittings)&lt;/li&gt;
&lt;li&gt;Material (CPVC, PVC, brass)&lt;/li&gt;
&lt;li&gt;Size (½”, ¾”, 1”)&lt;/li&gt;
&lt;li&gt;Product type (ball valve, handle, fitting)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;is indexed in Algolia.&lt;/p&gt;

&lt;p&gt;When contextual signals occur (for example, a category is opened or a material is selected), the agent triggers retrieval automatically. Algolia’s faceted search and ranking capabilities are used to narrow and prioritize results based on relevance and common demand, transforming a static catalogue into a proactive assistant.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why Fast Retrieval Matters
&lt;/h2&gt;

&lt;p&gt;This experience depends on &lt;strong&gt;instant response&lt;/strong&gt;. In a retail environment, even small delays break the flow between the retailer and the customer.&lt;/p&gt;

&lt;p&gt;Algolia’s fast, contextual retrieval ensures that:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Results appear immediately when context changes
&lt;/li&gt;
&lt;li&gt;Product narrowing feels natural and effortless
&lt;/li&gt;
&lt;li&gt;The agent enhances the workflow instead of interrupting it
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Because retrieval is fast and precise, the agent feels invisible yet helpful — which is essential for a non-conversational experience.&lt;/p&gt;




&lt;p&gt;Thanks for reviewing my submission!&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>algoliachallenge</category>
      <category>ai</category>
      <category>agents</category>
    </item>
  </channel>
</rss>
