How to organise quote requests through WhatsApp

Associate the request with a reference, record the objective and identify missing information. Distinguish an initial estimate from an approved proposal and assign the next action. WhatsApp can start the conversation; organisation needs to preserve context, versions and decisions through to the final reply.

By Lyntev. Updated on .
About 5 minutes to read.

A request that stays connectedThe same reference follows the request and prevents duplicates.

Translation published on . Original Portuguese guide; source revision .

By the end, you can:

  • Collect the minimum needed to assess a request
  • Separate estimate, proposal and confirmation
  • Keep versions and the next action without unnecessarily repeating data

Identify the result the person wants

Start by understanding the task and conditions that change the work. “How much does a website cost?” does not identify pages, materials, a shop or functionality. “How much does repairing this cost?” may require equipment, symptoms and assessment. Ask a few questions at a time and explain why the information is needed. A lengthy interrogation can deter someone still trying to understand the options.

Record the objective clearly and separate what the customer said from what the team concluded. If you send a summary, allow an incorrect understanding to be corrected. Do not request invoicing details, documents or system access before the process needs them. Triage should create enough context to decide the next step, not collect everything that might become useful.

Give the request a reference and a next action

A long conversation can mix a quote, support and an earlier purchase. Create a way to identify the new request without losing its relationship to the contact. The reference can be simple as long as the team understands it and can search for it. Define who assesses it, what is missing and when it should be reviewed; a “quote” label does not represent that set of decisions.

Keep observable states such as “awaiting measurements”, “under assessment” and “proposal sent”. A state change should correspond to a fact. Do not mark a proposal as sent merely because an automatic message greeted the customer. If nobody has taken responsibility, the request remains unassigned and needs a triage destination.

From first contact to the quote decision
  1. Understand

    Objective, conditions and minimum information.

  2. Assess

    Person responsible, gaps and possible scope.

  3. Propose

    Version, inclusions and clear conditions.

  4. Confirm

    Recorded decision and agreed next step.

Illustrative flow; the tool should demonstrate how it preserves each stage.

Distinguish initial guidance from a specific proposal

You can help customers with an indication of scope or explain what determines the price, but state when assessment is still needed. An estimate should not look like a fixed commitment for unknown functions. In the proposal, identify inclusions, exclusions, stages, recurring costs and applicable external expenses, with variable charges approved before proceeding.

Choose a reference document or record for the presented version. The conversation can clarify and point to that content without spreading contradictory conditions across isolated messages. This guide organises commercial work; contractual conditions and sector-specific duties should be confirmed in the applicable context with the necessary support.

Organise materials without creating an excessive data folder

State accepted formats and what each material helps assess. An example photograph may be enough at an early stage; a complete document containing third-party information may not be necessary. Use an appropriate channel when content needs greater protection and explain how customers should send it. Do not ask them to publish attachments in an open space to make review easier.

Identify the version and destination of each relevant material, avoiding copies on uncontrolled personal devices. If an image arrives without context, associate it with the question needing clarification. If an attachment will not open, request a suitable alternative rather than assume its content. Quote quality depends on understood information, not the number of files received.

Work through a fictitious service request

Carpintaria Vale, a fictitious business, receives a message requesting a piece of furniture. The team confirms its use, approximate measurements and installation location without promising a final price from a photograph. It records reference PV-104, indicates that the material remains to be chosen and assigns assessment to a person. It then sends a proposal identified as version one, with scope and conditions.

The customer changes a measurement. The team retains the relationship to the request, reviews the impact and sends a new version, clarifying which replaces the previous one. The test checks whether another professional can understand the difference and continue the conversation. Values and results are not invented; the scenario exists to test continuity, not to represent a real order.

Record the decision and agree follow-up

Confirm the person received a proposal and knows the next step. A read message is not acceptance. If something changes, record what was approved or remains pending according to the defined commercial process. Avoid turning an availability question into a confirmed order without the necessary checks.

Agree relevant follow-up and respect the contact’s preferences and channel rules. Do not schedule a persistent sequence of messages because someone once requested information. If the person decides not to proceed, record only what is needed to close the request and learn about the scope. An unanswered request should have a review and person responsible rather than remain open indefinitely.

Test changes of version, person and channel

Prepare tests with an incomplete request, two requests from the same contact, a replaced proposal and an absent team member. Check whether the next person distinguishes these situations without asking customers for everything again. Also test the journey between WhatsApp and email or a form when the proposal needs another medium.

Track requests received, proposals issued, missing information and decisions using their own definitions. A rate of proposals sent may improve because you began refusing unfeasible requests earlier or because demand changed. Analyse the service type and loss reasons before attributing the effect to the tool. Organisation should enable better decisions, not merely produce more messages.

Keep a worksheet that fits the team’s process

Use the worksheet to ensure context, version and responsibility. It can live in a CRM, a management tool or a simple record with appropriate access. The chosen format should allow searching, correcting and closing a request without creating an unnecessary copy of the whole conversation. Define retention and attachment handling according to the purpose.

Before automating, try the worksheet with a few fictitious examples and ask another person to continue the work. If the next step is not obvious, improve the fields and rules. AI can help prepare a summary, but the team needs to check facts, conditions and commitments affecting the proposal.

Worksheet for your project

Request reference and objective:
Service and relevant conditions:
Confirmed information and missing information:
Necessary materials and appropriate channel:
Person responsible and next action:
Initial estimate or formal proposal:
Current version and changes from the previous one:
Inclusions, exclusions and costs to confirm:
Customer decision and appropriate evidence:
Agreed follow-up or closure:
Record retention and review:

Sources and criteria

Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.

Wellinton Oliveira

Written by

CEO of Lyntev

Technology with context, original analysis and sources you can consult.