How can a buyer hear a real customer's experience without turning the conversation into a scripted testimonial or exposing private information?
Context
A prospective buyer had already reviewed the proposed service and design direction, but still wanted to understand what the process felt like from a customer's side. More company materials would not answer the underlying concern: whether the cross-border relationship and day-to-day service were genuine.
The specific problem
Sharing an existing customer's contact details without permission would breach trust. Choosing an enthusiastic customer and controlling the answers would produce a sales exercise rather than a useful reference. It would also be misleading to describe an ongoing experience as a completed end-to-end project.
Our diagnosis
The appropriate response was a voluntary, consent-based introduction. The reference customer needed relevant firsthand experience, freedom to describe strengths and open issues, and a clear boundary around what had and had not happened. FoshanBuild's role was to obtain consent and make the introduction, not to monitor or direct the private conversation.
How we handled it
1. Identify the buyer's real concern
We first separated a trust question from product, design, price, and contract questions. The buyer specifically wanted to hear how another customer experienced the service and what it was like to work across borders.
2. Ask a suitable customer privately
We approached an existing customer with relevant firsthand experience, explained why the conversation had been requested, and made clear that participation was optional. No contact details were shared at this stage.
3. Confirm consent and the scope of the conversation
The existing customer explicitly agreed to be introduced and to share an honest account. The reference remained limited to experience so far; an ongoing project was not presented as a completed delivery or a guaranteed result.
4. Let the customers communicate directly
Only after consent did we share the minimum contact information needed for a private conversation. FoshanBuild was not present in the conversation and did not provide a script, require a positive answer, or request access to the private exchange.
5. Keep the reference separate from formal safeguards
Both parties later confirmed that the conversation took place, and the prospective buyer said it made the next steps feel more comfortable. Contracts, verified payment instructions, product evidence, inspections, and professional checks still remained separate requirements.
What was recorded
- The prospective buyer explicitly requested direct contact with a real customer because of trust concerns.
- A suitable existing customer was asked privately and explicitly agreed before any contact details were shared.
- The two customers communicated directly without FoshanBuild participating in or directing the conversation.
- Both parties independently confirmed afterwards that the conversation had taken place.
- The prospective buyer later said the conversation made the next steps feel more comfortable.
- No payment, sale, contract, or commercial decision is attributed to the conversation.
Result and current status
The buyer received a firsthand perspective that company marketing could not provide. The conversation reduced uncertainty, while the consent record and clear scope protected both customers' privacy and prevented an ongoing experience from being presented as a finished-project endorsement.
For a similar project
- Ask whether the reference customer's experience is relevant to your main concern.
- Confirm that the reference customer has voluntarily agreed to speak.
- Ask what went well, what remained difficult, and what is still ongoing.
- Do not treat one customer's experience as proof of your own future outcome.
- Continue to verify contracts, payment instructions, product records, inspections, and local requirements.
Scope note
A customer reference is a voluntary account of one customer's experience, not an independent audit or a guarantee of price, quality, delivery, compliance, or outcome. An introduction can be considered only when a suitable customer is willing, both parties consent, timing permits, and privacy can be protected.
Based on the complete private conversation records, the consent and introduction records, and independent confirmations after the customer-to-customer conversation. Names, countries, contacts, exact dates, project details, payment information, and message text are not published.