Capture the context, not just the email
A useful enquiry includes the business problem, company, required service and timing. Collect only what you need to make the first conversation useful. Explain how the information will be used and keep private notes out of the public website. Record the source alongside the enquiry so you can later connect marketing activity to real outcomes.
Save first, then process
Store the enquiry before asking another service to enrich or analyze it. Give each submission a unique identifier so a retry does not create another lead. The visitor should see a confirmation only after the record is saved. If an email service is unavailable, the enquiry should remain in the CRM with its next action clearly marked.
Create a reviewable next step
Score the information you actually have, and show why. A high score can suggest a consultation; missing information can suggest a clarification. Neither should silently reject someone. Draft a response that mentions their specific problem, and put it in an approval queue. When a reply arrives, stop the unanswered-enquiry sequence.
Close the reporting loop
Use the same lead record for meetings, proposals and the eventual project. Record estimated value separately from money received. This lets you ask which sources generate useful conversations and which produce clients. The Dev Mizan website uses this pattern: enquiries enter its own CRM, receive an explained score, and become drafts ready for review.