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

dhisana/utils/generate_linkedin_response_message.py

@@ -2,9 +2,11 @@ from typing import Any, Dict, List, Optional
 from pydantic import BaseModel
 from dhisana.schemas.sales import (
     ContentGenerationContext,
+    Lead,
     MessageItem,
     MessageResponse,
-    MessageGenerationInstructions
+    MessageGenerationInstructions,
+    SenderInfo
 )
 from dhisana.utils.generate_structured_output_internal import (
     get_structured_output_internal,
@@ -28,6 +30,7 @@ class LinkedInTriageResponse(BaseModel):
     triage_reason: Optional[str]
     response_action_to_take: str
     response_message: str
+    meeting_offer_sent: Optional[bool]
 
 
 # ---------------------------------------------------------------------------------------
@@ -59,13 +62,16 @@ async def generate_linkedin_response_message_copy(
     Returns a structured result conforming to LinkedInTriageResponse.
     """
     allowed_actions = [
-        "SEND_REPLY",        # Normal: send reply
-        "WAIT_TO_SEND",      # Wait because user was recently messaged
-        "STOP_SENDING",      # No more messages to user
-        "SCHEDULE_MEETING",  # If user requests a meeting
-        "FOLLOW_UP_LATER",
+        "SCHEDULE_MEETING",
+        "SEND_REPLY",
+        "UNSUBSCRIBE",
+        "OOF_MESSAGE",
+        "NOT_INTERESTED",
         "NEED_MORE_INFO",
-        "OTHER"
+        "FORWARD_TO_OTHER_USER",
+        "NO_MORE_IN_ORGANIZATION",
+        "OBJECTION_RAISED",
+        "END_CONVERSATION"
     ]
     
     cleaned_context = cleanup_reply_linkedin_context(linkedin_context)
@@ -88,65 +94,126 @@ async def generate_linkedin_response_message_copy(
         conversation_thread_dump = []
     
     current_date_iso = datetime.datetime.now().isoformat()
+    lead_data = linkedin_context.lead_info or Lead()
+    sender_data = linkedin_context.sender_info or SenderInfo()
+    campaign_context = linkedin_context.campaign_context or CampaignContext()
+
     prompt = f"""
-    You are a specialized LinkedIn assistant.
-
-    Your task:
-      1. Analyze the current LinkedIn conversation.
-      2. Inspect the user (lead) info, outreach campaign context, and any additional instructions.
-      3. Decide whether to automatically send a reply or if human approval is needed (triage).
-      4. If approval is needed, provide the reason.
-      5. Choose one recommended next action from: {allowed_actions}.
-      6. Provide a short LinkedIn message body that addresses the lead's conversation.
-      MAKE SURE the message is less than 300 words.
-
-    Use the following instructions to generate message: 
-    {variation}
-
-    1. Understand the conversation thread:
-       {conversation_thread_dump}
-
-    2. User & Company (Lead) Info:
-       {cleaned_context.model_dump()}
-
-    3. Triage Guidelines:
-       {cleaned_context.campaign_context.linkedin_triage_guidelines}
-       - 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.
-
-    4. Choose one action from this list: {allowed_actions}
-
-    Todays date is : {current_date_iso}
-    === IMPORTANT ANTI-SPAM AND RESPECT RULES ===
-    1. If we have sent a message to the user within the past 24 hours and the user has not responded,
-       do NOT send another message right now. Instead, triage with "WAIT_TO_SEND".
-    2. If we have sent more than 3 messages in total without any user response, do NOT send another message.
-       Instead, triage with "STOP_SENDING".
-    3. If the user explicitly says "don't reply", "not interested", or any equivalent,
-       do NOT continue the thread. Triage with "STOP_SENDING".
-    4. If the user has requested a meeting, triage as "AUTOMATIC" or "REQUIRES_APPROVAL" 
-       (depending on complexity), and set response_action_to_take to "SCHEDULE_MEETING".
-       Craft a helpful response for scheduling.
-
-    === TONE AND STYLE RULES ===
-    - Your message must be genuine, authentic, and professional.
-    - Avoid clichés and spammy or overly aggressive sales pitches.
-    - Do not push sales in an unnatural way.
-    - In the subject or body DO NOT include any HTML tags like <a>, <b>, <i>, etc.
-    - The body message and subject should be in plain text.
-    - If there is a link provided in message use it as is. dont wrap it in any HTML tags.
-    - <First Name> is the first name of the lead. Its conversational name. It does not have any special characters or spaces.
-
-    Make sure the message is less than 300 words.
-    === OUTPUT FORMAT ===
-    Your final output must be valid JSON in this exact format:
+        You are a specialized linkedin message reply assistant. 
+        Your task is to analyze the user's linkedin message thread, the user/company info,
+        and the provided triage guidelines to craft an appropriate response.
+
+        Follow these instructions to generate the reply: 
+        {variation}
+
+        1. Message thread or conversation to respond to:
+        {conversation_thread_dump}
+
+        2.
+        Lead Information:
+        {lead_data.dict()}
+
+        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 ''}
+
+        3. Campaign-specific triage guidelines (user overrides always win):
+        {campaign_context.linkedin_triage_guidelines}
+
+        -----------------------------------------------------------------
+        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**.
+
+        4. Choose exactly ONE of: {allowed_actions}
+
+        -----------------------------------------------------------------
+        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 {lead_data.organization_name}.  
+        • Plain-text only – NO HTML tags (<a>, <b>, <i>, etc.).  
+        • If a link already exists in the inbound message, include it verbatim—do not re-wrap or shorten.
+
+        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.
+
+        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.
+
+
+        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 message, 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; else empty or null>",
-      "response_action_to_take": "<one of {allowed_actions}>",
-      "response_message": "<the new or reply message>"
+    "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>"
     }}
     """
 
@@ -158,14 +225,18 @@ async def generate_linkedin_response_message_copy(
         initial_response, status = await get_structured_output_with_assistant_and_vector_store(
             prompt=prompt,
             response_format=LinkedInTriageResponse,
+            model="gpt-5.1-chat",
             vector_store_id=cleaned_context.external_known_data.external_openai_vector_store_id,
-            tool_config=tool_config
+            tool_config=tool_config,
+            use_cache=linkedin_context.message_instructions.use_cache if linkedin_context.message_instructions else True
         )
     else:
         initial_response, status = await get_structured_output_internal(
             prompt,
             LinkedInTriageResponse,
-            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':