Leads: Qualify a New Request Without Guessing
Question: How should a team handle a new request so it receives a clear next step without treating unknown information as fact?
A lead begins with what is known
A new inquiry can be incomplete. Record the request factually and keep unknown details visible. Do not assume identity, service eligibility, schedule availability, price, location, urgency, or customer intent simply because a message or call exists.
The lead-intake sequence
- Check existing records. Look for an existing lead or customer before creating a new active record.
- Capture the minimum needed. Record the requested service and a permitted contact method only when they are appropriate for the next step.
- Separate facts from requests. “Requested a morning visit” is different from “visit is confirmed.”
- Identify missing details. State what a teammate needs to verify next.
- Assign an owner. Every active lead needs a person or team role responsible for the next action.
- Choose a next action. Create a task, a follow-up, or a review; do not rely on an open-ended note.
- Review the visible record. Confirm it does not expose unnecessary private information.
Qualify without overpromising
| What you know | Safe action |
|---|---|
| The person asks for service but details are incomplete | Create a review task and request the minimum missing information. |
| The request may match an existing customer | Verify the record before creating a duplicate. |
| The person requests a particular time | Record the request; confirm availability separately. |
| The work could require approval or specialist review | Route it to the responsible human owner. |
| The request is not ready to act on | Leave a factual note and a dated follow-up. |
Keep data minimal
Do not put credentials, access codes, payment details, sensitive personal information, internal URLs, full message exports, or unrelated screenshots into a lead note. If a file cannot be safely redacted or cropped, do not attach it to a public or shared workflow.
For call outcomes, see Calls: Capture the Next Step Without Overpromising. For duplicate prevention, see Duplicate Records.
Boundaries
This guide supports a minimal-data qualification process. It does not prove identity, consent, service availability, quote accuracy, booking, customer communication, eligibility, payment, or conversion. Verify those facts in the approved record and process.