Share Customer References With Permission

A prospect asks to speak with a customer. Sending a name, email address and phone number is fast, but it can leave the customer fielding unexpected questions from people they never agreed to meet. A reference should be a coordinated introduction, not an exported contact list.

Ask the buyer what they need to learn, find a relevant reference, obtain permission for the specific introduction and share only the information needed. Confirm the scope with both parties and keep a record of the agreement. A customer's approval of a public quote does not automatically authorize direct calls.

This guide covers the operational reference workflow. Where personal data is involved, your privacy owner should determine the appropriate basis and handling. The ICO's consent guidance emphasizes specific information and recording consent where consent is relied on. ICO: Obtain, record and manage consent

1. Define the question before choosing a reference

Ask the buyer to name the decision they want the reference to inform. A question about implementation effort differs from a question about ongoing support or a particular workflow. Choosing the largest logo without checking relevance can waste the customer's time and produce an unhelpful conversation.

Record the buyer's company, evaluator role, proposed questions and intended use. If they intend to quote the reference in an internal memo, explain that to the reference before arranging the call. If they want a recorded session or a published quote, treat those as additional permission requests rather than assuming they are included.

Identify a reference with an actual relevant experience. Check that the person still holds the role and is authorized by their organization to discuss it. Do not imply they implemented a feature simply because their employer bought the product. A reference should speak within their direct knowledge.

Keep the request manageable. A focused conversation with three questions is easier to approve than an open invitation to provide unlimited support. Set realistic scheduling expectations and offer other approved evidence if a reference is unavailable.

Do not promise the buyer that the customer will endorse every claim. The reference may describe limitations or tradeoffs. That is useful evidence, not a problem to script away.

2. Request permission for the actual introduction

Contact the potential reference through the approved relationship owner. Explain who is asking, what the discussion concerns, which contact information you propose to disclose and how scheduling will work. Make it easy to decline or suggest a narrower scope.

An illustrative request could say: “A buyer evaluating our reporting workflow would like to ask about your rollout experience. May we introduce their operations lead to you for one scheduled conversation about that workflow? We would share your work email for scheduling only. Recording or public quotation is not included in this request.”

Adapt the language to your organization's policy and the person's situation. The goal is understandable permission, not a broad legal template. Do not make a customer feel that support, pricing or goodwill depends on accepting the request.

Record what was approved. A simple record can include the reference, buyer, purpose, allowed contact channel, scope, information date and any limits. Preserve the actual confirmation rather than replacing it with a salesperson's unchecked “yes” field.

Check whether organization-level authorization is also needed. A person may be willing to speak while their employer restricts external references. Do not treat personal willingness as permission to disclose confidential employer information.

If your team maintains a general reference program, verify that this introduction falls within its current permissions. A blanket list labeled “approved references” is insufficient if it does not explain the audience, topics and time limits. Review stale permissions before reusing a contact months later.

3. Share a brief, not a private customer dossier

Prepare a short reference brief containing only approved information. Explain the relevant use case, the reference's role in it and what the buyer may ask. Do not attach customer contracts, pricing, private usage logs, support tickets or unrelated documents to make the introduction look more substantial.

A controlled document link can help distribute an approved brief to the buyer group, but it does not turn an unauthorized disclosure into an authorized one. Review content first, then select access settings. Do not create a permanent public reference directory from private introductions.

Prefer coordinated scheduling over publishing direct contact details broadly. If your team arranges the meeting, the buyer may not need the reference's phone number at all. A small reduction in disclosed information can make the reference more comfortable without obstructing the conversation.

Check the brief on a recipient device before sending it. Make sure the buyer sees the approved summary and not internal account notes in adjacent folders or a spreadsheet tab. A reference list exported from a CRM can contain substantially more information than the buyer needs.

4. Set expectations for the conversation

Send both parties the agreed topics and meeting purpose. Tell the buyer that the reference is discussing their own experience, not acting as your support engineer or promising your product's future capabilities. Tell the reference who will attend so unexpected participants do not appear without context.

Clarify recording and note-taking before the session. If recording is requested, ask through the appropriate process and allow the reference to decline. Do not switch on recording because the meeting software makes it easy. Permission for one conversation is not permission for an indefinitely reusable video testimonial.

Avoid scripts that require the reference to repeat claims they cannot support. You can provide context and a proposed agenda, but the person should be able to describe their experience accurately. If there is a material benefit or incentive connected to an endorsement, have the responsible owner review its treatment and disclosure. FTC guidance requires endorsements to be truthful and not misleading. FTC: Advertisement endorsements

After the conversation, ask the buyer whether their original questions were answered. Do not assume the meeting proves the deal is approved. If a question remains open, route it to the appropriate product or implementation owner rather than asking the reference to supply an unsupported answer.

Thank the reference and respect the agreed boundaries. A second buyer request is a new scheduling decision, not an automatic extension of the first permission. Track reference workload so enthusiastic customers are not repeatedly asked for favors they did not intend to provide.

5. Worked example: a relevant reference without overexposure

Imagine a fictional vendor called Willow Reports and a fictional buyer called Eastbay Services. Eastbay wants to understand the work required to introduce a reporting workflow to a small operations team. Willow identifies a customer contact who participated in a similar rollout.

The relationship owner asks whether the contact will speak with Eastbay's operations lead about setup and adoption. The contact approves one scheduled conversation, asks that no recording be made and does not want a personal phone number shared. These are illustrative choices, not a real customer's permission record.

Willow sends a brief with the approved role and workflow summary. It schedules the call through the work email channel without giving Eastbay a customer contract or detailed account history. The agenda includes three practical questions about preparation, rollout friction and lessons learned.

During the call, the buyer asks about a product capability the reference does not use. The reference says so. Willow routes that question to its product owner instead of presenting the customer's silence as confirmation. Afterward, it records that the introduction occurred and that the original scheduling purpose is complete.

If Eastbay later requests a public quote, Willow makes a separate request with the exact wording and proposed publication location. It does not use meeting notes as a testimonial. The example's useful outcome is an honest, scoped exchange that respects the reference's time and control over their information.

6. Recover from an unapproved introduction and verify future requests

A typical failure happens when a seller forwards an old reference list to a new buyer. The list may include people who changed jobs, withdrew permission or agreed only to a different audience. Stop distributing it and involve the relationship and privacy owners to assess what was shared and the appropriate response.

Do not quietly replace the list and assume the issue has disappeared. The original recipient may still have a downloaded copy. Clarify which contacts were not approved for the introduction and ask them not to use those details, following your organization's process.

For the next reference request, verify:

• The buyer question is specific and relevant.
• The person has direct experience with the claimed workflow.
• Their contact details and role are current.
• Permission covers this buyer, purpose and contact channel.
• Any organizational approval requirement has been addressed.
• The brief contains only approved information.
• Recording and quotation are treated separately.
• The introduction does not expose private account materials.
• Follow-up requests require an appropriate new check.

If a reference withdraws from the program, update the source record and stop future introductions within the applicable process. Keep only the records your organization is authorized to retain. A healthy reference program makes refusal straightforward and does not treat customer goodwill as an unlimited resource.

Frequently asked questions

Is approval of a case study enough for a reference call?+

No. Written case study permission and direct contact permission cover different activities. Confirm the proposed buyer introduction, topics and contact channel before sharing details. Existing permission may cover it, but its scope must be checked.

Should we let buyers contact references directly?+

Only when the reference has approved that arrangement. Coordinated scheduling often reduces unnecessary contact disclosure and repeated requests. Make the allowed follow-up scope clear to both parties.

Can we quote the reference after the call?+

Do not turn notes into a published quote without approval for the wording and use. Recording, quotation, website publication and future sales distribution can each require separate review. Keep the permission record tied to the exact approved material.

Before you share

A strong reference introduction begins with a useful question and specific permission. Share the minimum information, coordinate the conversation and let the reference describe their real experience without pressure.

Parent guide

• What Belongs in a Digital Sales Room?

Related articles

• Share Case Studies Under Customer Restrictions

• Build a Buyer Business Case With Evidence

• Share Sales Documents With a Buying Committee

Sources and editorial disclosure

Primary documentation reviewed October 11, 2026. Examples, templates and checklists are illustrative editorial recommendations unless explicitly identified otherwise. Product settings and entitlements may change.

• ICO: Obtain, record and manage consent

• FTC: Advertisement endorsements

VDR Directory is published by the SendNow team. Product references are limited to documented capabilities; this guide does not report a signed-in product demonstration or a completed customer project. Stock photos illustrate the surrounding workflow and do not prove feature behavior. No ranking, revenue, compliance or legal outcome is guaranteed.