A quote request from your website usually gets lost not on the site itself but after it has been sent: the email went to a shared inbox nobody checks, the notification ended up in spam, the sales manager is on holiday. For every request to reach a sales manager and get a reply, you need a short form, delivery of the request to a CRM or Telegram where it is sure to be seen, and an auto-reply telling the buyer the request has been received.
Below: exactly where requests get lost, which fields the form needs, what to connect it to and how to check that nothing goes missing.
Where quote requests from your website get lost
Enquiries usually go missing in the same places:
-
A shared inbox. Emails arrive at a general address that everyone and no one reads. Each person assumes someone else will reply.
-
A form that broke without warning. After a site update it stopped sending emails, and nobody noticed: there were simply fewer requests.
-
Spam. Emails from the site land in the spam folder, and the sales manager doesn't see them.
-
A sales manager's personal inbox. The manager is on holiday or has left the company, but enquiries keep arriving at their address.
-
Conversations on a personal phone. The buyer messaged you on Telegram via a link on the site, but it's one employee answering from their own number. When the employee leaves, the conversation leaves with them.
-
The file didn't attach. The form won't accept a large drawing or the right format, and the buyer gives up.
-
Silence after sending. The buyer couldn't tell whether the request had got through, and sent it to another supplier.
The worst part is that these losses are invisible. The buyer doesn't complain — they simply work with another supplier, while the company concludes that the website "doesn't bring in enquiries".
Which fields a quote request form needs
The form should collect what the sales manager can't start costing without, and no more. Every unnecessary required field is a reason to close the form.
-
Product. A choice from the catalogue or a description in the buyer's own words. If the request is sent from a product page, the field fills itself in.
-
Quantity. The batch size or approximate requirement — the buyer may not have an exact figure yet.
-
When it's needed. The date by which delivery is required. It determines whether you can take the order on.
-
Drawing or technical specification file. The form accepts the formats your customers work in and files of realistic size, not just small images.
-
Contact details. Name, company, phone or Telegram — whichever the buyer prefers.
The sales manager can clarify payment terms, delivery and packaging in conversation.
If a buyer doesn't want to fill in the form, give them another route: a "Message us on Telegram" button or an address they can send a drawing to. The key thing is that these channels also lead to the person responsible, not to someone's personal number.
And test the form on a phone: a buyer may be sending a request while out on a job, with the drawing in their phone's gallery rather than on a computer.
Where the request goes: a CRM or the sales manager's Telegram
A request should go where it gets worked on, not where it just gets stored.
-
A sales manager's or sales team's Telegram. A notification arrives on the phone, and the sales manager sees the request immediately. For a small team this is often enough. The downside is that a message is easy to scroll past, and the request's status isn't recorded anywhere.
-
CRM. The request becomes a deal with an owner, a status and a history. If the sales manager is on holiday, the head of sales sees the request. If the manager leaves, the customer stays in the database.
A combination is usually more reliable: the request creates a deal in the CRM and at the same time arrives as a notification in Telegram. If there are several sales managers, the CRM distributes enquiries by product line or in rotation, and if a request goes unanswered for too long, the head of sales gets a reminder.
Another advantage of a CRM is that the drawing is stored in the deal record, not as an attachment in someone's email. If the buyer gets in touch again, the system finds them by phone number or email and shows what they asked for before and what they were told.
And whoever handles enquiries, each person should have a stand-in for holidays and sick leave.
Auto-reply: request received, reply on its way
Immediately after sending, the buyer should see on screen that the request has been received. Then comes an email or message confirming it: the request number, exactly what was sent, who will reply and when to expect it.
For example: "Thank you, your request has been received and passed to our sales manager, [name], who will contact you [timeframe]. If you'd like to add anything, just reply to this message."
Write the auto-reply in the language the buyer used to fill in the form, and sign it with the sales manager's name, not "the site administration". Give a response time the sales team can actually meet: an honest timeframe is better than a fast one that gets broken. If costing takes time, say so: the sales manager will first get in touch to clarify details and send the quote afterwards.
The auto-reply settles the buyer's "did it get through?" question. And it gives you time to prepare the quote calmly: the buyer knows their request is already being dealt with.
The auto-reply is also a chance to share something useful: a link to the catalogue, certificates or a page about your production. While the buyer waits for the quote, they keep getting to know you.
Tracking enquiries: goals in analytics
To understand how many quote requests the website brings in and where from, set up a form submission goal in Yandex Metrica or Google Analytics. Then you can see how many enquiries came in over the month and from which sources: search, advertising, email newsletters. Track clicks on the phone number and the Telegram button as separate goals: some buyers don't fill in the form but message or call straight away.
Once a month, compare two numbers: how many requests analytics recorded and how many enquiries appeared in the CRM. If the CRM has fewer, enquiries are getting lost somewhere, and you know where to look.
Also keep track of how many enquiries turned into orders. If there are plenty of enquiries but few orders, the problem may be response speed or the quotes themselves — and that's a conversation to have with the sales team. We explain how to bring advertising, the website, the CRM and sales together into one picture in our article on end-to-end analytics.
If there are few enquiries to begin with, the issue is not losses but whether buyers can find you. That's the subject of our article on how a manufacturer can find wholesale buyers and dealers through its website.
Checklist
-
Test request. Send a request from the site yourself and check who received it and when.
-
Recipient. Requests go to a specific person responsible, not just to a shared inbox.
-
Files. The form accepts drawings in the formats you need and at realistic sizes.
-
Confirmation. The buyer sees straight away that the request has been received and knows when to expect a reply.
-
Cover. If a sales manager is on holiday, someone else sees their enquiries.
-
Analytics goal. Quote request submission is set up as a goal in Metrica or Google Analytics.
-
Reconciliation. The number of requests in analytics matches the number of enquiries in the CRM.
If enquiries from your website land in an inbox and then take on a life of their own, we can help connect the form to a CRM and Telegram and set up the auto-reply and analytics goals. There's more on our integrations with external services page and on the "Website for a manufacturing company" page. One example of our work is the website of BOFPCB, a printed circuit board manufacturer.