Revising a Support Prompt Safely

Overview

A customer support prompt is operational policy wearing a prompt's clothes: the refund boundary, the escalation rule, the promise discipline. That makes revisions higher-stakes than they look — an edit that improves warmth while loosening the boundary is a net regression with a friendly face. This resource diffs a realistic support prompt revision and shows the safe pattern: tone and structure can move freely, policy lines must appear unchanged or strengthened in the diff, never in the removed list.

Workflow

1. 1
   Diff the loaded revision

   Version B reworks tone and adds structure. Run the diff and go straight to the removed list — it should be empty of policy lines.

2. 2
   Verify the boundaries

   Both policy lines survive in the modified list, strengthened: verification got a timeline, escalation got a third trigger.

3. 3
   Check what tone edits added

   'No generic empathy lines' is a constraint, not fluff — it shows as added control, not added ambiguity.

4. 4
   Apply the rule

   For support prompts: policy lines may appear in added or modified, never in removed. One glance at the diff enforces it.

Why This Works

• Support prompts fail on policy before they fail on tone — the diff checks policy first
• Modified-list review shows whether a boundary was strengthened or quietly relaxed
• The never-in-removed rule is simple enough for every editor to apply consistently

Use cases

• Reviewing edits to a support prompt that encodes refund or escalation policy
• Onboarding a new support lead onto a prompt's policy lines
• Confirming a tone rewrite left every boundary intact