The Reference Call Process: A Step-by-Step B2B Guide

A B2B reference call is a live conversation between a prospect and an existing customer. The prospect uses it to check your claims against real experience. The process that works has seven steps: qualify the moment, match the advocate, get consent from both sides, prep without scripting, run a focused call of about 30 to 45 minutes, follow up fast, and tie the result to the deal in your CRM. This guide walks through each one.

A quick note on the search term: “reference call process” also brings up hiring guides on checking a job candidate’s references. This article is for sales and customer marketing teams who put customers on the phone with buyers.

TL;DR

• A reference call is a trust-verification step. It typically happens late in the sales cycle, after the demo or proof of concept and before the final decision.
• Match advocates to prospects by use case, buyer role, industry, scale and willingness, not by how famous the logo is.
• Ask both people for consent individually before you make the introduction.
• Prep both sides, but never tell either what to say. A call that feels staged can turn an advocate into a detractor.
• Log every request against a CRM opportunity so you can track deals won and lost with references.

Table of Contents

• What a reference call is and when to use it
• The seven steps at a glance
• Step 1: Qualify the moment
• Step 2: Match the advocate to the prospect
• Step 3: Get consent from both sides
• Step 4: Make the introduction
• Step 5: Prep both sides without scripting
• Step 6: Run the call
• Step 7: Follow up and measure
• Common mistakes in the reference call process
• Why authenticity decides whether the call works
• Our perspective
• Put the process on rails with Clareefai
• FAQ
• Sources

What a reference call is and when to use it

A reference call is a conversation in which a prospect speaks directly with a current customer to validate the vendor’s claims through peer experience. It usually comes late in the cycle. The demo is done, the proof of concept has run, and the buyer wants to hear from someone who has lived with the product.

The buyer is rarely checking features at this point. They want to know what implementation really looked like, whether support shows up when something breaks, and whether the promised outcomes arrived. That is why a strong call can remove late-stage risk, while a mismatched or unprepared one can damage the deal.

Use a reference call when:

1. The buyer has moved past the demo and is comparing finalists.
2. A new stakeholder, such as procurement, finance or IT security, joins and needs independent reassurance.
3. The deal is large or complex enough that a wrong choice is costly for the buyer.
4. The prospect has raised a specific concern that a peer in a similar company can speak to.

Teams that wait for the prospect to ask are often scrambling. If you want to be ready, our post on being proactive with customer reference calls covers how to line up references before the request arrives.

The seven steps at a glance

Step 1: Qualify the moment

A reference call spends something scarce: a customer’s goodwill and time. Do not use it on a lead who is still exploring. Check that the prospect has a defined use case, a named decision process and a real concern the call can address.

Ask the rep one question before you request a reference: what does the buyer need to hear that we cannot tell them ourselves? If the answer is specific (“Will this scale across our three regions?”), the call has a purpose. If the answer is vague, keep nurturing.

Step 2: Match the advocate to the prospect

The most recognizable customer is usually the wrong choice. Good matching weighs use case, buyer role, industry, scale, geography, product experience and the advocate’s current willingness. A VP of Sales evaluating a rollout wants to hear from a VP of Sales who ran one, not from a marketing coordinator at a household-name brand.

A simple matching checklist:

• Use case: Did the advocate solve the same problem?
• Role: Does their seniority and function mirror the buyer’s?
• Industry and scale: Is their company a believable peer?
• Product experience: Have they used the features the prospect cares about?
• Availability: Have they been asked recently? Spread requests so no single advocate burns out.

This is where a structured reference database pays off. When every customer is tagged by those attributes, matching takes minutes instead of days. We go deeper in our guides to customer advocate matching and building a customer reference database.

If the pool is thin, the problem is upstream. Many teams have happy customers who have never been asked to speak up, and turning happy customers into advocates is the first job.

Step 3: Get consent from both sides

Never introduce two people who have not each said yes. Harvard Business Review’s advice on introductions is to ask both people individually why they want the connection and whether they are willing. Only when both are enthusiastic do you send the email.

For the advocate, make the ask easy to accept:

• Say who the prospect is (role, industry, size) and why you thought of them.
• State the time commitment up front, such as a single call of roughly 30 to 45 minutes.
• Offer a choice of dates and a way to decline without awkwardness.
• Explain what happens afterward, including that you will share the outcome.

For the prospect, confirm that they actually want to speak with a customer and what they hope to learn. That answer shapes your prep.

Step 4: Make the introduction

Keep the introduction email short. Name each person, state one line on why they are a good match, propose two or three time slots and step back. Do not oversell. The email is a handshake, not a pitch.

Decide in advance whether your rep joins the call. Reference programs differ here, and reps may or may not attend depending on what the prospect prefers. Ask the buyer. Many prefer to speak one on one, and honoring that signals confidence.

Step 5: Prep both sides without scripting

Prep is where good programs separate from risky ones. A short session 24 to 72 hours before the call should cover the prospect’s profile, likely objections, and a few do’s and don’ts. It should also explicitly invite the advocate to share honest experiences, including weaknesses, so nothing on the call surprises you.

The line you do not cross: never tell either party what to say. A coached reference is easy to detect, and a staged one can destroy credibility and turn an advocate into a detractor.

What prep should include:

For the advocate

• The prospect’s role, industry, size and top concerns
• The topics likely to come up: implementation, results, support, challenges
• Permission to be candid, plus a reminder that they can skip any question they are not comfortable answering
• Anything off limits for their own company, such as confidential figures

For the prospect

• Who the advocate is and how their situation resembles theirs
• A reminder that the conversation is theirs to steer
• A suggested list of questions, offered as a starting point only

For deals involving formal vendor reviews, our procurement reference prep guide shows how to move from request to matched call quickly.

Step 6: Run the call

Plan for about 30 to 45 minutes. The prospect leads. Your job, if you attend, is to make introductions, then be quiet.

A typical flow:

1. Introductions (2 to 3 minutes). Names, roles, a sentence on each company.
2. Context (5 minutes). Why the advocate chose the product and what alternatives they considered.
3. Implementation and results (10 to 15 minutes). How long rollout took, what changed, what the numbers look like.
4. Challenges and support (10 minutes). What was hardest, and how the vendor responded when something broke.
5. Wrap-up (2 to 3 minutes). Would they choose the vendor again, and what do they wish they had known?

Questions prospects should ask

Guidance on checking technology references points to the same themes. Prospects should cover why the customer chose the product, the alternatives considered, implementation time and impact, vendor interactions, problems, satisfaction, support, and whether they would choose the vendor again. Another guide adds what the customer wishes they had known, the hardest parts, and how the vendor responds when something breaks.

Turn that into a short list you can hand to buyers:

• What problem were you trying to solve, and why did you pick this vendor?
• How long did implementation take, and what did your team have to do?
• What results have you seen, and over what period?
• What was the hardest part?
• When something went wrong, how did the vendor handle it?
• What do you wish you had known before starting?
• Knowing what you know now, would you buy again?

Our customer reference calls guide has a fuller question bank organized by buyer role.

Step 7: Follow up and measure

The call is not the finish line. Within a day:

• Thank the advocate and the prospect separately.
• Ask the prospect whether they got what they needed and offer another call with a different customer if they want one.
• Tell the advocate how it went. When the deal closes, share the outcome. People who learn their help mattered say yes next time.

Track it like a sales process

Treat the program as a measurable part of the pipeline, not a favor desk. In practice that means linking every reference request to a CRM opportunity so you can see deals won and lost with and without references. Useful metrics to start with:

Watch time to match closely. A buyer who waits two weeks for a call has time to cool off or talk to a competitor.

Common mistakes in the reference call process

• Offering the same flagship customer every time. It overloads one person and often mismatches the buyer.
• Scripting answers. It backfires the moment a prospect asks a follow-up.
• Skipping consent. An advocate who feels ambushed will not help again.
• Waiting until the last week. Late requests lead to rushed matches and thin prep.
• Never closing the loop. Advocates who hear nothing afterward quietly drop out.
• Counting calls instead of outcomes. Activity is not impact. Tie calls to revenue.

Why authenticity decides whether the call works

Buyers can sense whether a call is real. That is the same principle behind everything that earns trust at the end of a sale: specific, verifiable, human voices. If you want the wider picture, this piece on how authenticity builds trust and growth shows why peer validation carries so much weight with late-stage buyers. For a sales-specific view, see our overview of ways to build brand credibility and how testimonials build trust for SaaS brands.

Our perspective

Most reference programs fail for a simple reason: they live in a spreadsheet and a few people’s memories. Someone in sales sends a Slack message asking who might talk to a fintech buyer, and three days later the deal has moved on.

We built Clareefai around the idea that a reference call should be as repeatable as any other step in your funnel. That starts with verified, contextualized customer voices stored in one place, so you know who your advocates are, what they have done and how they relate to each prospect. Our AI-powered promoter identification is designed to surface the customers most likely to be strong advocates, and our matching is designed to pair them with buyers by use case, role and scale.

We also believe the call itself should stay honest. The best references are not performers. They are real customers with real stories, and when you treat them well, ask first and share outcomes, they become ambassadors. Pair that with CRM integration and analytics, and your reference process stops being a favor and becomes a measurable sales asset.

ClareefAi

Put the process on rails with Clareefai

If you run reference calls by email and memory, the first thing to fix is speed and visibility. Clareefai gives sales and customer marketing teams one place to collect, verify and organize testimonials, video reviews and reference-call volunteers, then match them to opportunities and see what they influence in your CRM.

Plans are published on our pricing page: Basic at $250 per month, Professional at $624 per month and Enterprise at $1,250 per month. There is also a free plan to start with, and you can see how we handle unified testimonial management on our platform overview. If you want a walk-through, I’ll show you how matching and consent tracking work with your own customer list.

FAQ

How long does a reference call take?

Most B2B customer reference calls run about 30 to 45 minutes. Block 45 minutes on both calendars, and tell the advocate the expected length when you ask for consent so there are no surprises.

What should I expect on a reference call?

Expect the prospect to lead, asking about why the customer chose the product, how implementation went, what results they have seen, how support responds and whether they would buy again. If you are the advocate, you can be candid and skip anything confidential. If you are the prospect, come with your three or four biggest concerns written down.

Who should be on the call besides the prospect and the customer?

That depends on the buyer. Some prospects want the sales rep present to handle logistics, and others prefer a private conversation. Ask the prospect when you set the call up and follow their preference.

How do I choose which customer to offer?

Pick the customer who looks most like the prospect, not the biggest brand. Match on use case, buyer role, industry, scale and product experience, and check that the advocate has the bandwidth and the willingness to help right now. A structured database makes this far faster.

How is this different from a job reference check?

A job reference check is when an employer contacts a candidate’s former managers. A B2B customer reference call is the reverse direction: a buyer talks to a vendor’s existing customer to judge the vendor. The format is similar, since both are structured phone conversations, but the goals and the people involved are different.

Sources

• What Is Reference Call? Definition for SEs, PreSales Pulse
• Customer Reference, Saber glossary
• Customer reference matching without exhausting advocates
• Before Making an Email Introduction, Ask Permission, Harvard Business Review
• The Reference Call Prep Session, Pulse RevOps
• Selecting an ERP System: Checking Customer References, Visibility
• Reference Checks for Technology Partners, Launch Day Advisors
• How authenticity in branding builds trust and growth

Recommended

• Customer Reference Calls: Questions, Prep and Matching
• From Days to Seconds: Build a Customer Reference Database
• 7 Step Workflow to Reference Call Recording Consent for B2B Teams
• Cut Deal Time: B2B Customer Reference Program in 30–90 Days