dhisana 0.0.1.dev85__py3-none-any.whl → 0.0.1.dev236__py3-none-any.whl

dhisana/utils/generate_email_response.py

@@ -1,14 +1,14 @@
-import base64
 import datetime
 from typing import Any, Dict, List, Optional
-import aiohttp
 from pydantic import BaseModel
 
 from dhisana.schemas.sales import (
     ContentGenerationContext,
+    Lead,
     MessageItem,
     MessageResponse,
-    MessageGenerationInstructions
+    MessageGenerationInstructions,
+    SenderInfo
 )
 from dhisana.utils.assistant_tool_tag import assistant_tool
 from dhisana.utils.generate_structured_output_internal import (
@@ -22,15 +22,16 @@ from dhisana.utils.generate_structured_output_internal import (
 class InboundEmailTriageResponse(BaseModel):
     """
     Model representing the structured response for an inbound email triage.
-    - triage_status: "AUTOMATIC" or "REQUIRES_APPROVAL"
-    - triage_reason: Reason text if triage_status == "REQUIRES_APPROVAL"
+    - triage_status: "AUTOMATIC" or "END_CONVERSATION"
+    - triage_reason: Reason text if triage_status == "END_CONVERSATION"
     - response_action_to_take: The recommended next action (e.g. SCHEDULE_MEETING, SEND_REPLY, etc.)
     - response_message: The actual body of the email response to be sent or used for approval.
     """
-    triage_status: str  # "AUTOMATIC" or "REQUIRES_APPROVAL"
+    triage_status: str  # "AUTOMATIC" or "END_CONVERSATION"
     triage_reason: Optional[str]
     response_action_to_take: str
-    response_message: str
+    response_message: Optional[str]
+    meeting_offer_sent: Optional[bool]
 
 
 # ---------------------------------------------------------------------------------------
@@ -38,14 +39,180 @@ class InboundEmailTriageResponse(BaseModel):
 # ---------------------------------------------------------------------------------------
 def cleanup_reply_campaign_context(campaign_context: ContentGenerationContext) -> ContentGenerationContext:
     clone_context = campaign_context.copy(deep=True)
-    clone_context.lead_info.task_ids = None
-    clone_context.lead_info.email_validation_status = None
-    clone_context.lead_info.linkedin_validation_status = None
-    clone_context.lead_info.research_status = None
-    clone_context.lead_info.enchrichment_status = None
+    if clone_context.lead_info is not None:
+        clone_context.lead_info.task_ids = None
+        clone_context.lead_info.email_validation_status = None
+        clone_context.lead_info.linkedin_validation_status = None
+        clone_context.lead_info.research_status = None
+        clone_context.lead_info.enchrichment_status = None
     return clone_context
 
 
+# ---------------------------------------------------------------------------------------
+# GET INBOUND EMAIL TRIAGE ACTION (NO EMAIL TEXT)
+# ---------------------------------------------------------------------------------------
+async def get_inbound_email_triage_action(
+    context: ContentGenerationContext,
+    tool_config: Optional[List[Dict]] = None
+) -> InboundEmailTriageResponse:
+    """
+    Analyzes the inbound email thread, and triage guidelines
+    to determine triage status, reason, and the recommended action to take.
+    DOES NOT generate the final email text.
+    """
+    allowed_actions = [
+        "UNSUBSCRIBE",
+        "NOT_INTERESTED",
+        "SCHEDULE_MEETING",
+        "SEND_REPLY",
+        "OOF_MESSAGE",
+        "NEED_MORE_INFO",
+        "FORWARD_TO_OTHER_USER",
+        "NO_MORE_IN_ORGANIZATION",
+        "OBJECTION_RAISED",
+        "END_CONVERSATION",
+    ]
+    current_date_iso = datetime.datetime.now().isoformat()
+    cleaned_context = cleanup_reply_campaign_context(context)
+    if not cleaned_context.current_conversation_context.current_email_thread:
+        cleaned_context.current_conversation_context.current_email_thread = []
+    
+    if not cleaned_context.campaign_context.email_triage_guidelines:
+        cleaned_context.campaign_context.email_triage_guidelines = "No specific guidelines provided."
+
+    triage_prompt = f"""
+        You are a specialized email assistant.                          
+        Your task is to analyze the inbound email thread and the triage
+        guidelines below to determine the correct triage action.
+
+        allowed_actions = 
+        {allowed_actions}
+
+        1. Email thread or conversation:
+        {[thread_item.model_dump() for thread_item in cleaned_context.current_conversation_context.current_email_thread]}
+
+        2. Triage Guidelines
+        -----------------------------------------------------------------
+        General flow
+        ------------
+        • If the request is routine, non-sensitive, and clearly actionable  
+        → **triage_status = "AUTOMATIC"**.  
+        • If the thread contains PII, legal, NSFW, or any sensitive content  
+        → **triage_status = "END_CONVERSATION"** and set a short **triage_reason**.
+
+        Meeting & next-step logic
+        -------------------------
+        • Define `meeting_offer_sent` = **true** if **any** prior assistant
+        message in the current thread proposed a call or meeting.
+
+        • **First positive but non-committal reply**  
+        (e.g. “Thanks”, “Sounds good”, “Will review”) **AND**
+        `meeting_offer_sent` is **false**  
+        → **SEND_REPLY** asking for a 15-min call, ≤ 150 words, friendly tone.  
+
+        • **Second non-committal reply** or “Will get back” **after**
+        `meeting_offer_sent` already true  
+        → **END_CONVERSATION** (stop the thread unless the prospect re-engages).
+
+        • If the prospect explicitly **asks for times / suggests times /
+        requests your scheduling link**  
+        → **SCHEDULE_MEETING** and include a concise reply that
+        (a) confirms time or provides link,  
+        (b) thanks them, and  
+        (c) ends with a forward-looking statement.
+
+        Handling interest & objections
+        ------------------------------
+        • If the prospect asks for **pricing, docs, case studies, or more info**  
+        → **NEED_MORE_INFO** and craft a short response that promises to send
+            the material (or includes it if ≤ 150 words fits).
+
+        • If they mention **budget, timing, or competitor concerns**  
+        → **OBJECTION_RAISED** and reply with a brief acknowledgement
+            + single clarifying question or value statement.
+
+        • If they request to loop in a colleague (“Please include Sarah”)  
+        → **FORWARD_TO_OTHER_USER** and draft a one-liner tee-up.
+
+        Priority order for immediate triage
+        -----------------------------------
+        1. “Unsubscribe”, “Remove me”, CAN-SPAM language → **UNSUBSCRIBE**  
+        2. Explicit lack of interest → **NOT_INTERESTED**  
+        3. Auto OOO / vacation responder → **OOF_MESSAGE**  
+        4. Explicit request to meet / suggested times → **SCHEDULE_MEETING**  
+        5. Prospect asks questions or raises objection → as per rules above  
+        6. Apply “Meeting & next-step logic”  
+        7. Default → **END_CONVERSATION**
+
+        Reply style (when SEND_REPLY or SCHEDULE_MEETING)
+        -------------------------------------------------
+        • Max 150 words, clear single CTA, no jargon.  
+        • Start with a thank-you, mirror the prospect’s language briefly, then
+        propose next step or answer question.  
+        
+        If you have not proposed a meeting even once in the thread, and the user response is polite acknowledgment then you MUST request for a meeting.
+         
+        • Meeting ask template (use *exact* placeholder, will be filled later):
+        Hi {{first_name}}, would you be open to a quick 15-min call to
+        understand your use-case and share notes?
+
+        • Competitor-stack mention template:
+        Hi {{first_name}}, thanks for sharing your current stack. Would you be
+        open to a 15-min call to explore where we can add value?
+        
+       
+
+        Custom triage guidelines provided by the user. This takes precedence over above guidelines:
+        {cleaned_context.campaign_context.email_triage_guidelines}
+        
+        Guard-rails
+        -----------
+        • Only one unsolicited follow-up per thread. If no response, stop.  
+        • Never disclose PII/financial data; instead **END_CONVERSATION**.  
+        • Stay friendly, concise, and on topic.
+
+
+        Required JSON output
+        --------------------
+        {{
+        "triage_status": "...",
+        "triage_reason": null or "<reason>",
+        "response_action_to_take": "one of {allowed_actions}",
+        "response_message": "<only if SEND_REPLY/SCHEDULE_MEETING, else empty>"
+        }}
+
+        Current date is: {current_date_iso}.
+        -----------------------------------------------------------------
+        """
+
+
+    # If there's a vector store ID, use that approach
+    if (
+        cleaned_context.external_known_data
+        and cleaned_context.external_known_data.external_openai_vector_store_id
+    ):
+        triage_only, status = await get_structured_output_with_assistant_and_vector_store(
+            prompt=triage_prompt,
+            response_format=InboundEmailTriageResponse,
+            model="gpt-5.1-chat",
+            vector_store_id=cleaned_context.external_known_data.external_openai_vector_store_id,
+            tool_config=tool_config,
+            use_cache=cleaned_context.message_instructions.use_cache if cleaned_context.message_instructions else True
+        )
+    else:
+        triage_only, status = await get_structured_output_internal(
+            prompt=triage_prompt,
+            response_format=InboundEmailTriageResponse,
+            model="gpt-5.1-chat",
+            tool_config=tool_config,
+            use_cache=cleaned_context.message_instructions.use_cache if cleaned_context.message_instructions else True
+        )
+
+    if status != "SUCCESS":
+        raise Exception("Error in generating triage action.")
+    return triage_only
+
+
 # ---------------------------------------------------------------------------------------
 # CORE FUNCTION TO GENERATE SINGLE RESPONSE (ONE VARIATION)
 # ---------------------------------------------------------------------------------------
@@ -68,54 +235,140 @@ async def generate_inbound_email_response_copy(
         "FORWARD_TO_OTHER_USER",
         "NO_MORE_IN_ORGANIZATION",
         "OBJECTION_RAISED",
-        "OTHER"
+        "END_CONVERSATION",
     ]
     current_date_iso = datetime.datetime.now().isoformat()
     cleaned_context = cleanup_reply_campaign_context(campaign_context)
     if not cleaned_context.current_conversation_context.current_email_thread:
         cleaned_context.current_conversation_context.current_email_thread = []
+    
+    lead_data = cleaned_context.lead_info or Lead()
+    sender_data = cleaned_context.sender_info or SenderInfo()
 
     prompt = f"""
-    You are a specialized email assistant. 
-    Your task is to analyze the user's email thread, the user/company info,
-    and the provided triage guidelines to craft a response.
+        You are a specialized email assistant. 
+        Your task is to analyze the user's email thread, the user/company info,
+        and the provided triage guidelines to craft an appropriate response.
+
+        Follow these instructions to generate the reply: 
+        {variation}
+
+        1. Email thread or conversation to respond to:
+        {[thread_item.model_dump() for thread_item in cleaned_context.current_conversation_context.current_email_thread] 
+            if cleaned_context.current_conversation_context.current_email_thread else []}
+
+        2)  Lead Information:
+            {lead_data.dict()}
 
-    Follow these instructions to generate the reply: 
-    {variation}
+            Sender Information:
+            Full Name: {sender_data.sender_full_name or ''}
+            First Name: {sender_data.sender_first_name or ''}
+            Last Name: {sender_data.sender_last_name or ''}
+            Bio: {sender_data.sender_bio or ''}
+        
 
-    1. Understand the email thread or conversation to respond to:
-       {[thread_item.model_dump() for thread_item in cleaned_context.current_conversation_context.current_email_thread] if cleaned_context.current_conversation_context.current_email_thread else []}
+        3. Campaign-specific triage guidelines (user overrides always win):
+        {cleaned_context.campaign_context.email_triage_guidelines}
 
-    2. User & Company (Lead) Info:
-       {cleaned_context.model_dump()}
+        -----------------------------------------------------------------
+        Core decision logic
+        -----------------------------------------------------------------
+        • If the request is routine, non-sensitive, and clearly actionable  
+        → **triage_status = "AUTOMATIC"**.  
+        • If the thread contains PII, finance, legal, or any sensitive/NSFW content  
+        → **triage_status = "END_CONVERSATION"** and give a concise **triage_reason**.
 
-    3. Triage Guidelines:
-       {cleaned_context.campaign_context.email_triage_guidelines}
+        4. Choose exactly ONE of: {allowed_actions}
 
-       - If the request is standard, simple, or obviously handled by standard processes,
-         set triage_status to "AUTOMATIC".
-       - If the request is complex, sensitive, or needs special input,
-         set triage_status to "REQUIRES_APPROVAL" and provide triage_reason.
+        -----------------------------------------------------------------
+        Response best practices
+        -----------------------------------------------------------------
+        • MAX 150 words, friendly & concise, single clear CTA.  
+        • Begin with a thank-you, mirror the prospect’s wording briefly, then answer /
+        propose next step.  
+        • Never contradict, trash-talk, or disparage {campaign_context.lead_info.organization_name}.  
+        • Plain-text only – NO HTML tags (<a>, <b>, <i>, etc.).  
+        • If a link already exists in the inbound email, include it verbatim—do not re-wrap or shorten.
 
-    4. Choose one action from this list: {allowed_actions}
+        Meeting & follow-up rules
+        -------------------------
+        1. Let `meeting_offer_sent` = **true** if any earlier assistant message offered a
+        meeting.  
+        2. If First “Thanks / Sounds good” & *no* prior meeting offer  
+            → **SEND_REPLY** asking for a 15-min call (≤150 words).  
+        3. If Second non-committal reply *after* meeting_offer_sent, or explicit “not interested”  
+            → **END_CONVERSATION**.  
+        4. If prospect explicitly asks for times / requests your link  
+            → **SCHEDULE_MEETING** and confirm or propose times.  
+        5. If One unsolicited follow-up maximum; stop unless prospect re-engages.
 
-    5. Provide your recommended email body that best addresses the user's message.
-    DO NOT reply to any PII or financial information requests; triage them as "REQUIRES_APPROVAL".
-    DO NOT replay anything negative about my product or company {campaign_context.lead_info.organization_name}; triage them as "REQUIRES_APPROVAL".
-    current date is : {current_date_iso}
-    DO NOT share any link to internal or made up doucment. You can attach or send any document.
-    If the user is asking for any document point them to organization's website found in sender information if available:
-    {campaign_context.sender_info.model_dump()} 
+        If you have not proposed a meeting even once in the thread, and the user response is polite acknowledgment then you MUST request for a meeting.
 
-    Your final output must be valid JSON with the structure:
+
+        Objections & info requests
+        --------------------------
+        • Pricing / docs / case-studies request → **NEED_MORE_INFO**.  
+        • Budget, timing, or competitor concerns → **OBJECTION_RAISED**  
+        (acknowledge + one clarifying Q or concise value point).  
+        • “Loop in {{colleague_name}}” → **FORWARD_TO_OTHER_USER**.
+
+        Unsubscribe & priority handling
+        -------------------------------
+        1. “Unsubscribe / Remove me” → **UNSUBSCRIBE**  
+        2. Clear lack of interest → **NOT_INTERESTED**  
+        3. Auto OOO reply → **OOF_MESSAGE**  
+        4. Explicit meeting request → **SCHEDULE_MEETING**  
+        5. Otherwise follow the Meeting & follow-up rules above  
+        6. Default → **END_CONVERSATION**
+
+        Style guard-rails
+        -----------------
+        • Plain language; no jargon or filler.  
+        • Do **not** repeat previous messages verbatim.  
+        • Signature must include sender_first_name exactly as provided.  
+        • Check UNSUBSCRIBE / NOT_INTERESTED first before other triage.
+
+        If you have not proposed a meeting even once in the thread, and the user response is polite acknowledgment then you MUST request for a meeting.
+         
+        • Meeting ask template example:
+        Hi {{lead_first_name}}, would you be open to a quick 15-min call to
+        understand your use-case and share notes?
+
+        • Competitor-stack mention template example:
+        Hi {{lead_first_name}}, thanks for sharing your current stack. Would you be
+        open to a 15-min call to explore where we can add value?
+        
+    Use conversational name for company name.
+    Use conversational name when using lead first name.
+    Do not use special characters or spaces when using lead’s first name.
+    In the subject or body DO NOT include any HTML tags like <a>, <b>, <i>, etc.
+    The body and subject should be in plain text.
+    If there is a link provided in the email, use it as is; do not wrap it in any HTML tags.
+    DO NOT make up information. Use only the information provided in the context and instructions.
+    Do NOT repeat the same message sent to the user in the past.
+    Keep the thread conversational and friendly as a good account executive would respond.
+    Do NOT rehash/repeat the same previous message already sent. Keep the reply to the point.
+    DO NOT try to spam users with multiple messages. 
+    Current date is: {current_date_iso}.
+    DO NOT share any link to internal or made up document. You can attach or send any document.
+    If the user is asking for any additional document END_CONVERSATION and let Account executive handle it.
+    - Make sure the body text is well-formatted and that newline and carriage-return characters are correctly present and preserved in the message body.
+    - Do Not use em dash in the generated output.
+
+    Required JSON output
+    --------------------
     {{
-      "triage_status": "AUTOMATIC" or "REQUIRES_APPROVAL",
-      "triage_reason": "<reason if requires approval; otherwise null>",
-      "response_action_to_take": "<chosen action>",
-      "response_message": "<the email body to respond with>"
+    "triage_status": "AUTOMATIC" or "END_CONVERSATION",
+    "triage_reason": "<reason if END_CONVERSATION; otherwise null>",
+    "response_action_to_take": "one of {allowed_actions}",
+    "response_message": "<the reply body if response_action_to_take is SEND_REPLY or SCHEDULE_MEETING; otherwise empty>"
     }}
+
+    Current date is: {current_date_iso}.
+    -----------------------------------------------------------------
     """
 
+
     # If there's a vector store ID, use that approach
     if (
         cleaned_context.external_known_data
@@ -124,6 +377,7 @@ async def generate_inbound_email_response_copy(
         initial_response, status = await get_structured_output_with_assistant_and_vector_store(
             prompt=prompt,
             response_format=InboundEmailTriageResponse,
+            model="gpt-5.1-chat",
             vector_store_id=cleaned_context.external_known_data.external_openai_vector_store_id,
             tool_config=tool_config
         )
@@ -131,6 +385,7 @@ async def generate_inbound_email_response_copy(
         initial_response, status = await get_structured_output_internal(
             prompt=prompt,
             response_format=InboundEmailTriageResponse,
+            model="gpt-5.1-chat",
             tool_config=tool_config
         )
 
@@ -139,6 +394,7 @@ async def generate_inbound_email_response_copy(
 
     response_item = MessageItem(
         message_id="",  # or generate one if appropriate
+        thread_id="",
         sender_name=campaign_context.sender_info.sender_full_name or "",
         sender_email=campaign_context.sender_info.sender_email or "",
         receiver_name=campaign_context.lead_info.full_name or "",
@@ -155,6 +411,7 @@ async def generate_inbound_email_response_copy(
         message_item=response_item,
         response_action_to_take=initial_response.response_action_to_take
     )
+    print(response_message.model_dump())
     return response_message.model_dump()
 
 

dhisana/utils/generate_flow.py

@@ -1,4 +1,3 @@
-import logging
 from pydantic import BaseModel
 from dhisana.utils.dataframe_tools import get_structured_output
 

dhisana/utils/generate_linkedin_connect_message.py

@@ -25,7 +25,6 @@ from dhisana.utils.assistant_tool_tag import assistant_tool
 # LinkedIn Connection Message Schema
 # ----------------------------------------------------------------------
 class LinkedInConnectMessage(BaseModel):
-    subject: str
     body: str
 
 # ----------------------------------------------------------------------
@@ -125,10 +124,19 @@ async def generate_personalized_linkedin_copy(
         LinkedIn Thread: {conversation_data.current_linkedin_thread or ''}
 
         IMPORTANT REQUIREMENTS:
-        - Output must be JSON with "subject" and "body" fields only.
-        - The entire message must be under 40 words total (subject + body).
+        - Output must be JSON "body" of the message.
+        - The entire message body must be under 40 words total.
+        - In the body DO NOT include any HTML tags like <a>, <b>, <i>, etc.
+        - The body should be in plain text.
+        - If there is a link provided in body use it as is. dont wrap it in any HTML tags.
         - No placeholders or extra instructions in the final output.
         - Do not include personal addresses, IDs, or irrelevant internal data.
+        - Linked in message always has saluatation Hi <First Name>, unless specified otherwise.
+        - <First Name> is the first name of the lead. Its conversational name. It does not have any special characters or spaces.
+        - Make sure the signature in body has the sender_first_name is correct and in the format user has specified.
+        - User conversational name for company name if used.
+        - Make sure the body text is well-formatted and that newline and carriage-return characters are correctly present and preserved in the message body.
+        - Do Not use em dash in the generated output.
     """
 
     vector_store_id = (
@@ -142,14 +150,18 @@ async def generate_personalized_linkedin_copy(
             prompt=prompt,
             response_format=LinkedInConnectMessage,
             vector_store_id=vector_store_id,
-            tool_config=tool_config
+            model="gpt-5.1-chat",
+            tool_config=tool_config,
+            use_cache=linkedin_context.message_instructions.use_cache if linkedin_context.message_instructions else True
         )
     else:
         # Otherwise, generate internally
         response_data, status = await get_structured_output_internal(
             prompt=prompt,
             response_format=LinkedInConnectMessage,
-            tool_config=tool_config
+            model="gpt-5.1-chat",
+            tool_config=tool_config,
+            use_cache=linkedin_context.message_instructions.use_cache if linkedin_context.message_instructions else True
         )
 
     if status != "SUCCESS":
@@ -158,12 +170,13 @@ async def generate_personalized_linkedin_copy(
     # Wrap in MessageItem for consistency
     response_item = MessageItem(
         message_id="",  # fill in if you have an ID
+        thread_id="",
         sender_name=sender_data.sender_full_name or "",
         sender_email=sender_data.sender_email or "",
         receiver_name=lead_data.full_name or "",
         receiver_email=lead_data.email or "",
         iso_datetime=datetime.utcnow().isoformat(),
-        subject=response_data.subject,
+        subject="Hi",
         body=response_data.body
     )