At many manufacturing and export companies in China, sending a sample, a drawing or a datasheet is treated as a favor from an individual salesperson. A buyer asks for a specification on a call or on WeChat (微信), the messenger many sales teams in China use with buyers, and the file goes out from a personal inbox within minutes. A drawing is forwarded as a chat attachment. The sample itself lives in someone’s notes or courier history. It feels efficient: the buyer has something to review, and the salesperson believes the request is done. Weeks later, a colleague asks which revision of the drawing went out, or whether the sample was actually shipped. The original salesperson has changed phones, or the thread has been buried under later messages. Who asked for what, which version was sent, and when shipment was promised—those answers are often already gone.
How a WeChat official account should publish content, how domestic search and content should connect to the website, how WeChat Channels generate leads, how to follow up after a trade show, and how official-account posts and website posts should divide the work—all have their own pieces, and this article will not reopen them. How a bilingual site should separately serve domestic and overseas buyers, what a buyer checks to verify that you are a real company, whether an inquiry can be completed inside WeChat’s in-app browser, and how to tell distributor inquiries from end-buyer inquiries are also outside the scope here. Which fields a form should keep, how to balance completion effort against lead quality, and what should happen after a submission is received, assigned and followed up, are likewise covered elsewhere. This article will not rewrite that field list, and it will not rewrite the four post-submit states. The narrower subject is this: requests for samples, drawings, datasheets and other technical documents often stop in a salesperson’s personal inbox or in a private chat. The company cannot see them, cannot hand them off, and cannot tell how far follow-up has gone.
A Technical Request Is Often Treated as a Personal Favor, Not an Inquiry
Treating it as a personal favor is easy to understand. The other person has already said what they need. Asking them to complete a form can feel like extra friction. Sending an attachment from the inbox the salesperson already lives in, or forwarding a PDF in the chat, takes a few minutes. Using a company entrance means explaining where it is, waiting for a submission, and waiting for a colleague to notice. The salesperson concludes that once the file has been delivered, the service is complete. If the company sees it the same way, the request is never recorded as an inquiry that someone has to receive.
Personal helpfulness does not survive a handover. After a personnel change, the person who picks up the conversation cannot see whether the request was for a particular model, a working condition or a general arrangement drawing. After a new device or a buried thread, it is equally unclear whether the file that went out was this year’s datasheet or last year’s, when the mounting dimensions had not yet changed. Samples scatter even more easily: the shipping address sits in some message, a ship-by date was promised somewhere, the courier record lives in one person’s app, and nobody can say whether the buyer confirmed receipt. If those facts exist only in a Sent folder or a private chat, the team cannot pick the conversation back up when the buyer asks again. What is lost is not whether anyone cared. It is the record a company should have of a technical request.
A request for a sample, a drawing or a datasheet is itself a strong signal of intent. The other party has usually moved past “what do you do” and is trying to judge whether a model or a solution fits their production line, project or operating conditions—and to pass the material to an engineer, a quality contact or a manager. Intent enters a follow-up rhythm only when the company has received it: who replies, whether the material has gone out, which revision was sent, and whether the next step is a sample or a technical call. A request that lives in a personal inbox or a one-to-one chat may still be remembered by the salesperson. To the company, it has barely happened. An intention the company cannot see is hard to assign, and hard to continue after people change.
Put a Matching Entrance on the Website, and Let the Request Arrive Where the Team Can See It
The website should offer an entrance that matches this kind of request, rather than printing a salesperson’s personal email at the bottom of the page and leaving it at that. The entrance can be straightforward: request a sample; download or apply for drawings and specifications. It should sit on the relevant product or service page, and it should say what information is needed this time—a company name, a contact method, the model or application range of interest, and, for a sample, a ship-to address and a note on quantity where that is required to respond. It should also say how you will reply after submit, and within what kind of time range the request will be handled. That range has to match the team’s real capacity. Do not publish a “sent immediately” or “same-day reply” promise the team cannot keep. Which fields belong on a form, and which should be required, is a separate subject, already covered in Which Fields Belong in a B2B Inquiry Form? Balance Effort and Lead Quality; this article will not rewrite that list. What has to be confirmed here is narrower: the entrance should make clear that this is a sample or technical-document request, and it should collect what is needed to reply or to ship—not a complete customer file.
The submission should arrive in a place the team can see, not only in one salesperson’s personal inbox. “Visible to the team” can mean a shared mailbox several people can open, or a form record that carries the type of request. You do not have to install a complex customer-management system before you start. The point is that when someone changes roles, takes leave or is traveling, another colleague can still see who asked for what, and when, and who should handle the next step. How to confirm receipt, assign an owner, and distinguish qualified from pending is already covered in After the Form: Build a Reliable B2B Lead Handoff and Follow-up Loop. This article will not rewrite those four states, and it will not argue for any particular piece of software. It stops one step earlier: the request should first appear as an inquiry in a place the company can actually receive.
Not every document should be available for public download. Product manuals, catalogs or a datasheet you have already decided may go out publicly are well served by a stable link, so what the buyer opens is the version you currently stand behind. Detailed drawings, interface dimensions, custom proposals or specifications that are not yet public are better handled as an application first, then sent under the arrangement you have agreed. This is not a way to hide documents in order to make buyers work harder. It is a way to attach each outbound file to a specific request, and to give the team a chance, before sending, to confirm what may be shared publicly and what needs a separate agreement. This article will not discuss how a confidentiality agreement should be drafted. The point is only that the check before an outbound drawing or specification should actually be done by the person responsible for sending it.
The entrance should still live on a page that makes the product or solution range, the conditions of use and the next step clear. A lone “request drawings” button, with no explanation of which models it covers or under what conditions they apply, still leaves sales filling in the operating conditions afterwards—and still makes it easy to send a file that does not match the page. How a service page helps a buyer see range, evidence and the next step is already covered in How to Write a B2B Service Page That Helps Buyers Take the Next Step; this article will not rewrite that structure. Without an explanation the buyer can check, the request entrance is only the chat message “please send me the file,” moved onto a web page. The company gains a record. The judgment does not get easier.
What Goes Out Should Be the Current Version, and It Should Match the Page
An old PDF forwarded in a hurry from a chat is the file most likely to fight the website. The page has already been updated with a new model range, a new mounting dimension or a tighter limit on use; the attachment that left an inbox or a WeChat thread is still last year’s datasheet. When the buyer forwards both the link and the file to an engineer, the two documents disagree. The mismatch is rarely an attempt to conceal anything. More often, a personal folder still holds the file that “always worked.” To a buyer, disagreement is a reason to ask another round of questions—and a basis for judging whether you keep your own documents under control.
What goes out, then, should be the currently valid version, and it should be consistent with the product range and application conditions shown on the website. The team should be able to check that the file name, date or revision number sent this time is the version you are prepared to stand behind now. For manuals that may be downloaded publicly, a stable link is less likely to go out stale than a file passed from person to person. For drawings or custom notes that are sent after an application, the record of that application should show which file was sent. The purpose of the check is not to build an elaborate archive. It is to avoid a follow-up in which sales and the buyer are each holding a document that contradicts the other.
The next action can stay specific. Open the product or service page from which samples or drawings are requested most often, and look at two things: whether the page has a matching request entrance, and whether a submission arrives where the team can see it rather than only listing a salesperson’s personal email; and whether the files colleagues actually send still match the current page. Then review one recent outbound sending: before it went out, did anyone confirm what could be shared publicly and what needed a separate agreement? Do not use the occasion to add every other qualification field at once; what else belongs in the first step still belongs to the field-design discussion. How requests are assigned and how their status is tracked after submit is covered in the form-to-deal article; this piece will not expand that. The entrance itself should still complete successfully; if the buyer opens the page inside WeChat, the request has to be able to go out first—that point has its own article, and this one will not expand it. To put “turning a technical request into a trackable inquiry” back into the larger question of being found, understanding the offer and starting a conversation, see our website acquisition guide. To compare which part of the path is currently stuck, the solutions overview shows what search, pages and technical work can each add. These are suggestions about how the work connects, not a promise of inquiry volume or conversion results.
VisioBound (增界) is operated by Shanghai Aigesihua Media Technology Co., Ltd. We help B2B companies with SEO, Google Ads and Baidu PPC management, GEO (AI-search visibility), on-site factory video production, and WordPress technical support. Based in Shanghai, we connect search, advertising, and content to clear service pages and inquiry paths for both domestic and overseas acquisition.
If you want to sort out how the website should receive requests for samples, drawings and technical documents, start with About VisioBound or contact us.
Frequently asked questions
Do we need a customer-management system before we can keep sample and drawing requests under control?
No. Start by letting the request arrive where the team can see it, making the outbound version checkable, and making sure someone can pick it up after it has been sent. A shared inbox or a form record that carries the type of request is often enough. Whether you later choose a more complete tool can follow volume, access and the complexity of collaboration; a tool cannot replace the fact of the company being able to see the request. Assignment and status tracking after submit are covered in the form-to-deal article; this piece will not rewrite those four states.
Should every drawing and datasheet be available for public download on the website?
No. Manuals, catalogs or a general datasheet you have already decided may go out publicly are well served by a stable link, so you are not passing around an attachment that may already be out of date. Detailed drawings, interface dimensions, custom proposals or specifications that are not yet public are better requested first, then sent under the arrangement you have agreed. Before a drawing or a specification goes out, confirm what may be shared publicly and what needs a separate agreement. How that agreement should be drafted as a legal text is outside the scope of this article.
If the buyer has already asked for the file in WeChat or a personal email, do we have to make them fill in the website form?
You do not have to push an already-started conversation back onto a form. Send the current valid version if it is appropriate to send, and at the same time record the request where the team can see it: who asked, what they asked for, which revision went out, and who owns the next step. If they will still need a sample, further drawings or materials their colleagues can forward, invite them to submit those later requests through the matching entrance on the website, so the company can receive what follows. Chat remains a good place to confirm a dimension or agree a time to talk. It should not be the only place the company can see that a technical request has been made.
