How to Prepare for a Customer Call in 15 Minutes
How to prepare for a customer call without opening ten tabs: what to check in the CRM, tickets, usage and billing, and a one-page brief template to fill in.
Quick answer: To prepare for a customer call, spend 15 minutes building a one-page brief: why the call is happening, what changed since the last call (tickets, usage, billing, open promises), who will be on it, the one outcome you want, and three questions to ask. Check the same sources in the same order every time.
Why customer call prep takes so long
Prep is slow because the account's story is spread across tools. The CRM has the contract and the contacts, the help desk has the tickets, the product has the usage, finance has the invoices, and the real context is in a Slack thread or last quarter's call notes. A recent thread in r/CustomerSuccess asked CSMs how many tabs they open before a customer call, and the honest answer is "all of them".
The cost adds up. One CS team wrote on Reddit that each quarterly business review took their CSMs 6 to 8 hours, counting prep, the meeting and the follow-up, across 40 accounts. Most calls aren't QBRs, but the same problem shows up at a smaller scale before every check-in, escalation and renewal.
The fix isn't a better dashboard. It's a fixed routine and a short written brief.
What to check before a customer call
Go through the same sources in the same order, and only pull what changed since your last conversation. The question for each one is "what would embarrass me if the customer brought it up first?"
| Source | What to pull | Red flags |
|---|---|---|
| Last call notes or recap email | What you promised, what they promised, open questions | A promise from your side that hasn't shipped |
| Help desk (Zendesk, Intercom, Freshdesk) | Tickets opened since the last call, anything still open | The same issue reported twice, a ticket waiting on your team |
| Product usage | Active users, the features they bought it for, trends | Usage dropping, a key team that stopped logging in |
| Billing | Plan, seats, renewal date, failed payments | Renewal inside 90 days, seats unused, an overdue invoice |
| CRM and contacts | Who is joining, their role, who signs | A new stakeholder, your champion changing jobs |
| Internal Slack or notes | What sales, support or product said about them | An escalation you weren't tagged in |
If you keep a recap email after every call, step one takes a minute. Our guide to writing a customer call recap email covers that half of the loop.
A one-page customer call brief template
Write this in your CRM notes, a doc or wherever your team keeps account context. Keep it short enough to read in the two minutes before you join.
Account: [name], [plan], renewal [date]
Call type: [check-in / escalation / renewal / onboarding review]
On the call: [names, roles, who decides]
Why this call: [one sentence]
Since last time:
- [ticket, usage change or billing event]
- [promise we made, and its status]
- [promise they made, and its status]
The one outcome I want: [e.g. agree on a fix date, confirm renewal, get a second team onboarded]
Risks: [what could go wrong in the conversation]
Questions to ask:
1. [about their goals this quarter]
2. [about the red flag above]
3. [about who else should be involved]
"The one outcome I want" is the line that matters most. A call with a single clear goal is easier to steer and easier to follow up on. If you can't fill it in, ask whether the call needs to happen or could be an email.
How to prepare for different kinds of customer calls
The brief stays the same. What you weigh changes:
- Check-in. Focus on usage and their goals. Bring one specific suggestion based on what they use, not a tour of features.
- Escalation. Read every ticket in the thread, know the current status and the next date from your team, and decide in advance what you can offer. Don't go in without an owner for the fix. If tickets are piling up, our guide to replying to support tickets faster helps with the backlog.
- Renewal. Billing, seat usage and any open promise first. Know who signs and whether they're on the call.
- Onboarding review. Compare what they said they wanted at kickoff with what they've set up so far.
Using AI to prepare for customer calls
AI is good at the "what changed" step. Paste the ticket history and your last recap into an assistant and ask for a summary of open issues, promises and anything that looks like a risk. It's faster than reading twenty tickets, and it often spots the repeated complaint you'd skim past.
Two rules keep this safe:
- Check what you're allowed to share. Customer data, ticket contents and contract terms may be covered by your company's AI policy or your customer's contract. Use the tools your company approves.
- Read the sources for anything you'll say out loud. Use the AI summary to find what to look at, then confirm dates, amounts and promises in the original record before the call.
The prompt matters more than the tool. A useful one names the call type and the outcome you want, for example: "Summarize these tickets and notes for a renewal call. List open issues, promises either side made and whether they were kept, and anything that suggests they might not renew."
How Blip AI speeds up customer call prep
Most of call prep is typing: the brief, the prompt for the AI summary, a note to a teammate, the follow-up after. Blip AI lets you say it instead. Speech runs at about 150 words per minute, against about 52 for the average typist.
- Talk through the brief. Click into your CRM notes or doc, hold Fn on Mac, Ctrl + Win on Windows or Ctrl + Super on Linux, and say what you know about the account. Blip removes the filler words and fixes punctuation, so it reads like notes, not a transcript.
- Write longer AI prompts. The more context you give the assistant (call type, outcome, what worries you), the better the summary. That's much easier to say than to type.
- Get account names right. Add customer names, product names and plan names to Blip's dictionary so they're spelled correctly every time.
- Draft the follow-up. After the call, say "Hey Blip" and describe the email you want. Action Mode drafts it instead of transcribing word for word. With Personalized Blip, it signs off with your name and follows your own writing rules, such as "keep emails short".
Blip works in any app with a text field, including Salesforce, HubSpot, Zendesk, Slack and Gmail in the browser. The free plan includes 2,000 words a month. Download Blip AI for Mac, Windows, Linux, iOS or Android.
FAQ
How long should you spend preparing for a customer call? About 15 minutes for a routine check-in, escalation or renewal call, if you check the same sources in the same order and write a one-page brief. Big meetings like QBRs or executive reviews need more, but the same brief is the starting point.
What should a customer call brief include? A customer call brief should include the call type, who is joining and who decides, what changed since the last call (tickets, usage, billing, open promises), the one outcome you want, the risks, and three questions to ask.
What should a CSM check before a renewal call? Before a renewal call, a CSM should check the renewal date and plan, seat and feature usage, any failed payments, open tickets, promises from earlier calls, and who signs the contract and whether they'll be on the call.
Can AI prepare for a customer call for you? AI can summarize tickets, notes and usage into a list of open issues and risks, which saves most of the reading. It can't decide the outcome you want from the call, and you should confirm any date, amount or promise in the original record before you repeat it to the customer.
What questions should you ask on a customer check-in call? Good check-in questions are about the customer's goals for the next quarter, whether the product is helping with the reason they bought it, anything that's been frustrating, and who else on their team should be involved.