When you need a part you don't have, Intelligence finds it. The RFQ Agent sources from vendors. Email-to-RFQ reads their responses. Your team manages exceptions, not data entry.
A customer needs a part you don't have in stock. Or a work order requires a component that's not on the shelf. Someone on your team, whether purchasing or a sales rep brokering the deal, needs to find that part. They send RFQs to vendors, wait for responses, manually enter pricing and availability back into the system, compare options, and make a decision. When vendors reply by email, someone re-keys the price, condition, trace data, and lead time, line by line.
April 2026
When a customer needs a part you don't have, the clock starts. Every hour between "we don't have it" and "we found a vendor" is an hour the customer might buy from someone else. Today, that sourcing process is manual: someone identifies vendors, sends emails, waits for responses, follows up. For AOG requests, that delay can mean a grounded aircraft and a lost customer.
The RFQ Agent starts sourcing the moment stock runs out, not when someone notices. Vendor RFQs go out in minutes, not hours. Your team manages the decision, not the process.
When the Source of Supply Model can't find a suitable part in your inventory, it triggers a NO_STOCK signal. The RFQ Agent picks up that signal and takes action:
The Vendor Suggestion Model identifies qualified vendors for the part based on history, performance, pricing, and availability patterns. It recommends who to send the RFQ to.
The agent creates outbound RFQs and sends them to the recommended vendors, including part number, quantity, condition requirements, and any special instructions.
The RFQ Agent is part of the mesh architecture. It doesn't run on a schedule or wait for someone to click a button. It activates when a signal tells it a part is needed. The sourcing process starts itself.
Live
Vendor responses arrive as emails: unstructured, inconsistent, and scattered across inboxes. Someone on your team reads each one, finds the original RFQ it relates to, and re-keys the price, condition, trace data, and lead time into the system. This is pure data entry that adds zero value; the information already exists in the vendor's email. Every minute spent re-keying is a minute not spent evaluating options, negotiating, or closing the deal.
Email-to-RFQ eliminates the re-keying entirely. Vendor responses go straight into the RFQ record, matched and organized, ready for your team to compare and decide.
When a vendor responds to your outbound RFQ by email, the Email-to-RFQ agent handles it:
The agent reads the vendor's response email, extracting price, condition code, trace/tag data, lead time, and availability for each line.
Matches the vendor's response to the original outbound RFQ automatically. No hunting through email threads to figure out which request this is for.
Updates the RFQ record with the vendor's pricing, condition, trace documentation, and terms. The purchasing team sees all vendor responses in one place, ready to compare.
| Without Email-to-RFQ | With Email-to-RFQ |
|---|---|
| Vendor emails a response; someone re-keys price, condition, trace into the system | Vendor response parsed and entered automatically |
| Multiple vendor responses scattered across inboxes | All responses matched to the original RFQ, side by side |
| Data entry errors on pricing and trace data | Extracted directly from the vendor's email, no re-keying |
| Hours spent on vendor response management | Minutes reviewing and selecting the best option |
The agents handle the workflow. These models provide the knowledge that makes the agents effective at sourcing and evaluating vendor options.
This is how Intelligence knows where to look for parts.
The Source of Supply Model defines the search criteria for every inventory lookup: which locations to check, how to match condition codes, what trace documentation is required, how to rank results by lead time and availability, and what customer-specific requirements apply from the quote request and account record. When the RFQ Agent needs to determine what you don't have before sourcing externally, it starts with the Source of Supply Model.
This is how Intelligence knows who to buy from.
When the RFQ Agent needs to send outbound vendor RFQs, the Vendor Suggestion Model identifies the best vendors to contact. It considers vendor history, past pricing, performance, lead times, and availability patterns. Instead of your team manually deciding who to RFQ, the model recommends vendors based on your actual transaction data.
Here's how Intelligence supports the complete purchasing workflow:
Source of Supply searches on-hand inventory, alternates, on order, on repair, and secondary locations. Nothing found. NO_STOCK signal emits.
Identifies qualified vendors and creates outbound RFQs. Depending on your configuration, the agent can send automatically or pause for your team's approval before the RFQs go out.
Email-to-RFQ parses each response (price, condition, trace, lead time) and matches to the original request.
All vendor responses in one place. Select the best option based on price, lead time, and trace quality.
The sourced part flows back to the original customer quote. The Sales Agent can then allocate, generate the release, and close the deal.
Larger operations with a purchasing department manage vendor relationships and sourcing as a distinct function. Email-to-RFQ eliminates the manual data entry that consumes most of their day. The RFQ Agent handles the outbound sourcing they'd otherwise do manually.
In smaller shops, the sales rep who received the customer RFQ also handles vendor sourcing. For them, the RFQ Agent and Email-to-RFQ are extensions of the Sales workflow. The same person manages both sides, and Intelligence handles the vendor data entry so they can focus on the deal.
From outbound RFQ to vendor selection, automated sourcing inside AvSight.
Watch the sourcing workflow Schedule a demo