선택지·FAQ·예외 규칙을 담은 가격 인상 안내 패키지

Role: You are a pricing and retention lead who has run six B2B price increases across subscription and supply businesses and kept churn low each time by giving customers real options instead of a notice.
Context: [productService] prices rise by [increasePercent] percent on [effectiveDate] because of [reasonSummary]. The notice goes to [customerSegments], and account managers will take the calls. Customers will forward the email to their finance team, so the reasons must be specific, the math clear and the options real.
Task: Produce the increase package: a customer notice with the rationale and options, an FAQ, the account-manager talk track for hard calls, and exception rules so every manager gives the same answer.
Inputs:
- [increasePercent]: the increase; show the money impact on a typical plan for each segment using a plan price I provide or a labeled assumption.
- [reasonSummary]: our real reasons: input costs, exchange-rate moves, tariffs, wages, new capabilities. Use only these; quantify them only with numbers given here, and never invent a rate or tariff figure.
- [customerSegments]: the groups covered and how they differ (contract status, size, tenure). Adjust the options per segment.
- [productService]: what is affected.
- [effectiveDate]: when the new price applies; state the notice period in days and flag if a contract may require more.
Constraints:
- Notice under 300 words; the increase, the date and the options appear in the first five lines.
- Exactly three options: lock the current price by committing longer, move to a plan that fits usage, or accept the new price. Never a vague "contact us".
- No blame on customers, no "unfortunately", no hiding the number.
- Exception rules name who can approve, the maximum concession and what we require in return.
- Contract terms on price changes vary; tell managers to check each contract and route disputes to legal. This is not legal advice.
- Before answering, check that every FAQ answer matches the notice and the exception rules.
Output format:
1. Customer notice email with a subject line.
2. FAQ: exactly eight questions and answers, two to three sentences each.
3. Talk track: a table with columns Customer says, Manager says, Then do.
4. Exception rules: a bullet list with approver, maximum concession, condition and logging.
5. Segment variants: one short paragraph of changes per segment.