Agree what each stage means
Agree on a few definitions the team can apply consistently. Interest might mean opening a product inquiry. Received means the request was saved. Qualified means someone reviewed it against the service's fit criteria. Keep proposals and customer outcomes as later stages.
Do not let a software default define the business process accidentally. A button labeled conversion can include several behaviors. Write down the trigger and the evidence behind each number before using it in a performance discussion.
Count receipt when receipt is confirmed
A website inquiry event should correspond to the system confirming receipt, not only to a click on Send. Failed validation and repeated clicks should not look like separate successful inquiries. Test the implementation with a recognizable internal example.
Google Analytics offers a recommended generate_lead event for submitted information. That standard name can help organize reporting, but it does not validate your form or establish that an inquiry is qualified. Keep customer names, email addresses and message content in the business record, outside analytics event parameters.
Read the numbers with the inquiries
Read the inquiries alongside their products and sources. What did those people need, and did the website give them enough information? If a campaign attracts requests the business cannot serve, review its message and audience.
Keep qualification in the system where the team manages the relationship. If website reporting and the CRM are not connected, compare the records through a documented review instead of presenting a fabricated automatic funnel. Unknown source values should remain visible.
Where the data has gaps
Not every visit is recorded, and a person may return through a different device or channel. Campaign labels provide context rather than a complete explanation of a sale. Search reports, analytics and inquiry counts can differ because they measure different activity.
Small samples also need care. One additional inquiry can make a percentage look dramatic. Review the actual records and comparable time periods before deciding that a change caused an improvement. Note seasonal demand and simultaneous campaign changes.
Choose a change and review its effect
Choose a specific intervention based on the pattern. If visitors ask the same basic question, clarify the product page. If the form fails on a phone, fix the interaction. If good inquiries wait unassigned, improve ownership before buying more traffic.
Record the change and the date for a follow-up review. Separate internal test entries from business conclusions. The review should end with an assigned action and enough evidence to judge its effect.
- Interest is not receipt.
- Receipt is not qualification.
- Qualification is not a completed sale.
- A recorded event needs an accurate trigger and a practical use.
