A quote request is not finished when someone replies, “We will check.” It needs an owner, enough detail to prepare an offer, a realistic return time, and a record of what was sent. If the customer also writes through Instagram or email, the team should recognize the same opportunity without accidentally merging two different people. The practical answer is to treat each request as work with a visible status and next action, rather than a message buried in an inbox.
Record where the request came from, what the customer needs, which questions remain open, who prepares the quote, who keeps the conversation moving, and when the next update is due. Review unowned requests, pending approvals, and overdue commitments every day. A chat list or label can make a conversation easier to find; it does not mean a person has accepted responsibility or that a proposal has been sent.
Capture enough detail without turning the first reply into a form
Start with the information needed to route the request: the product or service, quantity or scope, location, and intended timing where those matter. If the price depends on a site visit, measurements, documents, or professional review, say so plainly and explain who will handle that step. Do not quote a price or delivery date the team has not confirmed. A short human reply should tell the customer that the request was received and identify the one missing detail that matters most. A string of automated questions can make an urgent inquiry feel ignored.
Keep a factual summary next to the conversation: entry channel, return contact, the need described by the customer, the agreed date, and files the customer chose to provide. Mark assumptions as assumptions. If someone starts a second conversation, verify identity before linking the records. A similar name or shared phone is not sufficient. The guide to mapping the customer journey across channels explains how to separate source, interaction, and opportunity without inventing one continuous story.
Avoid scattering personal details or customer documents into an informal spreadsheet available to everyone. Share only what the quote preparer needs and follow the operation's access rules. When a specialist must take over, pass on the context and a specific question. The customer should not have to repeat the full brief because the conversation moved between colleagues.
Give the conversation an owner, and the quote a producer
A “quotes” queue can be useful, but someone still needs to answer the customer. Distinguish the person accountable for communication from the person calculating price, inventory, availability, or technical feasibility. They may be the same person in a small team. In a larger operation, sales may keep the customer informed while operations prepares the estimate. Record both roles when they differ, each deadline, and what must happen before the offer can go out. The guide on conversation ownership develops that distinction.
Software behaves differently. Official WhatsApp Business guidance describes lists for organizing and finding chats in the app; the lists instructions note that availability and the transition from labels can vary during rollout. In dedicated service tools, Zendesk documents assignment to a group or agent, while Intercom distinguishes assignment to a team from assignment to a teammate. These are examples of vendor behavior, not claims that every tool works alike. Test the actual tool before relying on a queue as proof of personal ownership.
When no one can take the request, leave it visible as awaiting assignment and escalate it. Do not put an absent colleague's name on the work just to clear the list. During a shift change, the incoming person should accept the critical cases and see every promise already made. The shift-handover checklist can be adapted to a sales workflow.
Make quote status observable
Use a small set of states linked to real actions: received, waiting for customer detail, under review, waiting for internal approval, proposal sent, waiting for a decision, won, lost, or canceled. Define the evidence that moves a request forward. “Proposal sent” requires a sent copy and the document version; “waiting for the customer” requires an actual question or decision. Do not close a request simply because the conversation has been quiet.
Before sending an offer, check scope, terms, validity, and who approved it for this business. Do not copy conditions from an old quote without review. If there are several revisions, mark the current one and preserve the history. The person speaking to the customer needs to know which return time is safe to promise and when approval is still required. If the offer is declined, record the reason when the customer provides one; do not invent an objection to fill a CRM field.
A shared view should let the team open the conversation, see the last message sent, and identify the next action. The sales-to-support handoff guide is useful when the sale leads to onboarding, scheduling, or later service. The goal is not to multiply fields. It is to stop a quote from depending on the memory of whoever held the phone that day.
Follow up usefully and measure what went missing
Agree on the next update when the request arrives. If an internal answer is still pending, update the customer at the promised time even if the proposal is not ready. A follow-up should add value: confirm a required detail, explain a condition, or ask whether the decision has changed. Do not send repeated reminders just to press a silent lead. Honor requests not to be contacted and the rules of the channel in use.
Review four groups daily: new requests without an owner, overdue internal analysis, sent proposals without a next action, and customer updates promised for today. Assign a concrete action and person to each exception. The guide to keeping customer commitments covers due times, rescheduling, and completion evidence. In a weekly review, separate losses attributed to verified reasons from unanswered proposals. Silence alone does not prove the price was too high.
Useful measures include requests received, time to first human response, time to proposal, unowned requests, overdue promises, and conversion by origin when identity and attribution are reliable. Compare similar periods and read a sample of conversations before crediting a change to software or staffing. The lead-origin guide explains why a click, a conversation, a proposal, and an account created are distinct steps.
- Source, contact, and customer-stated need recorded as facts.
- Open questions, dependencies, and unconfirmed details marked clearly.
- Conversation owner and quote producer identified; transfers accepted.
- Review deadline and next customer update agreed.
- Proposal state backed by send evidence, version, and approval where needed.
- Unowned requests, overdue promises, and duplicates reviewed daily.
- Opt-outs honored; no repeated chase without a useful reason.
- Metrics interpreted with real examples rather than invented outcomes.