Understand the working context
Review the customer agreement before preparing the document. Include the relevant products, prices and timing, and make any commercial explanation appropriate to the relationship. A shared-list increase may leave some fixed agreements unchanged. Avoid suggesting that every item changed when the customer’s actual pricing shows otherwise. Keep the letter with the account so colleagues can find the version used in the conversation.
Put it into practice
- Check the customer’s affected pricing.
- Review product names, amounts and effective timing.
- Make the reason and next contact clear.
- Review the document and recipient before sending.
A practical example
A customer buys several products under different rules. The generated letter lists the applicable changes while excluding a fixed price that remains the same. The account owner checks the document and discusses any questions with the customer before using a configured email service to send it.
In the current workspace
Atlas can prepare and store customer price-increase letters for supported pricing changes. Sending a saved document is an explicit reviewed action through an available connection.
Explore the productAtlas feature scope reviewed 17 October 2026. Plan availability and connection setup apply.