A quote remains open in NetSuite, but that status does not tell the account manager what to say next. The buyer may be waiting for internal approval. They may need a delivery date your team has not confirmed. They may already have sent a PO to somebody else.
Useful follow-up starts by finding out who owes the next answer. Once you know that, you can send a message that moves the decision forward. Below are examples for common manufacturing sales situations and a way to automate them without chasing customers who have already replied.
Check what happened since you sent the quote
Read the latest customer reply and check whether your own team has an outstanding task. If engineering still owes the buyer an answer, the account manager should chase that internally before asking the customer to place an order.
Oracle’s estimate reports provide a starting point for reviewing quotations. Your follow-up queue also needs communication context that a quote total alone cannot provide. Keep it within the sales quoting process, with an owner and a next action for each active request.
Before scheduling another message, check for a PO, a recent reply and a revised quote. A request that already moved to order handoff should no longer receive sales-chasing messages.
Write the message around the decision you need
These examples illustrate a process; replace the details with the current customer agreement.
The buyer has not resolved a technical choice:
We can supply the coated or uncoated version. The coated option adds four working days. Which version should we keep on quote Q-218?
The buyer is approaching the quote expiry date:
Quote Q-218 is valid through Friday. If your approval will take longer, tell me your expected decision date and I’ll confirm whether we can extend the price.
You are waiting for a delivery decision:
We can send 16 tonnes first and the remaining 8 tonnes the following week. Would that meet the site schedule, or do you need one delivery?
Do not imply stock is reserved or prices will rise unless someone has confirmed it. Delivery promises need an operational basis, even when the message comes from an automated workflow.
For a manufacturing buyer, the unanswered question may concern the next production step rather than price. NIST MEP’s supplier-selection guidance includes capability and capacity checks. Give the buyer evidence for the issue they are actually evaluating.
If they are waiting to confirm your capacity, a useful follow-up identifies the proposed production window and asks whether their release date still holds. If engineering is reviewing a substitute, send the comparison and ask for the named decision. Record that answer before scheduling another message. Repeating “Have you reviewed our quote?” does not move either decision forward.
Agree a follow-up date with the buyer
An urgent replacement-part request and a capital-equipment project need different follow-up intervals. Agree a next date with the buyer where possible. If there is no agreed date, set a default interval for that kind of sale and change it when the buyer tells you their timetable.
Track the last meaningful customer reply, next action, owner and reason for waiting. Pause the sequence when engineering owes an answer; sending another reminder before completing your own technical clarification is poor service.
Oracle includes expiration information in its estimate import model. Use validity as one scheduling input, not as permission to invent urgency. If the customer needs an extension, have the pricing owner confirm the terms before the rep promises it.
Review whether follow-up produces useful customer answers
Review the share of follow-ups that produce a useful answer: order, rejection, revised scope or an agreed next date. Separate explicit losses from no response in your quote pipeline. Otherwise you cannot tell whether the problem is price, timing or poor qualification.
Bourne can combine the current estimate with the conversation history and prepare the appropriate next message. Start with approval before sending, then automate narrowly defined cases where your team trusts the wording and stop rules. Keep an owner for exceptions such as a buyer replying to an old revision.
Frequently asked questions
How many times should we follow up on a NetSuite quote?
There is no useful universal number. Set the cadence by the customer’s buying timetable and the urgency of the request. Stop or pause when the buyer responds, the quote becomes obsolete or your own team owes the next action.
Should an AI agent send follow-ups automatically?
It can for agreed cases after you test the recipient selection, quote version and stop rules. Keep approval for changed prices, technical claims and new delivery commitments.
What should we do when an old quote gets a reply?
Attach the reply to the original request and compare it with the current version. Confirm which terms the buyer means before restarting a sequence or preparing an order.
Further reading
NIST MEP: supplier selection
Practical supplier checks covering capacity, quality records and total cost.
Buğra Gündüz
Buğra Gündüz is the co-founder and CEO of Bourne and co-founder of HockeyStack. He built HockeyStack into an eight-figure AI business. At Bourne, he works with entrepreneurs and established companies to create AI products and services.