How to Automate Customer Follow-Up After Sending a Quote

To automate customer follow-up after sending a quote, track each sent quote, assign its next action and check whether it still needs chasing before any reminder goes out. A fixed email schedule alone cannot account for a customer replying, calling or asking for a different price.

A customer's reply should pause the automatic chase, not mark the quote as resolved. Someone must review the conversation and record what happens next. If replies cannot reliably be linked to the correct quote, automate staff follow-up tasks before automating customer emails.

Define the quote record before scheduling messages

Start by mapping what happens between sending a quote and receiving a decision. Include the awkward routes: a reply to a different email thread, a telephone conversation, a request for revised work and a quote left waiting for an internal answer.

Choose one place where staff can see the current position. This might be the CRM or quoting software, provided it can hold the following information without a separate reminder spreadsheet:

• Quote reference and version: the specific offer being followed up, linked to the customer and intended recipient.
• Sent confirmation: when that version was actually sent, rather than merely created or approved.
• Responsible person: someone accountable for questions, exceptions and the next action.
• Current status: for example, sent and unanswered, under discussion, awaiting revision, accepted, declined, expired or closed.
• Next action and due date: distinguish a customer reminder from a staff call, review or revision.
• Last contact: the latest relevant message or recorded conversation.
• Reminder eligibility: whether automatic contact is permitted, including any manual pause or request not to chase.

Keep the quote's commercial status separate from its reminder status. A quote can remain open while reminders are paused because the customer has asked a question.

Choose a customer message or a staff task

A customer reminder is appropriate when the current quote was sent, remains unanswered and has a clear next step. It should identify the quote and make it easy to ask a question or give a decision.

A staff task is safer when there is something to interpret: a scope question, an uncertain reply match, a requested change, a delivery failure or a telephone conversation that needs recording. Do not send another chase while the customer is waiting for your team to answer.

Reply handling is a capability to demonstrate rather than assume. For example, QuoteRoutine describes matching replies to quotes, stopping its routine and flagging the quote for human response, with ambiguous replies routed for review. That illustrates the distinction your own process needs: stop the routine, but preserve responsibility for the unresolved quote.

Ask whoever configures the workflow to show what happens when one customer has two open quotes. Matching an email address is not enough to establish which quote the conversation concerns.

Build the follow-up sequence around current status

Start only when sending is confirmed

Use the event that confirms the quote has been sent, not the creation of a draft or an update to the customer record. If sending fails, create a task for the owner rather than scheduling reminders about a quote the customer may never have received.

Give each quote version one active follow-up sequence. Check whether the CRM, quoting tool or email platform already sends reminders, and choose which system controls them. Two independent schedules can both appear correct while sending duplicate messages.

Set an editable schedule with a purpose

Choose timing around how your customers make decisions. A straightforward repair quote and a project requiring several approvals should not automatically receive the same schedule.

For illustration, a business might schedule an initial check-in three working days after sending, then a staff review a week later if there is still no response. Those intervals are assumptions to test, not a recommended benchmark. A promised customer decision date should override the default.

A simple message could say: “I'm following up on quote Q-104 for the reception repairs. Do you have any questions, or would a later follow-up date suit you better?” Use a reply address the team monitors, and link only to the current quote.

Recheck eligibility immediately before sending

A message queued yesterday may be inappropriate today. Before sending, check that the quote version is current, its status still allows reminders, the next action remains due and no reply or manual pause has been recorded.

Chatley's follow-up documentation describes delayed message steps and stopping conditions including replies, quote acceptance and decline. It also recommends previewing and simulating workflows. For any chosen tool, demonstrate the timing of those checks, especially whether a queued message is cancelled when the status changes.

Where updates from email or quoting software arrive late, an immediate check can still miss a recent conversation. If that uncertainty cannot be controlled, route the due action to staff for review instead of sending automatically.

Specify what pauses, stops or replaces the chase

• Reply received: pause reminders and assign a review task. Resume only after someone records an appropriate next action and date.
• Telephone or other offline conversation: staff record a short note, update the status and change the next action during the conversation or immediately afterwards.
• Revision requested: cancel reminders for the old version. Keep a task open for preparing the revision; start a new sequence only once the replacement is sent.
• Accepted or declined: stop pending reminders. Do not infer either outcome merely because an email arrived.
• Expired or manually closed: stop the chase. If renewal is appropriate, give it a separate staff action.
• Failed follow-up email: flag the failure for the owner. Do not repeatedly resend without checking the address and failure reason.

No email connection can reliably account for an unrecorded phone call. Make recording the outcome part of the staff process, with an obvious pause control available while details are being entered.

Walk one quote through reply, revision and acceptance

Illustrative example: a maintenance company sends quote Q-104, version one. Its record shows “sent and unanswered”, a named owner and a reminder due on Thursday.

On Wednesday, the customer replies asking to remove part of the work. The workflow pauses the reminder and assigns the owner a revision task. The quote remains unresolved; the customer has neither accepted nor declined it.

The owner sends version two on Friday. Version one's pending reminders remain cancelled. Version two gets its own next action, based on the agreed review date rather than the original Thursday schedule.

The customer then accepts by telephone. The owner records acceptance against version two, stopping its reminders. If the owner forgets to record the call, the system may still see an unanswered quote. The implementation therefore needs both reliable connections and a workable staff habit.

Test the exceptions before enabling customer emails

Run the process with internal recipients first. Check the record, pending messages and staff tasks after each test, rather than checking only whether an email arrived.

• A reply just before a reminder: the reminder is suppressed and a review task appears. Test a reply that is still waiting to be processed, too.
• An unrecorded telephone discussion: confirm the workflow cannot detect it, then test that recording the call cancels pending contact.
• A revised quote: no message refers to the superseded version or links to its old price.
• A failed email: the owner receives an actionable exception, without duplicate retries or an incorrect “contacted” status.
• Two open quotes for one customer: an ambiguous reply goes to review rather than changing the wrong record.
• Acceptance or decline before sending: queued reminders are cancelled, including those scheduled by another tool.

Begin with staff-only tasks, then enable customer messages for a small, straightforward group of quotes. Review exceptions before widening the scope.

Use the existing CRM unless a missing connection prevents safe follow-up

Keep the process in your CRM if it can track quote versions, receive relevant replies, assign tasks and suppress pending reminders when circumstances change. Ask for a demonstration using your actual shared inbox and quoting process.

If the CRM cannot see quote acceptance, revisions or email replies, automation and integrations may connect those events to the follow-up record. Agree which system owns each field so an older update cannot restart a cancelled chase.

If reliable matching is still unavailable, a daily queue of quotes needing staff attention is a useful first implementation. It removes the separate reminder list while leaving customer contact with someone who can check the latest conversation.