Skip to main content

Updated Sep 30, 2026Verified against the product Sep 30, 2026

Open in ClaudeOpen in ChatGPT

Prepare for a Customer Call

Before a customer call you need four answers: where the relationship stands, who you're meeting and what they care about, what's open or at risk, and what you want out of the call. FunnelStory keeps all four current for every account, so preparing takes minutes rather than an afternoon of digging through email and notes. This guide is a ten-minute routine for any call: a check-in, an escalation, a renewal conversation, or a handoff.

Let the briefing come to you​

With meeting prep set up, FunnelStory sends you a Slack message about 30 minutes before any meeting with a customer account. It covers the account's health, recent activity, feature requests, notes from earlier meetings, and open action items. It needs two connections for your user:

  1. A calendar, from the profile menu → Calendar Settings → Authorize Calendar.
  2. Slack, mapped to your FunnelStory user.

See Meeting prep for the details. The briefing is a good start; the steps below are for calls that matter more.

1. Read the story so far (2 minutes)​

Open the account from Accounts. The Adoption → Overview tab is the account's history ledger:

  • the summary and key facts — customer since, current ARR, last renewal, next renewal, and open risks;
  • the timeline, showing renewals, expansions, contractions, and risks over the account's life;
  • the Upcoming section, with the meetings already on the calendar.

If you only have two minutes, this is the tab to read.

2. Know who you're meeting (3 minutes)​

Open Renewal → Dossier. The Account Dossier has a stakeholder profile for each contact: their role (Champion, Economic Buyer, Blocker, and so on), whether they're Active, Flat, or Dark, what they care about, and which of your teammates talk to them. For each person on the invite, note what they care about and who on your team knows them best.

Then check coverage. Relationship Intelligence at the top of the Dossier flags single-threaded accounts and engagement drops, and the Customer Relations tab shows the full relationship map. If only one contact is really engaged, a goal for this call is meeting a second one.

3. Check what's open (3 minutes)​

  • Needle-Movers tab — open concerns and opportunities, such as a pricing worry, a competitor mention, or a feature request, each with the source excerpts. Anything the customer raised that you haven't answered should be on your agenda.
  • Dossier → Active Concerns and Positive Signals — what's working against or for the relationship in the last 90 days.
  • Adoption → Tickets — support issues still open. Walking in unaware of an open escalation is the fastest way to lose a call.
  • Adoption → Tasks — commitments your team made and hasn't closed.

4. Decide what you want from the call (2 minutes)​

Write down one goal and the questions that serve it. The account tells you where to aim:

If you see…Aim the call at…
A Churn prediction, or health dropping in Renewal → Driving FactorsWhat's changed for them, and what would make the product indispensable again
A single-threaded relationship or a contact gone DarkAn introduction to a second stakeholder
Open feature requests or ticketsClosing the loop on each, with a date
Strong usage and positive signalsA value story and, if it fits, expansion — see Renewal → What's Next for what similar accounts did

After the call​

  • Record decisions in Adoption → Notes (Add New Note) and follow-ups in Adoption → Tasks (New Task) with owners and dates.
  • If the call raised a new risk or opportunity, it will reach the account as a needle mover once the meeting or follow-up email is ingested — check the next day that it was captured.
  • Your notes and the meeting itself feed the Dossier, so the next person to prepare for this account starts from what you learned.

Prefer to ask Claude?​

With the FunnelStory skills set up in Claude, ask "Prepare me for my call with [Account]" for a pre-call brief built from the same data, or "Give me an account brief for [Account]" for a fuller write-up to share with your team.

Last updated on