How to Stop Losing Enquiries: First Replies and Useful Follow-Up

A customer asks for a price. You reply, then hear nothing. That silence does not tell you whether they are comparing providers, waiting for information you promised, or no longer interested. For a small service business, the useful question is: who needs to act next, and when?

This guide gives you four places to check, reply examples and a compact enquiry record. You can use them with a spreadsheet and your existing work conversations. For the wider path through delivery and repeat orders, see the small business customer workflow.

Find the point where the enquiry stopped

Review enquiries from one completed working period and look for the last commitment in each conversation. “I will check availability and get back to you” leaves the next action with your business. “We will discuss it and reply on Friday” gives the customer time to decide. Recording both as “did not buy” hides the difference.

Decide who checks each incoming channel and who covers when that person is delivering a service. Set your response target around your opening hours and the type of enquiry. A same-day repair request needs a different rule from a detailed project estimate. A precise promise is useful only if your team can keep it; specify the time zone when the customer is elsewhere.

Make the first reply useful before asking for another action

Use the information the customer has already given, explain what you can offer and identify the next decision. A link helps when it opens the relevant service or product. A generic homepage link leaves the customer to find the answer again.

When the request is specific enough

In this hypothetical example, a customer asks a cleaning business for a regular clean of a two-bedroom apartment next Thursday. The business knows the service scope but still needs to check the schedule:

“For a regular clean, our standard visit covers the kitchen, bathroom, floors and accessible surfaces. I will check Thursday availability and send the quote by 3 pm today, London time. Do you prefer a morning or afternoon visit?”

The location and time are illustrative, not a promised response standard. Replace the scope and timing with your actual conditions, and make the time zone clear. The owner of the enquiry now has a task to send the quote; they should not wait for the customer to restart the conversation.

When you need one more detail

If the message only says “How much is cleaning?”, an exact price may be premature. Give a genuine starting range if your business has one, then explain which details affect the estimate:

“Could you tell me the approximate floor area and whether this is a regular clean or a clean after building work? That will help me work out the scope and price. We can check the date once the scope is clear.”

You do not need a full address or unrelated personal details just to answer that question. If a site visit is necessary for a firm quote, explain it before promising a final price. Clarification should help the customer decide rather than become a form they must complete without knowing why.

Keep a small record of the next action

An enquiry record should make unfinished work visible. Keep an enquiry reference, the work channel or thread link, the request, current state, owner, next action and due time. Use one necessary contact route rather than copying entire conversations or unnecessary personal information into a widely shared sheet.

Here is a hypothetical record you can adapt:

Enquiry: C-014, regular apartment clean. Channel: business email thread. Request: two-bedroom apartment, next Thursday. State: business checking availability. Owner: duty coordinator. Next action: check the schedule and send the scope and quote. Due: today, 3 pm, London time. Outcome: not yet known.

Useful states include “our reply due”, “waiting for customer details”, “offer sent”, “confirmed”, “declined” and “no response after follow-up”. These are suggested rules for your records, not a claim about field names in any software. At a shift handover, the next person must accept the action and deadline, not merely have their name added to a row.

When the customer accepts, record the service scope, agreed price, date and location, and payment arrangements. An acknowledgement that you received the request does not confirm a free appointment slot. If the scope or price changes, get agreement again before marking the job confirmed.

Follow up with a purpose and a stopping point

First check whether your business has done what it promised. If you still owe the quote, the next message should supply it rather than ask the customer to decide. Once the offer is complete, agree when to return to it: “When would it be useful for me to check back?” A time-sensitive booking and a project planned months ahead will need different timing.

If no follow-up time was agreed, choose one reasonable check-in that fits the booking date and the customer's channel. This is a starting policy you can adapt, not a universal sales rule. Refer to the actual enquiry and make it easy to resolve a question or decline:

“I'm checking back on the apartment clean for next Thursday. Do you have any questions about the scope or quote? If you need a different date, I can check it. If your plans have changed, let me know and I'll close this enquiry.”

Stop messages about that offer after a refusal or a request not to be contacted. If there is still no response after your appropriate check-in, record “no response”, the last contact date and that the active follow-up is complete. Do not label it “too expensive” or “chose a competitor” unless the customer said so. Silence is an unknown outcome, not permission to keep sending reminders.

Move channels when the customer chooses to or when it serves a clear purpose. You could offer Telegram as a way to place and view an order, while still answering the original question in email or Instagram. Requiring a new app or bot before giving a basic answer adds a decision the customer did not ask to make.

Where BotMarketing can support this process

BotMarketing's public mini-site and catalog can present the offer, while a company Telegram bot and Mini App can lead to an order or booking request. The business needs to fill in the relevant details, configure its bot and check that customer path. Staff still handle the request and confirm the actual arrangement. Available functions depend on the subscription and staff permissions.

Customer records and order history can preserve context within the service. An enquiry that remains in an external conversation should not be assumed to appear automatically as a Telegram request. You can maintain the small record above manually; it is not a promise of automatic task assignment with deadlines or importing every personal chat.

Automated messages run on a configured schedule, including to predefined audience cohorts. Cohort delivery requires an available private chat with the company's bot. That is different from sending a message exactly one day after any customer question: a cohort does not know every detail of an individual offer. Have the enquiry owner review a personal follow-up before sending it. Loyalty rewards and coupons cannot answer a missing question about price or availability.

For the longer relationship, read about building a customer base as an independent specialist. The immediate goal here is narrower: give each current enquiry a clear state and next action.

Test the process over one working week

1. Choose one common enquiry type. Define a useful first reply, an owner and a backup.
2. Record the next action and due time after each conversation. At the end of a shift, review overdue promises and enquiries without an owner.
3. Count separately the cases waiting for your reply, customer clarification, a decision on a complete offer, or confirmation after acceptance.
4. At the end of the period, separate confirmed jobs, explicit refusals and no response. Leave offers with future decision dates open.

If most enquiries stall while availability is checked, improve that step first. If the scope is unclear, improve the quote. More messages or a faster automated acknowledgement do not prove the process works better. A useful operational result is fewer unkept promises and a visible next action for each active enquiry.