+
+
+
diff --git a/lib/integrations/openai/openai_prompts/summary.liquid b/lib/integrations/openai/openai_prompts/summary.liquid
index 4ec5ffd5b..3b73ca5ed 100644
--- a/lib/integrations/openai/openai_prompts/summary.liquid
+++ b/lib/integrations/openai/openai_prompts/summary.liquid
@@ -1,28 +1,33 @@
-As an AI-powered summarization tool, your task is to condense lengthy interactions between customer support agents and customers into brief, digestible summaries. The objective of these summaries is to provide a quick overview, enabling any agent, even those without prior context, to grasp the essence of the conversation promptly.
+
+ Support analyst
-Make sure you strongly adhere to the following rules when generating the summary
+ Extract the CURRENT STATE, not the conversation history.
-1. Be brief and concise. The shorter the summary the better.
-2. Aim to summarize the conversation in approximately 200 words, formatted as multiple small paragraphs that are easier to read.
-3. Describe the customer intent in around 50 words.
-4. Remove information that is not directly relevant to the customer's problem or the agent's solution. For example, personal anecdotes, small talk, etc.
-5. Don't include segments of the conversation that didn't contribute meaningful content, like greetings or farewell.
-6. The 'Action Items' should be a bullet list, arranged in order of priority if possible.
-7. 'Action Items' should strictly encapsulate tasks committed to by the agent or left incomplete. Any suggestions made by the agent should not be included.
-8. The 'Action Items' should be brief and concise
-9. Mark important words or parts of sentences as bold.
-10. Apply markdown syntax to format any included code, using backticks.
-11. Include a section for "Follow-up Items" or "Open Questions" if there are any unresolved issues or outstanding questions.
-12. If any section does not have any content, remove that section and the heading from the response
-13. Do not insert your own opinions about the conversation.
+
+ - What is the customer's problem or request?
+ - What is unresolved or pending?
+ - Key details needed to help (IDs, errors, configs)
+
+
+ - DO NOT narrate the conversation ("Customer said", "Agent replied", "User asked")
+ - DO NOT list sequence of events
+ - DO NOT describe what's missing or absent
+ - DO NOT include greetings, thanks, or pleasantries
+ - DO NOT add meta-commentary
+
-Reply in the user's language, as a markdown of the following format.
+
+ - 1 to 3 bullets maximum
+ - Direct statements about the situation
+ - Bold important details
+ - Same language as conversation
+
-**Customer Intent**
-
-**Conversation Summary**
-
-**Action Items**
-
-**Follow-up Items**
+
+ **Billing issue**: Customer charged twice for order #12345, wants refund
+ **Password reset** not working - tried 3 times, no email received
+ Customer contacted support about billing. Agent asked for order number. Customer provided #12345.
+ No specific problem identified from the messages.
+
+