A quote request has arrived. What happens next?

A quote request arrives with a name, a phone number and a few sentences about the work. The notification lands in your inbox. You read it, then a call comes in, followed by an urgent fix and a meeting. By the afternoon, you are searching for the message that contained that useful detail.

Consider this a simple example, rather than a client case study. It helps explain where automation can be useful. The form already works. The question is how an incoming enquiry becomes a clearly defined piece of work that the business can take on.

Make the current state visible

An email alone does not tell you whether someone has dealt with the request. A read marker means it was opened. It may still be unanswered, incomplete or waiting for a colleague to make a decision.

I would start by naming the states: received, awaiting clarification, quote in preparation, sent and closed. Each should also show who is responsible and what needs to happen next.

A shared spreadsheet may be enough to begin with. What matters is that everyone can find the answer in the same place. If the next action exists only in the owner's memory, the process still depends on the owner being available.

Let the information move on

If the form already contains the name, address and description, nobody should have to copy them into another system. Give the enquiry its own record and connect the subsequent correspondence to it.

This is a useful starting point for automation. A system can record the arrival, assign the agreed owner and flag a missing piece of information. It should also handle repeated submissions: sending the same form twice should not silently create two separate jobs.

Exceptions need to be visible. An invalid phone number or a missing attachment should remain an open problem, rather than disappear behind a successful completion message. The next person needs to know what they can actually work with.

AI can prepare the work

A free-text enquiry may contain useful information in no particular order. Artificial intelligence can help by producing a short summary, extracting questions and preparing a reply for review.

For example, someone may explain what they want to build without saying who would use it. A draft reply can ask that question. The system should make clear which details came from the original message and which still need to be established.

I would require approval for the price, delivery date and scope of work. Those are business decisions. Preparing the reply can be delegated while responsibility for the commitment remains clear. The process needs an explicit place for that decision.

Keep the acknowledgement accurate

It is useful for the sender to know that their enquiry arrived. A brief acknowledgement can explain what was received, what happens next and whether any further information is needed.

Only promise a response time the business can meet. If nobody has reviewed the request yet, the message should not imply that a personal assessment has already taken place.

Internal notifications should go to the person who needs to act. Sending every update to everyone creates another inbox to sort through. It helps to distinguish an ordinary status change from a situation that requires someone to intervene.

Plan for interruptions

What happens if the email service rejects a message? If the assigned person is away? If sending has started but the system never receives a clear result?

These questions belong in the first version. Show which step completed and which needs checking. Repeatedly retrying an uncertain send can produce several copies of the same email.

The operating instructions should explain how to continue the enquiry manually. That makes the automation part of everyday work. A colleague needs to understand the next action, without having to understand the software behind it. Someone should also be able to see what has already been sent before taking over.

Start with one route through the process

For the first version, I would choose one common type of enquiry. I would follow it from arrival to an approved response, then use it in practice to identify where people still have to search, copy information or ask again.

The success criteria should follow that route. Is responsibility visible? Does less information need to be entered twice? Can someone check what went out? A specific claim about time saved should come after measuring the actual process.

The SSP building process follows the same approach: clarify the need, define a small first version, put it into use and hand it over. Handling enquiries can be that first piece.

If your work gets stuck after the quote request arrives, describe where enquiries come in, who handles them and which step always depends on someone remembering it. That gives us a place to start.