Pricing notes should survive being pasted into a support reply

A practical note for small SaaS pricing changes: write the changelog, email, and support macro from one clear source.

Pricing updates get messy when the public note, customer email, billing FAQ, and support reply all explain the change differently. A useful test is to paste the pricing note into a support reply and see whether it answers who is affected, when it starts, what action is needed, and what exception applies. If support has to rewrite the policy each time, the note is not concrete enough. I would rather write one plain source and adapt the tone per channel than create four slightly different versions.