Trace one enquiry from start to finish
Submit an approved test enquiry through each important form, not just the homepage. Record when it was submitted, where it appeared and who was notified. A thank you screen proves only that the visitor reached that state; it does not prove a CRM record or email arrived. Check calls and calendar journeys separately because they may use different integrations and owners.
Give every lead a named next action
Define who receives new enquiries, how availability is handled and what happens if routing fails. A pipeline stage should describe a real event such as contacted, estimate sent or appointment booked. Avoid stages that are updated automatically without confirming the underlying action. Staff need a fallback queue and a way to identify an enquiry that was never assigned.
Use consent based follow up
An acknowledgement can confirm receipt and explain the next step, but it should not pretend a staff member has reviewed the request. Agree appropriate contact channels and stop rules. Review consent and local requirements before email or SMS sequences, and honour opt outs. Contact attempts should fit the service and customer expectation; a universal number of messages is not a substitute for a sensible process.
Measure progression, not just speed
Record response time alongside successful contact, qualification, booking and eventual sales outcomes. A fast automated message is not the same as a useful conversation. Review failed delivery, unassigned records and leads that remain in one stage without action. Use the findings to improve ownership or the enquiry journey before paying for more traffic. Never place customer records or sensitive messages into advertising events.