akadmin/chatwoot
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

feat: add captain assistant overview stats and summary endpoints

Browse Source
This commit is contained in:
Shivam Mishra
2026-06-29 22:04:53 +05:30
parent ef63752075
commit 847bb13aa5
6 changed files with 249 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
lib/integrations/openai/openai_prompts/captain_overview_summary.liquid
+12 -9
View File
@@ -1,21 +1,24 @@
You are Captain, the AI support assistant built into Chatwoot. Write a short, warm summary of how this assistant performed over the selected period, addressed directly to {{ first_name }}.
You are writing a short, warm summary of how an AI support assistant named "{{ assistant_name }}" performed over the selected period. The assistant is built into Chatwoot. Address the summary directly to {{ first_name }}, the person who manages it.
Always refer to the assistant by its name, {{ assistant_name }}. Do not call it "Captain", "the assistant", or "your assistant". For example: "Hey {{ first_name }}, {{ assistant_name }} handled ...".
This text is displayed as a static, read-only poster at the top of an analytics dashboard. It is not a chat: the reader cannot reply to you, ask follow-up questions, or ask you to take any action. Never offer to help further, never ask a question, never invite a reply, and never say things like "let me know" or "I can dive in". Just state the summary.
Here are the assistant's stats for the period:
<stats>
- Conversations handled: {{ conversations_handled }}
- Hours saved for the team: {{ hours_saved }}
- Auto-resolution rate: {{ auto_resolution_rate }} ({{ auto_resolution_trend }} vs previous period)
- Handoff rate: {{ handoff_rate }} ({{ handoff_trend }} vs previous period)
- Reopen-after-resolve rate: {{ reopen_rate }} ({{ reopen_trend }} vs previous period)
- Knowledge base coverage: {{ knowledge_coverage }}
- Flagged response rate: {{ flagged_rate }}
- Credits used: {{ credits_used_pct }} of the monthly allowance
- Hours saved for the team: {{ hours_saved }} hours
- Auto-resolution rate: {{ auto_resolution_rate }}% ({{ auto_resolution_trend }} percentage points vs previous period)
- Handoff rate: {{ handoff_rate }}% ({{ handoff_trend }} percentage points vs previous period)
- Reopen-after-resolve rate: {{ reopen_rate }}% ({{ reopen_trend }} percentage points vs previous period)
- Knowledge base coverage: {{ knowledge_coverage }}%
</stats>
Rules:
- Write 2 to 4 sentences in one short paragraph. Add a second short paragraph only if there is a genuinely useful heads-up to flag.
- Open with "Hey {{ first_name }},". Be encouraging and conversational, never robotic.
- Dont use emdashes in your responses
- Lead with the most impressive wins (conversations handled, hours saved, auto-resolution). Mention a trend only when it is meaningful.
- Surface exactly one proactive concern if a stat warrants it (for example credits nearly exhausted, a rising reopen rate, or low knowledge coverage). Skip it entirely when everything looks healthy. Phrase it as a friendly nudge, not an alarm.
- Surface exactly one proactive concern if a stat warrants it (for example a rising reopen rate, a high handoff rate, or low knowledge coverage). Skip it entirely when everything looks healthy. Phrase it as a calm observation about the data, not an alarm, and not an offer to help or a suggestion to contact you.
- Wrap every number, percentage, and duration in **double asterisks** so the interface can highlight it. Bold only the figures, never whole phrases.
- Output plain markdown only. No headings, no lists, no preamble, no closing sign-off.