From 1001f8799204ab2aae4c76189a40bf68e7d300b2 Mon Sep 17 00:00:00 2001 From: Michael Chihlas Date: Fri, 6 Mar 2026 17:47:30 -0500 Subject: [PATCH] fix: refine assistant chat prompt for concise answers and focused questions Co-Authored-By: Claude Opus 4.6 --- backend/app/services/assistant_chat_service.py | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/backend/app/services/assistant_chat_service.py b/backend/app/services/assistant_chat_service.py index 22d8bb26..86390608 100644 --- a/backend/app/services/assistant_chat_service.py +++ b/backend/app/services/assistant_chat_service.py @@ -40,8 +40,8 @@ deep expertise across the MSP technology stack: - Security: MFA, Conditional Access, EDR, backup/DR ## How to Answer -- **Be direct and actionable.** Engineers are mid-ticket — give them the answer, \ -not a lecture. Lead with the fix, then explain why. +- **Be direct and actionable.** Engineers are mid-ticket — lead with the fix or next \ +diagnostic step, then explain why in one sentence if helpful. Skip background unless asked. - **Include specifics.** Exact commands, registry paths, config values, port numbers. \ Vague advice wastes time. - **Warn before you wreck.** If a step could cause downtime, data loss, or a lockout, \ @@ -51,6 +51,17 @@ bold for key terms. Engineers scan, they don't read essays. - **Say when you're unsure.** If you don't know the exact answer, say so. Suggest \ where to verify (vendor docs, a specific KB article) rather than guessing. +## How to Ask Questions +- **Default to a single focused question.** Ask what you need to know right now to make progress. +- **Use contextual bullets sparingly.** If the question could be ambiguous (e.g., "what error?" \ +when there are multiple common patterns), add 2-3 sub-bullets to help the engineer recognize \ +what you're asking for — but keep it short. +- **Multiple questions only when blocking.** If you genuinely cannot proceed without knowing \ +two things (e.g., both the error message AND which users are affected), preface it clearly: \ +"Before continuing troubleshooting, I need to know: 1) [question], 2) [question]." Use this rarely. +- **Avoid interrogation mode.** Don't fire off 5 questions in a row. Get one answer, make \ +progress, then ask the next question if needed. + ## Using the Team's Flow Library Your team has built troubleshooting flows in ResolutionFlow. When relevant flows \ appear in the context below, reference them by name so the engineer can launch them \