Practical workflow guide / After the quote

Automate quote follow-up
with clear stop rules.

A useful quote follow-up workflow starts with a confirmed quote-sent event, prepares a relevant next step and stops when the customer responds. It should not turn an unanswered proposal into an endless sequence of messages.

This guide covers the period after a quote is issued. If you still need to capture and assign the initial enquiry, start with the inbox-to-lead-tracker guide. Keep the two stages connected without treating every inbound message as a new opportunity.

By AIVIQ Enterprises Inc. · Updated 5 October 2026

01 / The trigger

Start from a recorded event.

Trigger the workflow only when an approved quote is recorded as sent. A saved draft or an email-open signal is not enough. Confirm which system supplies that event and how a corrected quote replaces the earlier version.

Use the quote ID and version to recognise repeated events. If a connection retries, update the existing follow-up rather than scheduling a second message. Check that the quote remains open before preparing any reminder.

02 / The record

Give the workflow enough context.

Agree a small set of fields before choosing software:

Quote ID and version: connect the reminder to the right document.
Sent date, expiry and next review date: use the agreed time zone and customer decision window.
Recipient and contact permission: use the approved channel, not another address guessed from a contact record.
Owner, status and last interaction: identify who can answer and whether the customer has already replied.
Stop reason: preserve why a sequence ended, including acceptance, decline or a request not to contact.

Missing ownership, unclear permission or an uncertain status should create an internal review task, not a customer-facing message.

03 / The useful message

Prepare a draft, not a commitment.

Choose timing with the business owner. There is no universal interval that fits an urgent repair and a planned project equally well. Start with one helpful reminder for review, using the issued quote and approved business information.

A person checks the recipient, current status, wording and send decision. Do not let a draft invent discounts, availability, expiry extensions or a new price. Any automatic acknowledgement needs a separately agreed boundary.

Fictional example / Not a client result

A revised quote changes the next step.

A fictional Vancouver repair business sends quote Q-104. Before its reminder is reviewed, the customer asks to remove one item. The workflow marks the quote revision requested, cancels the pending reminder and assigns the request to the owner.

“Thanks for the update. We have your request to revise Q-104. Our team will review the change and reply.”

This is an illustrative draft, not an automatically sent message. A revised quote needs its own approved version and next review date.

04 / Stops and exceptions

Check again before sending.

Stop pending reminders after a reply, acceptance, decline, expiry, opt-out or manual takeover. Recheck the record immediately before any approved send, because a customer can respond while a draft is waiting.

Treat ambiguous replies and out-of-office messages as review cases. If the mailbox or tracker is unavailable, pause the affected action and notify the owner. Record failures visibly. A retry must not send a duplicate or restart a completed sequence.

05 / Acceptance checks

Test the awkward cases first.

A repeated quote-sent event creates only one pending follow-up.
A missing owner or recipient blocks customer contact.
A reply arriving before approval cancels the pending reminder.
A revised, accepted or expired quote cannot use an outdated draft.
A failed connection produces a visible alert and a safe retry.
A person can pause the workflow and resume work manually.

Use fictional records first. Agree the expected result for each test and record what actually happened before introducing live data.

06 / Decide from evidence

Measure work completed, not messages sent.

Compare overdue follow-ups, review time, duplicate actions and missed stop events against the current process. A sent reminder is not a sale. The automation planning calculator can help estimate capacity after human review and running costs, without promising cash savings.

For earlier-stage enquiries, see lead follow-up with a human handoff. Keep quote-stage rules distinct so the same customer does not receive overlapping sequences.

AIVIQ / Vancouver-based, remote across Canada

Scope one quote workflow.

Tell us where quotes are recorded, which mailbox receives replies and who approves the next step. AIVIQ checks supported connections and agrees deliverables, exclusions and provider costs in writing. A quote workflow is not automatically covered by every starter package.

Request a written workflow scope Vancouver AI automation service

No compulsory sales call. Do not include customer records or passwords in the initial enquiry.