The study would test whether leads are owned and contacted within the window or sit in a queue.
Question and scope
This is a proposed research protocol, not a report of completed findings. It asks what share of leads reach a named owner and a first contact within the response window. The result would describe the routing control. Record the exception and the person who approved it.
The protocol does not measure whether the lead was qualified. It measures whether the owner and the contact happened on time. Use the same format for every handover so the next reader can scan it. Keep the boundary visible in the place where the work is assigned.
Population and unit of analysis
Define the population as leads received during a stated window. The unit is one lead, with the source, the owner, the assignment time, and the first contact recorded. Write the deadline as a date and a local time. Review the first few notes together before the process expands.
Link the lead to the opportunity so the same lead is not counted twice. A short note with four fields is easier to use than a long narrative. Review the first few notes together before the process expands. Keep the evidence with the record rather than in a separate log.
Definitions and measures
Define assignment as a named owner in the CRM. Define first contact as a logged call or message. Measure both against the window. Record the exception and the person who approved it.
Report the assignment rate and the contact rate separately. A lead can be assigned but never contacted. Name the owner in the same line as the action. Keep the boundary visible in the place where the work is assigned.
Evidence standard
Use the CRM timestamps and the message log. A note that says contacted without a timestamp is weak evidence. Write the deadline as a date and a local time. Separate what was observed from what was assumed.
Record the channel and the outcome. A failed attempt is not the same as a conversation. Test the rule on one real lead before applying it to the queue. Separate what was observed from what was assumed.
Sampling and collection
Use a census of the leads if the volume is manageable. If sampling is necessary, stratify by source and segment. Update the template when the same question appears twice. Record the exception and the person who approved it.
Pilot the classification on a few leads and compare the reviewers. Clarify how a reassignment is treated. A short note with four fields is easier to use than a long narrative. Name the owner in the same line as the action.
Analysis and reporting
Report the assignment and contact rates by source and segment. Show the leads that were never owned. Test the rule on one real lead before applying it to the queue. Update the template when the same question appears twice.
Present the results as a description of the routing control, not a judgment about the rep. Name the rule that should change. A control that depends on memory is not yet a control. Separate what was observed from what was assumed.
Limits and sources of error
The CRM may not capture contacts made outside the system. State the channels included. If the source is unclear, route the question instead of guessing. Keep the evidence with the record rather than in a separate log.
The response window may vary by lead type. Report the window used. Review the first few notes together before the process expands. Name the owner in the same line as the action.
Review cadence
Repeat the review after a routing change or at the same interval each quarter. Compare the same sources and the same window. Keep the original note beside the corrected version. Test the rule on one real lead before applying it to the queue.
Assign the follow-up to the sales manager and set a date. The protocol should produce a specific decision about the routing rule. Ask whether a new reviewer could act on the record without a conversation. Record the date and the source so the next reviewer can repeat the check.
Sources
Apply the operating question
Use the finding to define one source, output, review owner, and exception path inside a real workflow.
Discuss the workflow