Plan changes, and the proration nobody writes down

The opening message is usually ambiguous. Somebody who types that they want to change their plan may mean any of five things, and the pattern that produces the worst answers is picking the most common one and describing it confidently.

Material shaped as a short list of the changes you support, each with one line on what it does, lets a single reply cover the fork. The subscriber recognises their case, names it, and the second reply is precise. Two exchanges beats one confident wrong one.

The rule is publishable and belongs in the material: a mid period move up is charged the difference for the remainder, or a move down takes effect at renewal with nothing credited, or unused time becomes a balance against the next invoice. Whichever is true, the assistant can state it with a citation and it holds for everybody.

What it must not do is arithmetic. The moment somebody says they are eleven days into a period on one plan and asks what moving costs, the answer needs their plan, their price, their date and any reduced rate they carry, none of which the assistant can see. A number produced from a partial description looks like a figure out of your billing system, and it will be argued about when the real invoice lands.

Immediately, at the next renewal, or at the end of a notice period. Each of the five changes may answer this differently inside the same product, and the answer decides whether somebody is about to be charged again this week.

State the effective moment in the same sentence as the change itself. A reply that explains how to move down without saying when it lands is complete on its face and useless in practice, because the reason they asked today rather than next month is the date.

People move down to spend less and then find they have also given something up. The seats over the limit, the older records, the export they were about to run. That second discovery arrives as an angry message about lost data, and it started as a routine plan change.

The assistant should surface the loss in the same answer as the method, unprompted. It reads as care rather than as friction, and it is the one paragraph in this intent that reliably prevents a complaint.

What the change will cost me, what I will be charged on the day, whether my reduced rate survives it, how many seats I currently have. The assistant cannot see a plan, a price, a period or a promotional arrangement, and every one of these questions needs all four.

The reply that works states the rule, says plainly that the exact figures come from the account, and takes the request. Anything softer reads as a quotation.

I moved down and was charged the old amount, I paused and it restarted, I shifted the date and got billed twice. These are contested accounts of what a system did, they usually involve money that has already moved, and they need somebody who can look at the record rather than a restatement of the policy the subscriber is disputing.

Somebody wants to spend less, not to leave. They ask about moving down, the assistant matches on the closest material it has, which in most businesses is the page about leaving, and returns that route. It is accurate, it is well written, and it answers a question they did not ask.

A share of those people follow it. You have converted a downgrade into a churn, and it happened because the material for the change they wanted did not exist and the material for the exit did. The fix is content rather than configuration: write the plan change routes as their own documents, keep them well away from the page about leaving, and check that the assistant answers a request to pay less with a way to pay less.