An enquiry arrives through the website. Someone forwards it to sales. A conversation happens, a proposal is sent and then the opportunity disappears into an inbox.
Nobody has deliberately ignored it. The business simply has no dependable way to see who owns the next step or whether it happened.
This is where CRM and automation can make a practical difference. Not by replacing sales judgement, but by making the customer journey easier to manage consistently.
Before investing in more acquisition, look at the opportunities already entering the business. A better handover and a clearer follow-up process may deserve attention before another campaign does.
Map the journey before configuring the software
Start with what happens today. List the ways enquiries arrive, how they are assessed, who responds and what normally happens before a customer commits.
Turn perspective into progress
Ready to make
the next move?
Bring the challenge to Seven52. We will help identify the clearest route forward.
Include the less tidy routes. Someone may phone after reading an article, reply to an old email or contact a team member directly. If the process only accounts for website forms, important opportunities will remain outside it.
Then identify where information is lost or action depends on memory. Are enquiries duplicated? Do proposals go out without a follow-up date? Does an absent salesperson leave everyone else unsure what was discussed?
Those gaps form the brief. Choosing software first can result in a sophisticated system that reproduces the same unclear process with more fields to complete.
Define stages by evidence, not optimism
A useful pipeline shows where an opportunity genuinely stands. Each stage should represent a meaningful change, with a clear condition for entering and leaving it.
“Enquiry received”, “qualified”, “discovery completed”, “proposal sent” and “decision pending” may suit one business. Another may need samples, a site visit or technical approval. Use stages that reflect the actual buying process rather than importing somebody else's funnel.
Avoid stages that merely describe a feeling. “Looks promising” does not tell a colleague what happened or what should happen next. Equally, sending a proposal is not evidence that the customer has reviewed or accepted it.
Agree what closes an opportunity and how you record the reason. A poor-fit enquiry, a lost competitive bid and a deferred project reveal different things about the business.
Give every live opportunity an owner and next action
The most valuable CRM field may be the one showing what happens next. A contact record without an owner, action and date is still easy to neglect.
Define who is responsible at each stage and what happens during leave, absence or reassignment. Make the handover explicit when another person needs to contribute, rather than assuming a notification transfers responsibility.
Record enough context for the next conversation to be useful. That includes the requirement, relevant constraints, previous discussions and commitments already made. Avoid collecting information simply because a field is available.
For a hypothetical property agency, a viewing request should not become an isolated phone number. The person responding needs to know which property prompted the enquiry and what the customer has already asked. Context makes follow-up feel like a continuation, not a restart.
Automate the dependable parts of the process
Automation is well suited to clear, repeatable actions. It can acknowledge receipt, route an enquiry, create a task or remind an owner that an agreed follow-up is due.
Begin with rules the team can explain. If an enquiry concerns a particular service, assign it to the appropriate team. If a proposal is sent, create a review task for an agreed date. If essential information is missing, flag it rather than allowing the record to progress unnoticed.
An acknowledgement should set accurate expectations. Confirm that the enquiry has arrived and explain the next step without pretending that a person has already reviewed it.
Also define when automation stops. A reply, booked appointment, completed purchase or request not to be contacted may need to remove someone from a sequence. Without exit conditions, useful follow-up can become an awkward series of messages that ignores the conversation.
Keep human judgement at decision points
Not every delay should trigger another email. A customer may be waiting for internal approval, revising scope or dealing with a concern that needs a proper conversation.
Give the team room to adjust the next step and record why. Automation should support their understanding, not force every prospect through an identical timetable.
This matters particularly for higher-value work. A construction project may depend on site information. A professional services engagement may require specialist assessment before anyone can confirm suitability. Those decisions should not be reduced to a score based only on form answers.
Use suggested priorities as prompts for review rather than unquestionable verdicts. A system can make information visible, but the business remains responsible for how it interprets and acts on that information.
Connect the systems and test the exceptions
An integration is only useful if the right information reaches the right place reliably. Decide which system owns the record and which details need to move between the website, CRM, booking tool or sales platform.
Test more than a successful submission. What happens when a person enquires twice, changes an email address or books after speaking to sales? What happens if the receiving system is temporarily unavailable?
Agree how failures are detected, who investigates them and how records are recovered without duplication. Check access permissions and applicable data-handling requirements before transferring customer information.
Avoid creating an automation nobody understands. Keep a simple description of its trigger, action, exclusions and owner. When a team member or tool changes, that documentation helps prevent a routine adjustment from breaking the journey.
Measure progression and make the system easier to use
Review response times, unassigned enquiries, overdue actions and movement between stages. Then look at accepted opportunities, completed sales and the reasons prospects do not progress.
Compare like with like. Different services and buying cycles can produce different patterns. Recent enquiries need time to mature before their eventual value can be assessed.
Listen to the people using the CRM. If they maintain a separate spreadsheet because the system makes daily work harder, find out why. Simplify unnecessary fields, improve training and resolve duplicated effort. Adoption is part of implementation, not an optional extra after launch.
At Seven52, we connect websites, marketing and CRM around the journey from interest to customer. If your business generates enquiries but follow-up feels inconsistent, book a discovery call. We will help identify where ownership, information or timing breaks down, then shape a process your team can use with confidence.
