PRIMARY PATH
xujingxu60@gmail.com
Ask buyers to send the checklist by email with file links or notes.
Email RFQRFQ / EMAIL-FIRST PATH
Prepare a clear RFQ for faster manual follow-up.
Send product family, model notes, application, quantity range, destination market, finish direction, and file links to xujingxu60@gmail.com.
EMAIL RFQ BLOCK
Make the main path obvious.
The page should not depend on a complex form. Email remains the reliable V1 path.
SUBJECT GUIDE
Promilink RFQ - product family
Encourage buyers to send organized requests.
FILE LINK
Share cloud links
Use links for drawings, photos, or product references.
RFQ CHECKLIST
Ask for fields that help real follow-up.
These fields support long-term customer asset building.
Ask buyers to include
Name and emailCompanyCountry or marketBuyer typeProduct lineModel notesQuantity rangeMaterial or finish preferenceProject or application typeOEM or packing notesFile links or notes
BUYER-SPECIFIC RFQ PROMPTS
Different buyers should send different context.
This helps Promilink collect better customer assets from the first email instead of receiving vague inquiries.
DISTRIBUTOR
Send range and market context
Useful details include destination market, target category mix, product families, and listing image needs.
View productsPROJECT BUYER
Send application and document needs
Useful details include application scenario, product family, installation context, and file request.
View applicationsOEM TEAM
Send references and review files
Useful details include photos, drawings, finish direction, packaging notes, and product matching goals.
Open OEMWHAT HAPPENS NEXT
Set expectations without overpromising.
Explain the manual follow-up flow while avoiding fixed promises.
REVIEW REQUEST
Human review
Promilink reviews the product family, file links, and sourcing context.
CONFIRM INFORMATION
Ask follow-up questions
Missing data can be requested before detailed discussion.
MOVE TO DISCUSSION
Prepare next steps
Final details should be confirmed after review.
SOURCE CONTEXT
RFQ should keep page context useful.
A buyer coming from PDP, OEM, Applications, or Resources should know what to include.
FROM PDP
Include product link or model notes
Helps connect the request to a specific product sheet.
FROM OEM
Include reference files
Photos, drawings, or samples help start review.
FROM APPLICATIONS
Include usage scenario
Application context makes product matching clearer.