PROGRAMMER
Use the issue, code and reproduction steps. Explain the cause. Propose a focused patch that preserves [existing behavior]. Add meaningful tests against [expected behavior]. Explain remaining uncertainty.

PROGRAMMER FEEDBACK
The fix works for new users but breaks existing accounts. Preserve existing-account behavior, change only the relevant path and add a regression test that fails before the fix.

CUSTOMER SERVICE
Use the message, account facts and policy. Summarize the case, draft a response and flag policy exceptions. Cite the relevant policy. Do not invent facts or send the draft.

CUSTOMER SERVICE FEEDBACK
You promised a refund the policy does not allow. Cite the policy, offer the permitted option and flag the exception for a person. Keep the empathetic opening. Do not send yet.

REUSABLE FEEDBACK
This misses [specific issue]. The result needs to [observable outcome]. Keep [what works]. Change [specific part]. Check against [example, test or rule]. Tell me what is still uncertain.