---
title: "Website quote requests: preparation and follow-up · Lyntev"
description: "Define useful information, the journey, attachments and the response to a website quote request. Includes a fictitious example and a customer service acceptance worksheet."
url: "https://lyntev.com/en/guides/prepare-website-quote-requests"
language: "en-GB"
date_published: "2026-11-21T17:20:13.047Z"
date_modified: "2026-11-21T17:20:13.047Z"
---

1. [Home](<https://lyntev.com/en>)
2. [Practical guides](<https://lyntev.com/en/guides>)
3. How to prepare website quote requests that the team can assess

# How to prepare website quote requests that the team can assess

A quote request should collect the information the team needs to decide the next step. It does not need to replace the entire sales conversation. Explain the service, ask for the details you actually use and confirm what happens after submission. Receiving a request does not mean a quote is approved, a visit is booked or a final price is agreed. Plan the journey with the people who respond, because a complete form without follow-up still loses opportunities.

By [Lyntev](<https://lyntev.com/en/company>). Updated on 20 November 2026.
About 6 minutes to read.

[Start reading](<https://lyntev.com/en/guides/prepare-website-quote-requests#leitura>)[Download worksheet](<https://lyntev.com/recursos/en/pedir-orcamento-pelo-site.txt>)

**A request that stays connected**The same reference follows the request and prevents duplicates.

Translation published on 21 November 2026. [Original Portuguese guide](<https://lyntev.com/guias/pedir-orcamento-pelo-site>); source revision 20 November 2026.

By the end, you can:

- Choose questions that help assess the request
- Avoid unnecessary data and attachments
- Confirm receipt and follow-up by the team

In this guide

1. [Define what the team can decide on first reading](<https://lyntev.com/en/guides/prepare-website-quote-requests#decisao>)
2. [Write questions the customer can answer](<https://lyntev.com/en/guides/prepare-website-quote-requests#perguntas>)
3. [Request attachments only when they have a defined purpose](<https://lyntev.com/en/guides/prepare-website-quote-requests#anexos>)
4. [Explain the next step without creating false commitments](<https://lyntev.com/en/guides/prepare-website-quote-requests#expectativa>)
5. [Fictitious scenario: air conditioning installation](<https://lyntev.com/en/guides/prepare-website-quote-requests#cenario>)
6. [Follow the request through to the first decision](<https://lyntev.com/en/guides/prepare-website-quote-requests#acompanhamento>)
7. [Approve the journey using a shared worksheet](<https://lyntev.com/en/guides/prepare-website-quote-requests#ficha>)
8. [Sources and criteria](<https://lyntev.com/en/guides/prepare-website-quote-requests#fontes>)

## Define what the team can decide on first reading

Choose a specific decision: confirm whether you can take on the service, request a photograph, arrange an assessment or prepare a proposal. List the information that changes that decision. If a field does not affect the next step and is not needed to make contact, question why it is there. Asking for everything in advance can increase work and require the team to handle information it does not yet need.

Speak to the people who respond to requests, not only those designing the page. Identify recurring questions and differences between services. A repair request may need the equipment and symptom; an interior design project may need the space and objective. If the journeys differ greatly, offer understandable choices and suitable questions rather than a universal form full of conditional fields that are hard to interpret.

## Write questions the customer can answer

Use the user’s language and allow them to say they do not yet know. Someone may not know a device’s power rating, the exact area or the technical name of the problem. They can state the objective, describe what they observe or send an appropriate item when necessary. Do not turn a lack of specialist vocabulary into a reason to block a request the team could assess.

Provide format examples and explicitly identify required fields. W3C guidance on validation and notifications explains the importance of helping people correct errors and confirming the result. Apply this to specific messages: say which information is missing and how to provide it. Avoid messages such as “invalid” without context or a page that deletes all the text when just one field needs correcting.

Write questions the customer can answer

| Information | When it helps | How to ask |
| --- | --- | --- |
| Service required | Determines the team or journey | Choose from options described in everyday language |
| Objective or difficulty | Allows the scope to be assessed | Explain what you need to resolve |
| Relevant location | Affects a visit, delivery or the work | State the area needed at this stage |
| Preferred timing | Helps check capacity | Preferred date, flexible or still to be decided |
| Contact details | Allows the conversation to continue | A usable channel and contact preference |

## Request attachments only when they have a defined purpose

Explain which image or document is useful and why. A photograph of the equipment may help; an identity document may be unnecessary for the first assessment. Define the formats and limits the implementation actually accepts and provide an alternative if submission fails. Do not ask customers to reduce or convert files without instructions they can follow.

Plan who can open attachments, how they check them and how long they need to be retained under the applicable rules. Avoid automatically sending every file to personal inboxes or tools used indiscriminately. This guide does not define a universal retention policy: that decision depends on the processing and context. The task here is to make collection proportionate and link the file to the right request with appropriate access.

## Explain the next step without creating false commitments

Before the button, state what submission starts. If the team needs to confirm availability or collect more information, say so. If response time depends on opening hours or capacity, publish only a condition you can meet. Do not promise an immediate reply when the request enters an inbox read only at certain times. Customers should know how to seek support if they do not receive the expected acknowledgement.

In the final message, confirm receipt when it has actually been recorded and provide a reference where one exists. Do not announce that the quote is complete without an assessment. W3C documentation distinguishes success and error messages and recommends understandable information. In operation, that message should be accompanied by evidence of delivery: the request reached the system or team and can be found so work can continue.

## Fictitious scenario: air conditioning installation

A fictitious business receives messages saying only “I need air conditioning”. Its first form now asks for the type of space, area, objective and a way to make contact. It lets customers indicate that they do not know the technical characteristics. The team uses the information to decide whether a conversation or visit is needed rather than automatically presenting a fixed proposal based on incomplete answers.

In a test, a photograph upload fails and the page retains the other fields while explaining an alternative way to make contact. The acknowledgement says the request will be assessed, not that installation is booked. The person responsible finds the reference and records the first reply. The scenario is fictitious, does not constitute advice on equipment sizing and does not represent a function automatically included in every Lyntev proposal.

## Follow the request through to the first decision

Define who receives requests, who covers for that person and how a new request is distinguished from one already handled. An email forwarded to several people can lead to duplicate replies or no reply. Use a simple process the team can maintain, with states and responsibility. If there is business management software, the connection must be tested; a button or advertised integration does not prove the request was recorded.

Test a complete request, an incomplete one, incorrect contact details and a repeated submission. Confirm appropriate handling and the information visible to the customer. Monitor request quality and the work needed to respond. Do not assess success only by the number of button clicks: what matters is whether the request arrived, could be understood and received appropriate follow-up.

- Each question has documented usefulness for the first decision.
- Errors can be corrected without unnecessarily losing work.
- The submission and attachments reach their intended destination.
- The acknowledgement describes the actual state and someone is responsible for follow-up.

## Approve the journey using a shared worksheet

Complete the worksheet with the person responsible for sales and the website supplier. Link each question to the decision it supports. Identify optional fields and situations in which people can ask for help. This allows discussion of the form’s simplicity without deciding only by the number of fields. An extra field can be useful when it avoids an incorrect assessment; an easy field can be useless if nobody uses the answer.

After publication, review questions and incidents using minimal information and anonymised examples. If many requests need the same extra question, try improving the explanation before making another field required. If you collect information you never use, remove it while reviewing the journey. The form should evolve with customer service and observed needs while preserving clarity and proportionality.

### Worksheet for your project

```
Website quote request
Service and the team’s initial decision:
Questions and the usefulness of each answer:
Information the customer may not know:
Required and optional fields:
Necessary attachments, formats and alternative:
Destination, reference and person responsible:
Message before and after submission:
Tests of errors, repeated submissions and incorrect contact details:
First reply and cover for the person responsible:
Review of collected data and frequently asked questions:
```

## 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.

- [W3C — validação de campos e ajuda à correção](<https://www.w3.org/WAI/tutorials/forms/validation/>)
- [W3C — mensagens de resultado do envio](<https://www.w3.org/WAI/tutorials/forms/notifications/>)

## Continue to your next decision.

- [Build an accessible contact form](<https://lyntev.com/en/guides/create-contact-form>)
- [Connect the request to sales follow-up](<https://lyntev.com/en/guides/connect-website-form-crm>)
- [Try Lyntev’s quote request](<https://lyntev.com/en/request-a-quote>)

This guide is part of [Create or improve your website.](<https://lyntev.com/en/guides#sites-e-presenca>)

- [How to prepare for direct bookings on an accommodation website](<https://lyntev.com/en/guides/prepare-direct-accommodation-bookings>)

[Explore the guide library](<https://lyntev.com/en/guides>)

## Would you like to apply this to your business?

Send us your worksheet or explain what you need to improve. We help you choose the next step for your project.

- [Lyntev assistant Immediate answers about services, prices and timescales, with a cost estimate. Read the assistant guide](<https://lyntev.com/en/help/ai-assistant>)
- [WhatsApp +351 928 412 891. The message is only sent when you confirm it in WhatsApp. Write on WhatsApp](<https://wa.me/351928412891?text=Hello!%20I%20came%20from%20the%20Lyntev%20website%20and%20would%20like%20to%20discuss%20a%20project.>)
- [Form Describe what you need and receive the reply by email. Complete the form](<https://lyntev.com/en/contact>)
- [Email contacto@lyntev.com Send an email](<mailto:contacto@lyntev.com?subject=Request%20for%20information>)

![Wellinton Oliveira](<https://lyntev.com/media/autores/wellinton-oliveira.webp>)

Written by

[Wellinton Oliveira](<https://lyntev.com/en/company>)

CEO of Lyntev

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