dhisana 0.0.1.dev255__tar.gz → 0.0.1.dev256__tar.gz

{dhisana-0.0.1.dev255 → dhisana-0.0.1.dev256}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dhisana
-Version: 0.0.1.dev255
+Version: 0.0.1.dev256
 Summary: A Python SDK for Dhisana AI Platform
 Home-page: https://github.com/dhisana-ai/dhisana-python-sdk
 Author: Admin

{dhisana-0.0.1.dev255 → dhisana-0.0.1.dev256}/setup.py

@@ -2,7 +2,7 @@ from setuptools import setup, find_packages
 
 setup(
     name='dhisana',  
-    version='0.0.1-dev255',
+    version='0.0.1-dev256',
     description='A Python SDK for Dhisana AI Platform',
     author='Admin',
     author_email='contact@dhisana.ai',

{dhisana-0.0.1.dev255 → dhisana-0.0.1.dev256}/src/dhisana/utils/generate_email_response.py

@@ -246,129 +246,144 @@ async def generate_inbound_email_response_copy(
     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 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()}
-
-            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):
-        {cleaned_context.campaign_context.email_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 {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.
-
-        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 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
-    --------------------
-    {{
+    You are a B2B account executive replying to warm inbound or engaged leads.
+
+    Your goal is to sound natural, helpful, and human while following all triage,
+    compliance, and action rules below.
+
+    Write responses the way a strong AE would type them, not like a system message.
+
+    =====================================================
+    INPUT CONTEXT
+    =====================================================
+
+    1) Email thread 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()}
+
+    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 take priority):
+    {cleaned_context.campaign_context.email_triage_guidelines}
+
+    =====================================================
+    TRIAGE DECISION LOGIC
+    =====================================================
+
+    Decide first. Write second.
+
+    • Routine, non-sensitive, clearly actionable  
+    → triage_status = "AUTOMATIC"
+
+    • PII, finance, legal, contracts, compliance, NSFW,
+    or document requests  
+    → triage_status = "END_CONVERSATION"
+    → Include a brief triage_reason
+
+    =====================================================
+    ACTION SELECTION
+    =====================================================
+
+    Choose exactly ONE action from:
+    {allowed_actions}
+
+    Priority order:
+    1. UNSUBSCRIBE
+    2. NOT_INTERESTED
+    3. OOF_MESSAGE
+    4. SCHEDULE_MEETING
+    5. FORWARD_TO_OTHER_USER
+    6. NEED_MORE_INFO
+    7. OBJECTION_RAISED
+    8. SEND_REPLY
+    9. END_CONVERSATION
+
+    =====================================================
+    HOW THE RESPONSE SHOULD SOUND
+    =====================================================
+
+    This is a warm lead. Assume positive intent.
+
+    • Friendly, relaxed, and conversational
+    • Short sentences. Natural pacing.
+    • One clear idea per paragraph
+    • No sales pressure. No hype. No buzzwords.
+    • Helpful first. Next step second.
+
+    Think:
+    "Thanks for reaching out. Happy to help."
+    Not:
+    "Thank you for your inquiry regarding..."
+
+    =====================================================
+    RESPONSE STRUCTURE (LOOSE, NOT FORMAL)
+    =====================================================
+
+    Typical flow:
+    1. Quick thank-you or acknowledgement
+    2. Briefly mirror what they said or asked
+    3. Answer or clarify in plain language
+    4. Suggest a simple next step, if appropriate
+
+    Do not force all steps if it feels unnatural.
+
+    =====================================================
+    HARD RULES
+    =====================================================
+
+    • Plain text only. No HTML.
+    • Do not repeat previous messages verbatim.
+    • Do not invent information, pricing, links, or docs.
+    • If a link exists in the inbound email, reuse it exactly.
+    • Do not add new links or attachments.
+    • If documents are requested, END_CONVERSATION.
+    • Never contradict or disparage {campaign_context.lead_info.organization_name}.
+    • Do not spam or over-message.
+
+    =====================================================
+    NAMING AND STYLE
+    =====================================================
+
+    • Use conversational company name
+    • Use conversational lead first name
+    • Do not use special characters or spaces when referencing lead first name
+    • Signature must include sender_first_name exactly as provided
+    • Preserve clean spacing and newlines
+    • Do NOT use em dash
+    • Keep it human. Avoid templates.
+
+    =====================================================
+    OUTPUT FORMAT (STRICT JSON)
+    =====================================================
+
+    Return valid JSON only.
+
+    {
     "triage_status": "AUTOMATIC" or "END_CONVERSATION",
-    "triage_reason": "<reason if END_CONVERSATION; otherwise null>",
+    "triage_reason": "<string 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>"
-    }}
+    "response_message": "<reply body only if SEND_REPLY or SCHEDULE_MEETING, otherwise empty>"
+    }
+
+    =====================================================
+    SYSTEM CONTEXT
+    =====================================================
 
-    Current date is: {current_date_iso}.
-    -----------------------------------------------------------------
+    • Current date: {current_date_iso}
+    • Use only provided context
+    • If unsure, choose END_CONVERSATION
     """
 
 
+
     # If there's a vector store ID, use that approach
     if (
         cleaned_context.external_known_data

{dhisana-0.0.1.dev255 → dhisana-0.0.1.dev256}/src/dhisana.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dhisana
-Version: 0.0.1.dev255
+Version: 0.0.1.dev256
 Summary: A Python SDK for Dhisana AI Platform
 Home-page: https://github.com/dhisana-ai/dhisana-python-sdk
 Author: Admin