Enhance intent handling by adding transaction_type support

- Updated the chat_with_session_memory function to include transaction_type in the system message, improving clarity on user intentions.
- Modified the extract_and_update_intent function to incorporate transaction_type into the intent fields and added normalization guidelines for this field.
- Updated the database schema to include transaction_type in the user_intents table, ensuring proper data storage and retrieval.
- Added a migration script to safely add the transaction_type column if it doesn't already exist, maintaining database integrity.

ai_chat.py

@@ -70,6 +70,8 @@ def chat_with_session_memory(state):
             f"\n\nUser's property search preferences (only mention if relevant to conversation):\n"
             f"- Location: {intent_data.get('location_preference','[not set]')}\n"
         )
+        if intent_data.get('transaction_type'):
+            system_message += f"- Looking to: {intent_data.get('transaction_type')}\n"
         if intent_data.get('budget'):
             system_message += f"- Budget: {intent_data.get('budget')} per month\n"
         if intent_data.get('size_preference_sqm'):
@@ -228,7 +230,7 @@ async def extract_and_update_persona(state):
 
 async def extract_and_update_intent(state):
     print("DEBUG - Starting extract_and_update_intent")
-    intent_fields = ["location_preference", "budget", "size_preference_sqm", "must_have"]
+    intent_fields = ["location_preference", "budget", "size_preference_sqm", "must_have", "transaction_type"]
     user_message = state["user_message"]
     session_id = state["session_id"]
     intent = state.get("intent", {})
@@ -242,6 +244,7 @@ async def extract_and_update_intent(state):
     - Budget: {intent.get('budget', 'Not set')}
     - Size: {intent.get('size_preference_sqm', 'Not set')} sqm
     - Must-haves: {intent.get('must_have', [])}
+    - Transaction: {intent.get('transaction_type', 'Not set')}
 
     Instructions:
     1. Normalize abbreviations and common terms:
@@ -253,8 +256,11 @@ async def extract_and_update_intent(state):
        - If adding: Include both existing and new items in the array
        - If changing: Replace with new requirements
        - If clarifying: Update with more specific versions
-    3. If the user is asking a definition or clarification (e.g. 'What does square metre mean?'), answer that question fully and do not update the intent.
-    4. Return only a JSON object with keys {intent_fields}, using null for unknown.
+    3. For transaction_type field: Normalize to either 'lease' or 'buy':
+       - 'rent', 'rental', 'lease', 'leasing', 'to rent' → 'rent'
+       - 'buy', 'purchase', 'buying', 'sale', 'for sale', 'to buy' → 'buy'
+    4. If the user is asking a definition or clarification (e.g. 'What does square metre mean?'), answer that question fully and do not update the intent.
+    5. Return only a JSON object with keys {intent_fields}, using null for unknown.
     """
 
     response = await llm.ainvoke([{"role":"user","content":extraction_prompt}])
@@ -425,6 +431,10 @@ Examples of search_listings (user explicitly asking for properties):
 - "Show me properties"
 - "What do you have available?"
 - "I'm looking for properties in Cape Town"
+- "I want to rent a warehouse in Johannesburg"
+- "Looking to buy office space in Sandton"
+- "Do you have any rentals available?"
+- "What's for sale in Cape Town?"
 
 Examples of other (NOT property searches):
 - "Hi" → other

database.py

@@ -262,6 +262,7 @@ async def get_or_create_user_intent(session_id: str, wa_id: str) -> dict:
         "budget":              None,
         "size_preference_sqm": None,
         "must_have":           None,
+        "transaction_type":    None,
         "created_at":          datetime.utcnow().isoformat(),
         "updated_at":          datetime.utcnow().isoformat()
     }

supabase_setup.sql

@@ -43,10 +43,20 @@ CREATE TABLE IF NOT EXISTS user_intents (
     budget INTEGER,
     size_preference_sqm INTEGER,
     must_have TEXT[],
+    transaction_type TEXT CHECK (transaction_type IN ('rent', 'buy')),
     created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW(),
     updated_at TIMESTAMP WITH TIME ZONE DEFAULT NOW()
 );
 
+-- Migration: Add transaction_type column to existing user_intents table (if it doesn't exist)
+DO $$ 
+BEGIN
+    IF NOT EXISTS (SELECT 1 FROM information_schema.columns 
+                   WHERE table_name = 'user_intents' AND column_name = 'transaction_type') THEN
+        ALTER TABLE user_intents ADD COLUMN transaction_type TEXT CHECK (transaction_type IN ('rent', 'buy'));
+    END IF;
+END $$;
+
 -- Create properties table for property listings
 CREATE TABLE IF NOT EXISTS properties (
     id UUID PRIMARY KEY DEFAULT gen_random_uuid(),