The weekend inquiry
A request arrives Saturday evening and waits in an inbox until someone happens to open it. The person may already have talked to someone else.

Inquiries arrive by web form, email and phone, and each needs a quick first reply, an owner and a plan for what comes next. We can build the capture, routing and follow-up to support that.
Who it is for
Owners and front-desk or sales staff who receive requests through several channels and rely on memory or a shared inbox to decide who replies.
The problem
A lead is someone who has asked about your work and has not bought yet. The weak point is often the stretch between the first message and the quote, when nobody is sure who is replying and nothing prompts a check-in.
Inquiries rarely arrive through one door. A web form feeds a shared inbox, customers email staff directly and phone messages wait on a voicemail one person checks. Nothing shows what is still waiting.
Lead capture closes that gap with one record for every inquiry, a rule for who owns it, an immediate reply and follow-up that continues until the person says yes, says no or is closed out on purpose.
Situations
You may recognize one or more of these.
A request arrives Saturday evening and waits in an inbox until someone happens to open it. The person may already have talked to someone else.
Two people answer the same email while a voicemail goes unreturned, because nobody was assigned.
A custom furniture maker sends an estimate and waits. With no reminder to follow up, a warm lead cools off on its own.
Referrals, search, social media and a directory all bring inquiries, but nothing records which.
Before and after
The same inquiry, handled by habit and handled by a system. The right column is one possible setup; a project includes only what it needs.
Handled by habit
Lands in whichever inbox, form or voicemail the person used.
Handled by a system
Every channel feeds one list, with the source recorded.
Handled by habit
Whoever sees it replies, when they have time.
Handled by a system
An acknowledgment goes out right away, and a person is asked for a real answer by a deadline you set.
Handled by habit
Everyone assumes someone has it.
Handled by a system
A rule assigns it to one person, who is reminded if it sits untouched.
Handled by habit
Follow-up depends on memory.
Handled by a system
Scheduled reminders keep the follow-up going until there is an answer or someone closes the lead.
Handled by habit
Results are known by gut feeling.
Handled by a system
A pipeline view shows what is new, waiting and won, and which sources bring customers.
What we can build
A project may use only a few of these, starting where inquiries get lost most often.
Web forms, a shared email address and a quick form for logging calls all feed one list.
A message confirms the request arrived and what happens next, without pretending someone has read it.
Rules route each inquiry by service, area or workload and nudge the owner when it waits too long.
Stages such as new, contacted, quoted, won and closed, on a board that shows what needs action today.
Planned reminders and message templates for each stage, which stop when the person replies.
Where each inquiry came from and how it ended, so you see which channels produce customers, not just messages.
Is it worth it?
Honest answers usually settle whether a project is justified.
If one sale is worth far more than a follow-up call, even a small improvement matters. If sales are small and frequent, keep it light.
If you can name the spot, you can fix it. If not, record inquiries for a while first.
Software can assign an inquiry and send reminders, but it cannot supply the person.
Many CRMs and email programs include pipelines and reminders. Switching on a setting may be enough.
Estimate who goes unanswered and what they would have been worth. If it is very little, a lighter fix may do.
With few inquiries and one person seeing them all, a shared inbox, a spreadsheet and a standing reminder are probably the better answer. A system earns its place when forgetting one inquiry is a real loss.
Questions
Straight answers to what people usually ask before a project starts.
Tell us about your business and what you want to change. We will answer directly, and tell you if something simpler would do.
Or write to us at hello@samasadigital.com
Lead capture is the process of collecting every inquiry, giving it an owner and following up. A CRM is one tool that can hold that process, and often the right project is configuring the one you already have.
No. An automatic reply should confirm that the message arrived and say what happens next, but it should not pass for a personal answer. A person writes the real reply.
Phone calls and walk-ins are not captured automatically. Whoever takes a call or meets a visitor logs it with a short form. Recording calls needs a separate telephony tool, which may be possible to connect, depending on the tool you already use.
Tell us how inquiries reach you and what happens next. A few settings in your current tools may be enough, or a purpose-built flow may be worth the effort. We can help you weigh the two.
Complimentary preview
Send us your existing website or business information. We'll create a complimentary homepage concept so you can see what's possible before deciding to work with us.
No commitment. No template.
What to send