Four things to record after every quote follow-up

A note saying “called customer” leaves the next person guessing. Did anyone answer? Was there a question about the windows? Does the customer expect a reply, or should contact stop? Record enough to answer those questions before another colleague picks up the quote.

This guide is for window, door and enclosure teams following up documents they have already sent. Whether your business calls that document a quote or an estimate, identify the exact version discussed. A follow-up note records the conversation; it does not change the document’s scope or terms.

Four questions every note should answer

1. What actually happened?

Record the action, date, channel and observed result. “Phone call: no answer” is a result. “Not interested” is an interpretation unless the customer said so. When there is a reply, note the specific question or request rather than writing only “customer replied”.

2. Is another contact appropriate?

A reply changes the work to do. A technical question calls for a checked answer, not the same reminder again. A request to wait should be recorded with the period the customer mentioned. If they ask for no further contact, record that request and stop follow-up contact.

3. Who owns the next step?

Name one person responsible for the action. “Sales team” does not tell a colleague who will answer a glazing question or check installation details. If a technician must provide information, distinguish the person checking it from the person responsible for replying.

4. What happens next, and when?

Use a concrete action: “check whether removal of the existing frames is included” is clearer than “follow up”. Distinguish an internal review date from a date agreed with the customer. An unanswered call does not create an agreed appointment.

A note template you can reuse

Keep this note with the quote in the shared place your team already uses. Link to the actual document and relevant correspondence rather than copying a whole conversation. The labels below describe a working method, not a list of QuotixLab fields.

• Document: [quote reference and version discussed].
• Action: [date, time, channel and team member].
• Observed result: [reply, no answer, question or explicit request].
• Next step: [one action, or no further contact].
• Owner and date: [named person, deadline, internal or customer-agreed].
• Limits: [wait for a check, respect a postponement, stop contact or another relevant constraint].

Three examples for a window and door team

These are illustrative notes, not real customer cases. Replace the references, people and dates with the facts of the conversation. Keep only details needed to understand the work.

No answer after a call

“Quote W-104, version 2. Called on [date] at [time]; no answer, no voicemail left. Owner: [name]. Next step: check the shared inbox for a reply before deciding whether another contact is appropriate. Internal review: [date]. No appointment agreed.”

This separates the completed call from the next internal check. Do not record that the customer saw the quote, rejected it or wants another call without evidence. If a message was left, record that instead.

A question about the installation scope

“Quote D-208, version 1. Customer asks whether removal and disposal of the existing door are included. Owner: [name]. Next step: verify the scope with the installation lead, then reply by [agreed date]. No revised price or installation date confirmed.”

Record the exact point to check. If the answer leads to a revised quote, identify the new version and explain what changed. A requested change is not an accepted change, and a request for a site visit is not a confirmed booking.

The project has been postponed

“Quote W-315, version 3. Customer says the renovation is postponed and asks us to wait until [period]. Owner: [name]. Next step: review the request at that point before considering further contact. No exact call date or quote acceptance agreed.”

A postponement, a rejection and a no-contact request are different outcomes. Do not turn all three into “call later”. If the customer asks to end contact, make that clear to whoever takes over.

Keep drafts, actions and outcomes separate

A prepared email is not a sent email. A promised answer is not a completed check. Record what your team has done, what the customer has actually said and what remains to be done as separate facts.

The HubSpot documentation on logging activities distinguishes activity details, date, outcome and a follow-up task. The template here applies that distinction to quote handovers; it does not imply a HubSpot integration.

Before another colleague takes over

• Can they open the right quote version?
• Can they identify the observed outcome and any limit on contact?
• Is there one owner and one clear next step, with the date labelled correctly?
• Are unresolved technical questions visible without presenting an unverified answer as confirmed?

Keep the history when the next action changes. Add the new outcome instead of rewriting an earlier call as if the team had known more at the time. The purpose is a usable record, not a longer note.

If you want to assess QuotixLab for organising follow-up of quotes already sent, request the Founding Pilot. Requests are reviewed; submitting one does not activate access immediately.