CRM and request handling: where clients get lost
The most expensive leak in a business happens not in advertising but after it. The request has arrived, the money for it is already spent — and from there it can simply be lost. This is where improvements cost the least and deliver the most.
The most expensive leak happens after the advertising: the request has arrived, the money is spent, and then it gets lost. The benchmark for response speed is 5–15 minutes in working hours; after an hour the person is already talking to a competitor. Not everyone needs a CRM: up to twenty enquiries a month a spreadsheet filled in with discipline is enough.
In this article8 sections
Why this matters more than optimising advertising
Do the arithmetic: cutting your cost per click by 20% is hard work with an uncertain outcome. Raising the share of requests that reach a deal from 25% to 35% is 40% more clients on the same budget. And usually all it takes is calling back faster.
Response speed is the most underrated factor of all. Someone who leaves a request often leaves it in more than one place: they had three sites open. The one who answers first wins, not the one with the better price.
Where exactly requests get lost
| Point of loss | What it looks like | What to do |
|---|---|---|
| The request never arrived | Broken form, email in spam | Duplicate to a messenger, check weekly |
| It arrived but nobody saw it | An inbox nobody checks | Send notifications where they get read |
| Seen, but answered too late | Called back the next day | A response-time standard |
| Answered, but could not help | Do not know the price, cannot book | A script and access to the schedule |
| Could not reach them and forgot | One call and that was it | A rule of several attempts plus a message |
| No follow-up after «let me think» | The client is forgotten | A reminder in the system |
Standards worth introducing
- Time to first response. A target of 5–15 minutes in working hours. An hour is already a lot.
- Number of call attempts. At least three at different times of day, then a message on a messenger.
- Mandatory recording. Every enquiry logged, even when someone «was just asking».
- Returning to deferred leads. If they said «let me think», a reminder after the agreed interval.
These rules only work if someone checks them. A standard without oversight lasts a week.
When you need a CRM
A CRM is not a compulsory attribute but a solution to a specific problem: there are more enquiries than fit in your head and your messages.
| Situation | What is enough |
|---|---|
| Up to 20 enquiries a month, one person | A spreadsheet and discipline |
| 20–100 enquiries, two or three people | A simple CRM |
| Over 100, or a long sales cycle | A CRM with automation and integrations |
A CRM nobody enters deal outcomes into is useless and even harmful: it creates the illusion of control. An honest spreadsheet that gets filled in beats an expensive system that gets ignored.
What an enquiry record should contain
- Date and time it arrived.
- Source — where the person came from.
- Contact details and the substance of the request.
- Who is handling it.
- Current status and the date of the next step.
- Outcome: a sale with its value, or the reason for the refusal.
The last item is the one skipped most often, and it is precisely what turns request logging into sales analytics. Without outcomes you can calculate neither cost per client nor return by channel.
How to audit your own handling
- Leave a request yourselfFrom a number they do not know, during normal working hours. Time how long the callback takes.
- Repeat outside working hoursSee what happens to a request left in the evening.
- Listen to ten callsThat is usually enough to find the main problem.
- Calculate the funnelHow many enquiries, how many reached a proposal, how many reached payment.
- Find the narrowest transitionThat is where the cheapest growth is sitting.
A script for the first conversation
Not a text to be read out word for word, but a frame that keeps you from forgetting the essentials and losing people for no reason.
- Introduce yourself and name the company — the person left requests in several places.
- Restate the task in your own words, to show you listened.
- Give the price range immediately if asked. Dodging the question reads as an attempt to inflate it.
- Propose a specific next step: a visit time, an estimate, a call-out.
- Confirm what was agreed and repeat it out loud.
- Log everything in the system straight after the call, not in the evening.
The most common failure is the absence of a next step. The call ends with «we will get back to you» and no date, and that is where it ends.
What to automate first
| What | Why | Difficulty |
|---|---|---|
| Requests straight to a messenger | They will not get lost in email | Low |
| An auto-reply to the client | They know the request was received | Low |
| A reminder for the staff member | So the callback is not forgotten | Medium |
| Call recording | To see what actually happens | Medium |
| Requests into the CRM automatically | Nothing gets lost | Medium |
The first two take an hour and close the most galling losses — the ones where the request never reached a human at all.
Frequent questions
How quickly should we answer a request?
The faster the better. A practical target is 5–15 minutes in working hours. After an hour the person is most likely already talking to a competitor.
What about requests at night?
An automatic reply stating when you will call, plus a call first thing in the morning without fail. Silence until lunchtime the next day is a lost request.
Do we need call recording?
Highly advisable. It is the only way to see what happens between a request and a sale. Announcing that the call is recorded is mandatory.
How do we tell the problem is handling rather than marketing?
If you have enough requests, few sales, and the requests are relevant, the problem is downstream of marketing. Verify it by listening to calls and timing responses.
What if the manager does not enter the data?
Make entering it part of the process rather than extra work: the request lands in the system automatically and the manager only marks the outcome. Anything requiring manual duplication stops being filled in within a month.
How many call attempts count as enough?
Three at different times of day plus a message on a messenger. One failed call and crossing the name off is the cheapest way to waste requests you already paid for.
The materials answer general questions. We will look at your specific case — free and without obligation.