Subscription management can report Replacement plans could not be loaded, or it can show No matching replacement plan after a successful load. These are different results.
For a loading error, use the retry control and wait for the choices to load. Do not treat an error as proof that no plan exists.
If there is no published replacement for an upgrade or downgrade, describe the Requested service changes so the team can confirm scope and price. The custom description path requires meaningful detail and is not a universal substitute for every billing-frequency action.
If you need a monthly or annual change that has no eligible choice, ask the team to check that subscription. Do not select a different company or unrelated service merely to expose a price. Include the current plan, desired billing term, and company in your question. The current subscription stays in place until the change has been confirmed through the applicable flow.
Was this article helpful?
Tell us whether this answered the question you came with.