What is RFQ automation?

What actually gets automated?

Job creation: the moment a document arrives, the system opens a job for it and identifies what it has, a drawing package, a BOM, a spec, or some combination, without a person copying attachments into a folder or a spreadsheet by hand. What gets priced and whether to bid stay separate, later decisions.

How does a new enquiry get triaged?

Every shop gets its own intake address, and only senders it approves can start a job, so triage begins with a simple check: is this a legitimate enquiry at all. From there, the system looks at what was actually sent: which document types are present, whether a BOM references drawings that were not attached, and whether the package looks complete enough to quote.

An incomplete package is not silently quoted anyway. It is flagged with exactly what is present and what is missing, so the person who picks it up knows immediately whether to proceed or request the rest from the customer.

How are duplicate or revised RFQs handled?

A second email about the same job, whether a reminder, a revision, or an added file, is matched to the existing job rather than treated as a brand-new enquiry. Where the documents themselves changed, that becomes a revision on the same job with the difference visible, not a fresh quote built from zero.

What happens to enquiries it cannot fully read?

They still create a job. Whatever could be extracted is extracted, and whatever could not is marked clearly rather than left blank or guessed at, so the person reviewing it can see exactly where to start.