How to keep quote changes with customer follow-up
Website edition prepared November 7, 2026. The archive date is a reading order; the source news date is listed below.
A returning customer asks to add one item to a quote. Your colleague opens a newer document, but it is still a draft. The useful next step begins with finding the version the business actually approved.
1Find the approved version
2Capture the new request
3Assign the comparison
Integrations are scoped and tested separately.
The update behind the idea
Salesforce’s November 5 announcement lists Conversation History and reusable Skills for Agentforce Coworker among its available capabilities, subject to the applicable agreements. Other experiences are described within a November availability window. Those product details provide a starting point for discussing how employees return to earlier work.
Give the original quote a stable reference
Consider a small maintenance company quoting work at two properties for the same customer. A new website request should preserve the property, the customer’s wording and any quote reference supplied. The employee can then verify the connection to the appropriate project.
Show the approved version beside the change request. Keep its issue date, document link and responsible estimator together. A newer file should not automatically become the approved scope merely because it was uploaded last.
The customer may remember a price without remembering which options it included. Keeping the underlying document available lets the estimator compare the request with the actual scope instead of reconstructing it from a summary.
Make a change easy to review
A useful handoff might say that the customer wants another service added and has asked about Saturday. Record both as requests. Give the estimator a task to check the scope and availability, with the approved quote attached.
An assistant can help prepare that comparison from the records it is permitted to read. The employee still checks the original, resolves conflicting versions and decides whether a revised quote is ready. A remembered conversation alone does not authorize a new price.
Try a returning-customer test
Use a fictional customer with two projects, an approved quote and a later draft. Submit a change from a phone. Ask a colleague to find the correct original and explain which decision remains open. The test should also cover a missing reference, so the process asks for clarification rather than guessing.
For a ProgressorAI website and CRM discussion, this is a useful starting record: what was approved, what the customer now wants and who owns the review. The workflow shown here illustrates that approach.