Published October 2, 2026
Customer reference request coordination
A prospective customer asks to speak with someone who has used your service. The request seems straightforward until several colleagues suggest the same customer, nobody knows when that person was last contacted, and the proposed conversation expands beyond the original subject. An assistant can coordinate the process, but the relationship owner must remain accountable for whether the introduction is appropriate.
The aim is to reduce administrative friction without treating a customer's goodwill as an unlimited resource. A useful process makes the purpose, permission, and burden visible. It also gives the assistant a clear way to stop when a request lacks enough context.
Collect the reason for the request
Ask the requesting colleague what the prospect needs to understand. A general request for a “happy customer” does not provide enough direction. A specific question about working through a complex handoff, maintaining communication, or defining service scope gives the relationship owner something meaningful to assess.
Record the proposed participants, subject, expected format, and timing. Identify whether the prospect wants a conversation, written feedback, or permission to quote something publicly. These are different requests, and agreement to one should not be interpreted as agreement to all of them.
The assistant should also ask whether another resource could answer the question. An existing public explanation or approved written case example may be sufficient. A reference conversation should serve a real need rather than become a routine stage applied to every prospect without thought.
Keep selection with the relationship owner
The assistant can maintain a list of customers who have previously expressed willingness to consider requests. That list is a starting point, not standing permission. Current workload, recent service issues, and the nature of the requested discussion may change whether an introduction is suitable.
Ask the relationship owner to nominate an appropriate person and explain the relevant fit. Avoid selecting solely because someone responds quickly. Repeatedly routing requests to the most accommodating customer can create an uneven burden that remains invisible to the team.
| Decision | Assistant prepares | Relationship owner decides |
|---|---|---|
| Fit | Request context and previous contact history | Whether this customer is suitable |
| Permission | Clear invitation draft | Whether to approach and how |
| Introduction | Confirmed participants and subject | Any relationship-sensitive wording |
| Follow-up | Completion status and promised actions | Response to concerns raised |
Ask permission with a bounded invitation
A permission request should explain who wants the conversation, why, and what participation would involve. Make declining easy. The customer should not need to invent a reason or negotiate the request simply to protect their time.
Keep the invitation separate from the introduction. Until permission is received, do not put the customer into a group thread with the prospect. This preserves the customer's ability to consider the request without creating social pressure through an already completed introduction.
The assistant can send an invitation under an agreed process, or prepare it for the relationship owner to send. The correct choice depends on the existing relationship and the authority granted. Document the decision so it does not have to be rediscovered with every request.
Record the actual permission
Capture what the customer agreed to, including any subject boundaries or scheduling constraints. If the customer agrees to discuss a particular experience privately, do not expand that into permission to publish a testimonial. Preserve the distinction in the coordination record.
Record a refusal respectfully and without unnecessary detail. A simple note that the customer declined this request may be sufficient. Avoid retaining personal explanations that do not help future coordination, and do not interpret a refusal as a judgment about the customer relationship.
When the scope changes, return for permission. Adding participants, recording the conversation, or requesting public attribution can materially alter what the customer agreed to do. The assistant should flag those changes rather than letting them pass as minor scheduling adjustments.
Make the introduction useful
A good introduction gives both people enough context to begin. Include the agreed subject, relevant role information, and a clear next step. Do not provide a scripted endorsement or tell the customer what they should say about their experience.
For message design, consult the plain language guide. The assistant's practical job is to make the request understandable while preserving the customer's own voice. Avoid promotional wording that implies an opinion the customer has not expressed.
If the assistant coordinates scheduling, keep the conversation within the agreed scope. The prospect may ask for additional material or another call afterward. Those requests should return through the same permission process rather than becoming an open-ended obligation.
Track burden as well as completion
A reference record can show the date of the approach, whether it was accepted, whether the conversation occurred, and any promised follow-up. Include enough history to avoid repeatedly approaching the same person without awareness. Do not use the record as a ranking of customers by willingness to help.
Review the pattern with the relationship owner. If the same questions recur, the company may need clearer public explanations or better sales materials. Solving that underlying information gap can reduce the number of reference requests customers receive.
Close the loop with a courteous acknowledgment after the conversation. Confirm any follow-up before acting, especially if it involves another introduction or sharing additional information. The assistant should not assume that a successful conversation authorizes further use of the relationship.
Establish a clear stopping rule
Stop coordination when the purpose is unclear, permission is missing, or the scope has changed beyond what was accepted. Tell the requester exactly what is needed to continue. A bounded pause is more useful than repeatedly sending scheduling options while the central decision remains unresolved.
This workflow can sit within managed administrative support. If customer requests are consuming founder attention, a free consultation can help separate the recurring coordination from relationship decisions that should stay with you.
Frequently asked questions
Can we keep a permanent reference list?
You can maintain an internal coordination record, but a previous agreement should not automatically authorize a new request. Confirm suitability and permission in the current context. The record should reduce repeated work, not remove judgment.
What if the prospect wants a recorded call?
Treat recording as part of the request and obtain an explicit decision from the appropriate people before arranging it. Do not add recording to a conversation that was agreed as a private exchange. Follow your organization's applicable policies and requirements.
Should the assistant collect feedback afterward?
The assistant can ask whether the promised conversation occurred and whether an agreed follow-up remains. Questions about the customer's relationship or concerns may belong with the relationship owner. Define that boundary before the assistant sends a standard survey.