The advert worked. The customer clicked, read the page, and asked for a quote.
Your website said, “Thank you”. Your inbox said nothing. Somewhere, a spreadsheet may have acquired a row.
Who is replying?
If that question starts an investigation, your next conversion project may have very little to do with the advert. Paying for another lead is an odd response to losing track of the first one.
A useful follow-up process gives each enquiry a named owner, a helpful response and a dated next action. You can build the first version with a shared working list. The important part is knowing what should happen when everyone gets busy.
Give every open enquiry an owner and a next action
Imagine a Nairobi printer receiving a request for thirty branded shirts for an event. The customer gives a date, but the artwork needs checking before the team can quote.
A row saying “new lead” does not tell anyone to check the artwork. Use a working record that makes the task visible:
| Field | Example record |
|---|---|
| Enquiry and source | Thirty event shirts; website form. |
| Received | Monday, 10:15 a.m. |
| Owner | Named sales colleague responsible for the enquiry. |
| Status | Clarifying print requirements. |
| Last useful response | Asked for artwork and size breakdown. |
| Next action | Check whether the files arrived and send to production. |
| Due | Agreed working time on Tuesday. |
| Outcome | Open; quotation not yet ready. |
Keep the original message accessible. Do not ask the customer for details already sitting in another inbox.
Choose one primary working list, whether it is a CRM, shared inbox or sheet. Connect duplicate contacts about the same job. If someone follows up on WhatsApp after submitting a form, they have not necessarily become a second sales opportunity.
The owner can ask colleagues for help without surrendering responsibility into the void. Keep ownership until the receiving colleague accepts the handover, and specify who covers absence or overdue work.
For a solo operator, the named owner is you. The dated task is there for the version of you who gets interrupted halfway through the day.
Answer the request instead of announcing your intention to answer
“Thanks for reaching out. We'll be in touch” confirms receipt. It does not answer the question.
An automatic acknowledgement can be useful, especially outside working hours. Measure it separately from the first helpful response.
For our print enquiry, a useful reply could be:
Thanks for sending the quantity and event date. Please share the artwork and size breakdown so we can check the print requirements. We will confirm the price and whether we can meet your deadline before you commit.
That message uses information already supplied and requests what changes the quotation. It does not invent a price or reserve an unverified production slot.
If you can answer now, answer now. If a colleague must check something, explain what is being checked and give an update time the team can meet. Do not promise a ten-minute reply because a marketing article made it sound impressive.
Set your own response commitment by channel, working hours, and enquiry type. A simple availability question and a complex technical quote need different treatment. Define what happens when the commitment is missed.
Make the status describe what has actually happened
“Contacted” can mean a completed conversation to one colleague and an unanswered call to another. Use stages that tell the next person what work remains.
For a small enquiry process, try:
- New: a useful reply is due.
- Clarifying: specific information is missing.
- Preparing quote: the team is checking feasibility and price.
- Quote sent: the customer has the offer.
- Paused: there is a recorded reason and review date.
- Closed: won, declined, unsuitable or deliberately concluded.
These are suggested labels, not a mandatory software configuration.HubSpot's lifecycle guidance distinguishes broader lifecycle stages from detailed lead status. Use that principle to keep the record meaningful without adopting a pipeline your team will not maintain.
Qualification means finding out whether you can help. For the printer, quantity, artwork, deadline, and delivery location matter. A missing budget is a question to resolve, not proof that the person is wasting your time.
Follow up on the decision rather than your inbox
“Just checking in” announces that you have returned. Give the customer a reason to continue.
After sending the shirt quote, agree on a review time where possible. If their committee meets Thursday, that is more useful context than a universal day-three sequence.
Here are sample messages to adapt to the actual conversation:
| Situation | Useful follow-up |
|---|---|
| Artwork is missing | “Is the artwork ready to share? If the design is still being finalised, send the current version and we can explain what needs checking before print.” |
| The quote is under review | “Have you reviewed the shirt quote with your team? If the quantity or print specification has changed, send the update and I'll check the price and timing.” |
| The customer needs more time | “When would it be useful to revisit this? I'll note that date so we don't keep chasing while the plan is still undecided.” |
| The conversation has gone quiet | “Is this order still being considered? If the event plans have changed, let me know, and I'll update the enquiry. We would need to recheck production availability before confirming.” |
Do not send a message about a missing file after the customer has delivered it by another channel. Update the record when something changes.
Use real constraints for urgency. If the production schedule needs checking, say so. Invented scarcity is a poor substitute for knowing your capacity.
Stop scheduled sales follow-ups when the customer replies for a conversation, declines, asks you to stop, or completes the purchase. A pause in a sequence is part of the process working.
Automate the reminder before you automate the conversation
Start with rules you can explain:
| Trigger | Action | Evidence it worked |
|---|---|---|
| Successful enquiry received | Save it, assign an owner, and create a response task. | Complete record and visible task. |
| Next action becomes due | Remind the owner. | Reminder received by the right person. |
| Task passes its agreed deadline | Alert the backup or responsible manager. | Accepted follow-up responsibility. |
| Customer replies or enquiry closes | Pause or cancel relevant messages. | No stale follow-up goes out. |
If replies arrive through channels the system cannot reliably observe, create a human review task before sending the next message. An internal reminder can save work without pretending to understand the whole conversation.
A Sheets and Apps Script setup can support a modest process, but someone must maintain it. Google's quota documentation explains that exceeding limits can stop execution. Its installable-trigger guidance describes execution records and failure notifications, with exceptions for add-on-created triggers. Agree who watches failures and checks the business result.
Use a CRM when shared history, permissions, channel handling or volume outgrow what your list can support. The purchase should solve an observed limitation, rather than give the same missing tasks a more expensive home.
Bring Attention Lasso a few stalled enquiries and the channels they arrived through. We can help define the handovers and choose what to automate first.
Audit the last ten enquiries
Review ten recent genuine enquiries, including open ones. Ten is an initial working sample, not a benchmark. For each, find the received time, owner, first useful response, next action, and current outcome.
Then calculate what you can actually establish. For example, if four of ten open records lack a dated next action, 40% of that small reviewed group is relying on someone's memory. That’s illustrative, not a finding about your business or the industry.
Fix missing ownership and overdue actions first. Then investigate whether delays cluster around a channel, task, or handover. A slow production check may need a different fix from a form that fails to arrive.
Keep automatic receipts out of your useful-response measure. Follow a defined group of enquiries through to outcomes; this week's sales divided by this week's enquiries may combine entirely different customers.
Finally, submit marked internal tests. Try an out-of-hours enquiry, a returning contact and a closed request. Verify the record, task and stop conditions. The system should work when the conversation ends as well as when it begins.
Frequently asked questions
How quickly should I reply to a lead?
Reply as soon as you can provide useful help, within a commitment your team can reliably meet. Define working hours and urgent cases. An instant receipt is reassuring, but it should not hide a slow answer to the customer's actual request.
How many times should I follow up?
Use a bounded plan based on the enquiry, buying timeline, and customer preferences. Agree a review date when possible and make each message useful. Stop when they decline or ask you to stop, and reassess whenever they reply.
Can I manage leads in Google Sheets?
Yes, if the team can keep ownership, status, and dated tasks accurate. Check reminders and access, rather than relying on the sheet as passive storage. Move to a different setup when shared conversations or volume make that process unreliable.
What is the difference between acknowledgement and response?
An acknowledgement confirms receipt. A useful response answers the request or explains the specific next step. Track them separately so a fast automatic message does not make unanswered enquiries look handled.
Which follow-ups should I automate first?
Start with capture, assignment and internal reminders. Add customer messages only when the system can recognise replies, changes, and closed enquiries. Otherwise, a reminder to a person is more useful than sending the wrong customer message automatically.
How do I tell poor leads from poor follow-up?
Assess service fit separately from handling. Check whether the business could fulfil the request, then inspect reply times, quote delivery and next actions. A relevant enquiry left waiting shouldn’t be filed as poor quality because it never became a sale.
Keep the next promise visible
Pick one open enquiry. If its owner cannot name the next action and when it is due, fix that before buying more traffic.
Share the point where enquiries stall with Attention Lasso. We can help turn it into a process your team can operate and check.
Keep pulling the thread
