Inside sales receives a ten-line RFQ in Outlook. The buyer then replies with a quantity change, and the account manager forwards the thread to the shared mailbox. A useful integration should prepare one current NetSuite quote from that conversation. It should not create a quote for every message.
The work between Outlook and NetSuite therefore starts with understanding the request. After that, the workflow can match the items, retrieve prices and prepare an estimate for review. Here is how to connect those steps while keeping the original email available to the rep.
Start with the mailbox your team uses for RFQs
Start with the mailbox where the commercial team already receives RFQs. Identify who owns the queue and which messages count as new requests, revisions or follow-ups. Do not assume every email with “quote” in the subject needs an estimate.
In an email-to-quote integration, detecting a message and deciding what it means are separate steps. Microsoft documents message delta queries for tracking changes within a folder. A changed message may belong to a request already in progress, so the workflow must check that relationship before creating work.
Your implementation also needs permission to retrieve the content and attachments it uses. Confirm the tenant’s access policy and actual mailbox scope with IT. Do not request broad mail access merely because it simplifies a demonstration.
Follow the email through to a reviewed estimate
Use a visible state for each stage so inside sales can see where a request stopped:
- Receive the message and retain its identity and attachments.
- Associate it with a customer and an existing or new RFQ.
- Extract the requested lines and identify missing information.
- Resolve items and pricing against approved records.
- Present the draft and exceptions for review.
- Write the approved estimate, verify it and prepare the customer response.
RFQ intake handles request identity. Item matching handles product identity. Keeping those decisions separate makes a wrong customer match easier to correct without losing the original email.
Apply the buyer’s reply to the existing request
In our ten-line RFQ, suppose the buyer’s reply says “please make line 4 twenty units.” The review screen should show the original line quantity and the proposed change to twenty. The later forward adds context to that same request; it does not add another twenty units.
Preserve the original workbook and the later change. If a reply conflicts with an attached revision, ask which source governs. Do not use the newest attachment timestamp as proof of customer intent.
Stop any quote follow-up sequence when a relevant reply arrives. Have the workflow classify the next action before sending another scheduled reminder.
Treat a revised drawing differently from a request to change quantity. ASME Y14.35 addresses the identification of engineering revisions. The attachment’s email timestamp or filename should not replace the revision shown in the controlled document.
If the buyer sends drawing D after sales priced C, retain both and identify the affected lines before reusing the estimate. The email workflow can route the comparison to engineering and pause only the lines that depend on it. When the answer returns, link it to the quote revision that uses it so a later forward does not reopen an already settled question.
Verify the NetSuite write independently
Oracle exposes the estimate record through REST. The account’s features, fields and permissions still determine the implementation. Test a representative draft with required custom fields before automating a whole mailbox.
Store the resulting record ID beside the request. If the connection times out after submission, reconcile the result through your sync-error process before creating another estimate. Show whether the draft needs approval, whether NetSuite has saved it and whether the response has gone to the customer. A failure to send the email should leave the saved estimate available for another sending attempt.
Bourne is a strong fit when the work between email and ERP involves interpretation, history and multiple decisions. We can build the review workspace and connect the approved actions. A simple mail connector is enough only when the incoming data already identifies the customer, items and terms without investigation.
Frequently asked questions
Does Outlook integration mean every RFQ becomes a quote automatically?
No. Incomplete or ambiguous requests should enter a review queue. Define what makes a request ready for estimate creation and keep an owner for exceptions.
How do we prevent duplicate quotes from forwarded emails?
Track the message source and the commercial request separately. Match forwarded content to the existing request, then reconcile the resulting NetSuite record before another write.
Can the workflow send quotes from the shared mailbox?
That can be part of the configured deployment, with the required permissions and release rules. Test the sender, recipients, attachment version and customer approval state before enabling automatic sending.
Further reading
ASME Y14.35: engineering document revisions
Scope of the standard for identifying and recording drawing revisions.
Arda Bulut
Arda Bulut is the co-founder and CTO of Bourne and HockeyStack. He leads engineering at Bourne, building the platform people use to create AI products, agents and automations.