Process Teardown, Part 1: The New Inquiry, from "Contact Us" to a First Answer

Imagine a shop with a lovely window, a fresh coat of paint and a customer who walks in at 10:03 on a Tuesday. The shop is full of people. Nobody looks up. The customer waits, says "hello?" to the air and leaves. At 10:41 someone notices the door chime and says to the empty room: "Did anyone come in?"

That shop is closer to your website than you would like. The window is the home page, the door is the contact form, and the empty room is an inbox that nobody checks until Thursday.

This is the first part of a series called Process teardown. Each week I take one common business process apart, step by step, and show where it leaks and how to fix it. We start where every customer relationship starts: the new inquiry.

Why I call this operations and not marketing

Let me be clear about who is talking. I am an operations specialist, not a marketing or sales guru. I do not know a secret way to make strangers click your ad, and I would not trust anyone who claimed one. What I know is how work moves, where it waits and what it costs to let it wait.

An inquiry is exactly that. It arrives, it waits in a queue, a person picks it up and it either moves to a next step or dies quietly. Nobody calls that "operations," but it has everything an operations process has: an input, steps, handoffs, waiting, rework and an output. That is the central idea of Project Focus: leads, operations and sales are not three separate worlds. They are one flow, and the part where the flow breaks is almost always in the handoffs, as I described in Project Focus, Part 2.

So when I say "improve your lead handling," I mean "treat the inquiry as a process and manage the queue." If you already read process improvement: map, measure, fix, this is that method applied to a real, very common case.

The process in one line

Write the process as "from X to Y":

From: a stranger presses "send" on your contact form, calls, or writes a message. To: that person has received a useful first answer and knows the next step.

Everything between those two moments is the process. The end is not "a sale." It is a first answer and a next step, because that is the part you control.

The map of a typical inquiry

When I map this with a small business, the picture on the wall usually looks like this. Count the steps, the handoffs and, above all, the waits.

1. The person fills in the form, or sends an email or a message.
2. The form sends an email to a shared address (info@ something).
3. The email sits in the inbox. Wait: hours or days.
4. Someone notices it, often by chance, and reads it.
5. They forward it to the person who knows the answer. Handoff, then wait.
6. That person has a question and replies to the sender with a list of questions the form already asked.
7. The sender, who has also contacted two competitors, does not reply. Wait, then silence.
8. Eventually someone remembers, a week later, and sends a "just following up" message.
9. A conversation happens, or the inquiry is forgotten.

Nine steps, at least two handoffs, three waits and a loop that asks for information the customer already gave. Nobody designed this. It is the sum of everyone's good intentions.

Where it leaks

Here are the six leaks I see most often, from the most common to the most surprising.

1. Nobody owns the inbox

If three people can see the inbox, each one assumes the other two will answer. This is the bystander effect with a keyboard. The fix is a name, not a tool: one person is on duty for inquiries today, and another is the backup. See the idea of a single accountable person in the RACI chart guide.

2. The form asks too much, or too little

A form with fifteen fields loses people. A form with one field ("your message") produces replies that begin with a list of questions. The trick is to ask only what you need to give a useful first answer, usually name, a way to reach them, what they need and when. Everything else can be asked in the first conversation.

3. The auto-reply says nothing

"Thanks for your message, we will be in touch" is the sound of a door that closed. A better auto-reply tells the person three things: that you received it, what will happen next and when. "We read every message and answer within one business day" is useful, and it creates a promise you must keep, which is the point.

4. The first answer asks questions the form already asked

The customer already told you. Asking again signals that nobody read it. Use the form's information in your reply, even if only to confirm it back in one line.

5. No follow-up

Many inquiries do not reply to the first answer, not because they lost interest but because they got busy. A single, polite follow-up two or three days later is often the difference between a conversation and silence. Without a process, nobody sends it because nobody remembers.

6. After hours and weekends

If your inquiries arrive at night and your answers leave at nine in the morning two days later, the customer has already spoken to someone else. You do not need to work nights. You need an auto-reply that sets the expectation, and a rule about what happens first on Monday.

Speed matters, and I will not oversell it

On the question of speed, a widely cited study in the Harvard Business Review looked at how quickly companies responded to web inquiries and found that the businesses that replied fast were far more likely to reach a real conversation with the lead. I summarized it, with the link to the source, in AI for sales: follow-up that never forgets. It was a study of larger companies, it is more than a decade old, and your business is not theirs. Treat it as a reason to measure your own speed, not as a promise.

The three numbers (and a fourth)

You cannot improve what you cannot see, and you do not need a dashboard to see this. Three numbers on a piece of paper will do. Define each in one sentence, and keep the definition constant, as in Project Focus, Part 3.

1. Time to first answer. From the moment the inquiry arrives to the moment a person sends a useful reply. Use the median of the last 20 inquiries, in hours, because one very late answer can distort an average. Say whether you count business hours or calendar hours, and stick to it.
2. Answered within one business day. The share of inquiries that got a first answer by the end of the next business day. This is the number the customer feels.
3. Reached a next step. The share of inquiries that ended in a call, a quote request or a visit. Not a sale, just a step forward.
4. The queue. How many inquiries are waiting for a first answer right now. A queue of seven is a conversation. A queue of forty is a mystery.

Collect them by hand for two weeks. A shared spreadsheet with four columns (when it arrived, when it was answered, who answered, what happened) is enough. If that sounds boring, good. Boring is how you find the leak.

The teardown, with illustrative numbers

The numbers below are invented to show the method. They are not from a client.

A small dental-supply distributor gets about 40 web inquiries a month. The owner maps the process and follows the last 20 inquiries. The median time to first answer is 31 hours. Only 9 of the 20 (45 percent) were answered within one business day. The queue on the day of the review: 6 messages, the oldest nine days old.

Looking at the map, the owner finds three things. The form sends to an address three people can see. The first reply is almost always a list of questions that the form already asked. And there is no follow-up at all.

The owner changes only four things, in this order:

1. Names an owner and a backup for each week, written on the wall next to the monitor.
2. Cuts the form from ten fields to five and moves the rest to the first call.
3. Writes two templates: an auto-reply that promises an answer within one business day, and a first reply that confirms what the person asked and proposes two times for a 15-minute call.
4. Adds a follow-up three days later, as a calendar reminder for the owner of the week.

She measures again for two weeks. The median time to first answer falls from 31 hours to 6, and the share answered within a business day rises from 45 to about 90 percent. The invented numbers are not the point. The point is that none of the four changes needed software or a larger team. They needed a map, a name and a promise.

The fix ladder for inquiries

As in any process, fix in this order and stop when it works.

1. Eliminate. Remove fields from the form. Remove the "info@" mailbox that three people watch. Remove approval steps that add a day.
2. Simplify. One owner on duty, one backup, one place where inquiries live.
3. Standardize. Two templates: the auto-reply and the first reply. Write them once, in your voice, and improve them every month.
4. Reorder. Answer first, qualify second. A short human reply today beats a perfect one on Friday.
5. Automate. Only now. Routing the inquiry to the person on duty, a reminder if no one has replied in four business hours, a follow-up reminder after three days. See business process automation: twelve examples that pay back and seven workflows on autopilot.
6. Consider an AI helper. A tool that drafts the first reply from the form, for a person to check and send, saves time. A tool that answers alone, in a field where a wrong answer is costly, deserves caution. The AI agents for sales guide explains where the line sits.

The AI helper comes last for the same reason automation does. If the process is confused, a faster machine makes it confused faster.

Capacity: the question behind the queue

Sometimes the queue is long not because the process is broken but because there are more inquiries than people. That is a good problem and a real one. Before hiring, check the bottleneck: is it the answering, the qualifying or the quoting? The capacity planning guide shows how, and a simple kanban board with columns for "new," "answered" and "next step" makes the queue visible to everyone.

The hall of fame of inquiry mistakes

• The black hole. The form says "thank you" and nothing else, ever.
• The reply-all avalanche. Four people answer the same inquiry in four ways.
• The interrogation. The first reply is eleven questions long.
• The proud auto-reply. Three paragraphs about the company, no mention of when the person will hear back.
• The Friday promise. "We will answer within 24 hours" on a form that is read on Mondays.
• The one hero. One person answers everything, then takes a vacation.

I have never met a business that was careless on purpose. They were busy, and busy people leave doors open.

Try the first-answer kit

The tool below builds the three small texts that fix most of these leaks: the auto-reply, the first reply and the follow-up. Fill in your business, the promise you can really keep, and the questions you need. The tool warns you if the promise has no time in it, or if there is no next step. The sample is invented. Nothing you type leaves your browser.

Interactive tool

The first-answer kit

Loading the tool…

What to do this week

Open your own contact form and fill it in as a stranger. Time how long it takes to get an answer. Then do four things: write down the owner and the backup, cut one field, write the auto-reply with a real promise, and count the inquiries sitting unanswered today. That count is your starting number.

Next week, in part 2, we tear down the quote: from "can you send me a price?" to a signed yes. If you want help mapping your own lead-to-cash flow, look at my services, the free templates and the two-minute diagnostic, or tell me about your business.

What is the longest an inquiry has ever waited in your inbox before someone answered it? Tell me in the comments. I will not tell anyone. Probably.

General information, not legal, financial or tax advice. Examples are illustrative and the numbers are invented. If you send marketing email or messages, follow the rules that apply to you, such as the CAN-SPAM Act in the United States.

Frequently asked questions

What is a good response time for a new inquiry?

There is no universal number, and I would not trust anyone who gives one without a source. Measure your own median time to first answer and the share answered within one business day, then set a promise you can keep. A reply the same business day is a reasonable target for many small businesses.

Is handling inquiries a marketing task or an operations task?

Both, but the leaks are usually operational: no owner, a shared inbox, a slow first reply and no follow-up. Treating the inquiry as a process with an input, steps, handoffs and a queue lets you fix it without being a marketing expert.

What should an auto-reply say?

Three things: that you received the message, what will happen next and when the person will hear from you. The time you promise must be one you can keep, because a promise that you miss is worse than none.

Should I use AI to answer inquiries?

A tool that drafts the first reply for a person to check and send can save time. Letting a tool answer alone is riskier where a wrong answer costs money or trust. Fix the process first, because automation makes a confused process faster, not better.

Join the conversation

Did this help? A quick reaction tells me what to write next.

Useful Made me smile Go deeper on this

Be the first to react.

Comments

Loading comments…

Leave a comment

Name (optional) What is the longest an inquiry has ever waited in your inbox before someone answered it? Post comment

No email and no sign-up. Every comment is reviewed before it appears. Please keep it respectful and leave links out.