A quotation follow-up system should help the buyer make a decision and help the seller learn what is blocking it. It is not a schedule of repeated “just checking” messages. The system begins before the quote is sent, with clean requirements, clear scope, an agreed review step and one owner. It ends with an explicit outcome or a documented future trigger.
Place this workflow inside GPTWala’s CRM structure for manufacturers and wholesalers so every open quote has a status, next action and accountable person.
- Set the follow-up before creating the quotation
- Make the quotation easy to evaluate
- Create explicit quote stages and reason codes
- Use a context-led follow-up cadence
- Write follow-up messages that add information
- Route objections instead of arguing by message
- Automate reminders and records, not judgement
- Control versions, approvals and personal data
- Measure the quote funnel without misleading averages
- Use stage-based templates with human context
- Run a weekly open-quote review
- Frequently asked questions
- Sources and further reading
Set the follow-up before creating the quotation
Confirm the requirement, decision roles, quantity, delivery location, technical questions, commercial constraints and target decision date. Ask how the buyer will evaluate the quote and agree when to review it. A quotation sent without this context often becomes an unowned attachment.
| Pre-quote field | Reason | Minimum evidence |
|---|---|---|
| Requirement | Prevents quoting the wrong solution | Buyer-confirmed specification or brief |
| Decision process | Shows who and what affects approval | Roles, checks and target timing |
| Commercial scope | Prevents hidden cost disputes | Quantity, taxes, freight and terms basis |
| Review step | Creates a legitimate next contact | Date, channel and participants |
Make the quotation easy to evaluate
Use a controlled quote number, version, issue date, validity, buyer identity, item description, quantity, unit, price basis, taxes, freight, delivery basis, payment terms, exclusions and acceptance route. State variables and assumptions clearly. If an engineering or installation scope is separate, do not hide it inside a vague line item.
Link the relevant product data sheet or maintained digital catalogue instead of attaching uncontrolled files. Ensure that the quote and sales record refer to the same product and version.
Create explicit quote stages and reason codes
Use stages that reflect buyer reality, not seller optimism. Suggested stages are draft, internally approved, sent, receipt confirmed, under review, clarification or revision, commercial decision, accepted, declined, expired and nurture. Every active stage needs a next action and date.
| Stage | Required next action | Exit evidence |
|---|---|---|
| Sent | Confirm access and review date | Buyer received or opened through an approved system |
| Under review | Answer a specific question or wait for agreed date | Buyer status or meeting outcome |
| Revision | Record requested change and approval | New controlled version issued |
| Accepted | Confirm order, payment and fulfilment handoff | Purchase order or agreed acceptance |
| Declined | Capture reason and alternative | Buyer response or documented closure |
| Nurture | Record the real future trigger | Date, event or condition |
Use a context-led follow-up cadence
There is no universal best day for every quotation. A standard stocked item, custom manufacturing project and distributor agreement have different review cycles. Use the date agreed with the buyer, quote validity, production capacity and internal buying process. When no date was agreed, a short receipt confirmation followed by a reasonable review interval is safer than daily pressure.
| Contact | Purpose | Useful question |
|---|---|---|
| Receipt check | Confirm the quote is accessible and complete | Did the file arrive and is any information missing? |
| Review follow-up | Remove a decision blocker | Which technical or commercial point needs clarification? |
| Value follow-up | Add relevant evidence | Would a data sheet, sample or application call help? |
| Decision check | Confirm status and next step | Is the requirement active, changed or paused? |
| Close-loop message | Stop indefinite chasing | Should we close this version and revisit at a named trigger? |
Write follow-up messages that add information
Reference the requirement and quote number, summarise the purpose, add one relevant fact or answer, and ask one clear question. Keep the message short enough to reply to. Avoid invented scarcity, false deadlines, exaggerated results and generic attachments. Shopify’s sales follow-up guidance similarly frames proposal follow-up around the specific offer, buyer concern and a useful next step rather than a context-free reminder.
Use the buyer’s channel preference. If WhatsApp is used, follow the current WhatsApp Business Messaging Policy and keep evidence of opt-in for business-initiated messages. Review GPTWala’s WhatsApp consent workflow.
Route objections instead of arguing by message
Classify the blocker: technical fit, price or terms, timing, internal approval, competitor comparison, missing document, trust, no budget or no response. Send the right owner and evidence. A technical objection may need an application specialist; a price objection may reveal a quantity or scope mismatch; a timing objection may need a future trigger.
| Blocker | Diagnostic question | Possible response |
|---|---|---|
| Technical fit | Which requirement is not yet proven? | Data, sample, drawing or specialist call |
| Price | Which option or assumption is being compared? | Clarify scope, quantity and total cost |
| Timing | What event controls the purchase? | Record project or budget trigger |
| Approval | Who needs what evidence? | Provide an approval-ready summary |
| No response | Is the requirement still active? | Close the loop respectfully after the defined sequence |
Automate reminders and records, not judgement
Automation can create tasks, send receipt acknowledgements, surface quotes without a next action and stop a sequence when the buyer replies. It should not send repeated messages after a decline, ignore a changed scope or invent personalisation. Keep templates by stage and require the owner to review high-value or sensitive communications.
Connect automation to the small-business marketing automation framework, but separate marketing nurture from an active commercial quotation. A buyer can opt out of promotional communication while still receiving necessary transactional information through an appropriate channel.
Control versions, approvals and personal data
Only authorised people should issue or revise prices and terms. Preserve quote versions, approval evidence and the reason for a change. Restrict customer contact, drawings, pricing and payment information to people who need it. Do not paste confidential buyer data into unapproved tools.
Provide clear notices and respect applicable rights and withdrawal where personal data processing relies on consent. The DPDP framework has phased commencement and should be applied with qualified legal advice to the business’s facts.
Measure the quote funnel without misleading averages
Track quote count and value, time to issue, time in stage, revision rate, response rate, acceptance rate, lost reasons, discount pattern and revenue. Segment by product, source, buyer type, owner and complexity. A large engineered quote should not be compared with a repeat wholesale order as if their cycles were identical.
| Metric | Definition control | Decision use |
|---|---|---|
| Time to quote | Complete requirement to sent quote | Find estimating bottlenecks |
| Review engagement | Buyer response or meeting after send | Diagnose handoff quality |
| Revision rate | Quotes with controlled revisions | Find scope or pricing ambiguity |
| Acceptance rate | Accepted quotes divided by eligible closed quotes | Compare like-for-like segments |
| Loss reason coverage | Closed-lost quotes with valid reason | Improve product, offer and process |
Use stage-based templates with human context
Create a small approved library: receipt check, clarification, review invitation, revised quote, final validity reminder and close-loop message. Each template should contain editable context fields and one clear question. Train the team to remove irrelevant lines rather than sending the template unchanged.
Use GPTWala’s lead-qualification guide before quoting so sales does not use the follow-up stage to discover basic fit that should have been established earlier.
Run a weekly open-quote review
Review every open quote for current version, buyer status, next action, next date, owner, blocker and commercial risk. Close expired or dead records with evidence instead of leaving them permanently open. Escalate capacity or delivery promises that no longer match operations. Monthly, analyse loss reasons and revise qualification, quote design or proof assets based on repeated patterns.
Frequently asked questions
How do you follow up after sending a quotation?
Confirm receipt, follow the agreed review date, address one specific blocker or add relevant evidence, and ask one clear question tied to the buyer’s decision.
When should you follow up on a quote?
Use the review date agreed with the buyer and the real buying cycle. If none was set, confirm receipt and choose a reasonable interval based on complexity and urgency.
What should a quotation follow-up message say?
Reference the requirement and quote number, state why you are contacting the buyer, add useful context and end with one easy-to-answer question.
How many times should you follow up on a quotation?
There is no universal number. Use a defined sequence appropriate to the deal, stop when the buyer declines or opts out, and record a real future trigger when timing changes.
Can quotation follow-up be automated?
Tasks, acknowledgements, reminders and sequence stopping can be automated, but scope changes, objections, high-value messages and commercial judgement need human review.
How do you track quotation conversion?
Connect quote version and value to stages, buyer engagement, revisions, acceptance, revenue and controlled loss reasons, segmented by comparable deal types.
Sources and further reading
- Shopify: sales follow-up practices and templates
- WhatsApp Business Messaging Policy
- MeitY: Digital Personal Data Protection Rules, 2025
Policy and legal material is provided for operational awareness, not legal advice. Verify the current rules and obtain qualified advice for your circumstances.