# Stop quote enquiries becoming forgotten promises

Give quote enquiries a clear owner, state and next update. Make details and dependencies visible so suitable requests keep moving toward a decision.

By Daltn editorial team. Published 2026-11-01.
Canonical: https://daltn.tech/feeds/follow-up-unanswered-quote-enquiries/

## How do you keep quote enquiries moving toward a decision?

Keep quote enquiries moving with a named owner, a clear state and a promised next update. Record missing details, supplier inputs or other dependencies so colleagues know exactly what prevents the next step. Reserve time to prepare suitable quotes and tell customers when a commitment changes instead of leaving requests indefinitely pending.

## Keep these in mind

- A quote queue should show why each item is waiting.
- A quick acknowledgement and a useful quote are different milestones.
- Review lost enquiries without inventing a universal loss percentage.

## Find the moment work becomes invisible

An owner reads a customer message between deliveries and intends to prepare the quote later. Nothing assigns the work or records when the customer expects an answer. By evening, newer messages have pushed the request out of sight.

The first fix is a capture habit, not a complicated lead score. Save the customer, requested item or service, quantity, required date and a next action. If the request is incomplete, the next action is a clarification rather than quote preparation.

A message marked read should never be the only indicator that someone owns the request. A colleague covering the queue needs to understand whether the business has acted.

## Define the quote states

Use a small set of states that tell the team what to do. Too many stages can create administration without improving the handoff.

State | Meaning | Next action
--- | --- | ---
New | Not yet reviewed | Confirm owner and request fit.
Needs details | Important inputs missing | Ask one clear clarification.
Preparing | Requirements sufficient | Prepare and check the quote.
Approval needed | Terms outside authority | Send evidence to approver.
Sent | Customer has the dated version | Agree an appropriate follow-up.
Closed | Won, declined or no longer active | Record outcome and reason.

## An illustrative backlog review

A small supplier has six open quote requests. Two need dimensions, one needs a supplier price, one awaits discount approval and two are ready to prepare. Calling all six pending hides the actual work.

The supplier assigns clarification calls, requests the missing price and gives the approver a complete decision pack. A staff member prepares the two ready quotes. Each customer receives a specific next-step message based on what the team can confirm.

The next day, the team can see whether the missing inputs arrived. That creates a controllable process even if every quote cannot be completed immediately.

## Measure the customer’s actual wait

[HubSpot’s sales analytics documentation](https://knowledge.hubspot.com/reports/create-sales-reports-in-the-sales-analytics-suite) illustrates that response reports use particular start and activity definitions. Decide yours explicitly: enquiry arrival to first useful response, and complete requirements to checked quote sent.

A shared enquiry address can improve coverage when configured appropriately. [Microsoft’s shared-mailbox guidance](https://support.microsoft.com/en-gb/outlook/sharing/open-and-use-a-shared-mailbox-in-outlook) describes group access to a common email address. Shared visibility still needs a named person responsible for each request.

Record why enquiries do not proceed. Price, timing, poor fit and no response are different outcomes. A small sample cannot establish that 30% of enquiries always go to competitors.

1. Capture each new request in the agreed queue.
1. Assign one owner and check the required inputs.
1. Promise a next response the team can realistically deliver.
1. Review the oldest open items and unblock specific causes.
1. Record quote and customer outcomes to improve the process.

## Make the promise easier to keep

Reserve actual work time for quoting instead of relying on leftover minutes. Escalate requests requiring specialist input early. If the date changes, inform the customer before the old promise expires.

Keep every enquiry beside the original requirements, quote owner and next promised update. Check incoming details before reserving time to prepare the quote. If a supplier price or technical answer is missing, record that dependency and tell the customer what happens next.

A simple queue is useful when it tells a colleague exactly how to move a request forward.

Start with one enquiry source and a short daily check. Expand only after the team can keep the queue current without turning it into another abandoned list.

## Common questions

### How do we stop a quote request disappearing into a queue?

Give it an owner, promised update and clear state such as missing information or ready to prepare. Record dependencies, review old requests and tell customers before a promised date passes.

### Should every enquiry become a quotation?

Check fit, requirements and commercial practicality before committing to a quotation. Give unsuitable requests a clear response rather than leaving them open. Separate waiting for details from a commitment to prepare a quotation.

## Sources

- [Create sales reports in the sales analytics suite, HubSpot](https://knowledge.hubspot.com/reports/create-sales-reports-in-the-sales-analytics-suite): Supports making response-metric definitions explicit.
- [Open and use a shared mailbox in Outlook, Microsoft Support](https://support.microsoft.com/en-gb/outlook/sharing/open-and-use-a-shared-mailbox-in-outlook): Documents common-mailbox access for a group.