Case Study A · Support prompt cleanup
Rewrite of an overgrown customer-support prompt with conflicting tone and policy rules
A client had one long support prompt that had accumulated changes over time. It contained competing tone rules, repeated policy instructions and weak behavior for missing information.
Service€20 · up to 40 minutes
InputOne existing support prompt
Main issueConflicting rules + weak fallback behavior
OutputRewritten prompt + mini test checklist
What the client brought
- The current prompt/system instruction.
- Examples of weak answers.
- The intended tone and answer length.
- Non-negotiable policy and escalation rules.
A→Z optimization
- Clarify objectiveDefined the exact job: draft support responses using approved information while asking for missing details and avoiding unsupported commitments.
- Find instruction conflictsMarked duplicate rules, contradictions, vague behavior requirements and policy text that needed separation from response behavior.
- Restructure hierarchyRebuilt the prompt into role, objective, allowed context, hard boundaries, clarification behavior, tone and output format.
- Add fallback behaviorSpecified what to do when information was missing, when a human was required and when policy did not support a definitive answer.
- Test representative inputsRan normal FAQ, incomplete request, complaint and unsupported policy scenarios to validate the new structure.
- HandoverDelivered the rewritten prompt plus concise notes explaining changes and what to retest after future edits.
Artifacts delivered
Clean rewritten support prompt
Role/objective block
Boundary + escalation block
Tone/output-format rules
Focused test scenarios
Next-step notes
Session complete when
- The rewritten prompt had no obvious internal contradictions.
- Missing information triggered clarification or escalation behavior.
- Representative tests followed the intended tone and answer structure.
- The client had a reusable final version and retest guidance.