What should an account manager ask on a renewal call?
Start from what the customer told you before, then ask what changed. Each question below builds on something they said on an earlier call.
- What changed. You mentioned five or six plants sent the wrong format last year. How many still do?
- What it's worth now. You mentioned month-end took four days of fixes. What does month-end look like now?
- What's still left. You mentioned the team still checks some files by hand. What keeps those from moving over?
- Who decides. You mentioned a new finance lead joined in the spring. What will they want to see before the renewal?
- Where it grows. You mentioned two more regions start reporting next year. What would they need from the rollout?
Each one is a single open question, uses only what the customer said, and never offers a menu like "is it A or B?". Those are the rules Veracity's questions follow too.
How does Veracity bring the last call into this one?
Earlier calls with the same company feed the next call's opening question, questions and answers. So when the renewal call starts, the opening question is already built from what the account told you before.
You can edit that brief, or switch it off for a call that should start fresh.
Twice this year, plant managers got paid late.
You mentioned plant managers got paid late twice last year. What has changed for them since?A written example. It builds on what happened next, using the customer's own fact.
What if you inherited the account?
Import its past calls. In the Veracity portal you can bring in transcripts from any recorder as .txt, .md, .csv, .vtt or .srt files. Those calls feed the questions on your next call with the account, so your first call with them starts from that history.
What about the hard questions that come up at renewal?
New people join the call and ask new questions. When one turns technical, hit Answer and you get a line to say and the files it came from: your product docs, battle cards and security pages.
When the customer pushes back, you get a line to say, 30 words or fewer, with proof from your docs when one matches. The guide to handling objections on a live call has more.