Outcome
You can identify each lead source, process inquiries and NDA states, and create the next action on the correct canonical person.
Navigation path
CRM > Leads
Access
Active CREBuilder subscription with CRM entitlement
On this page
Before you start
Data, sources, and access to prepare
- CRM access
- Ownership or permitted scope for the lead contact
Recognize what the inbox contains
| Lead kind | Typical context | Primary decision |
|---|---|---|
| Inquiry | Message from a public listing or related capture | Read, respond, export, or delete the inquiry activity. |
| NDA Signer | Pending, active, or revoked NDA access with qualification answers | Approve, decline, or revoke according to listing policy. |
| Email Lead | Identified email-related engagement | Confirm context and next follow-up. |
| Forwarded | Lead imported from a supported forwarded source | Read the origin banner and verify source details. |
| Manual or New lead | Add Lead activity on a canonical person | Qualify and create the next task or pipeline record. |
Triage one lead completely
- 1
Search the lead queue
CRM > Leads > Search
Enter a term when the queue needs text filtering.
Expected result: Matching permitted lead activity remains.
If this does not happen: Clear the term if it excludes the lead you need.
- 2
Filter by lead type
CRM > Leads > type chips
Select one type chip when the queue needs activity-type filtering.
Expected result: Only the selected permitted lead type remains.
If this does not happen: If the page shows a load warning, select Retry. A failed request is not an empty inbox.
- 3
Expand source context
Lead row or card
Open the activity.
Expected result: The property, message, qualification, forwarding, or access details become visible.
If this does not happen: If the activity cannot open, retry the Leads request.
- 4
Read source context
Expanded lead activity
Review the complete source details.
Expected result: You understand why the lead appeared and which person it belongs to.
If this does not happen: If source data is incomplete, open the canonical contact timeline and related property before responding.
- 5
Confirm the canonical contact
Expanded lead > contact link
Verify identity, company, owner, source, lead type, tags, and existing timeline.
Expected result: The engagement is attached to the correct person and no duplicate is needed.
If this does not happen: If a duplicate exists, use the Contacts merge workflow before adding parallel follow-up.
- 6
Create the next action
Contact workspace or expanded lead controls
Add a note, task, requirement, deal, or appropriate access decision.
Expected result: The person has a dated, owned next step or a recorded terminal decision.
If this does not happen: If an optional save fails, preserve the text and add it from the contact workspace.
Use inquiry and NDA actions precisely
- 1
Review an unread inquiry
Leads > expanded Inquiry
Read the full message and source.
Expected result: The inquiry has been reviewed before its unread state changes.
If this does not happen: Leave it unread when review is incomplete.
- 2
Mark the inquiry read
Leads > expanded Inquiry > Mark read
Select Mark read.
Expected result: Unread status clears without deleting the activity.
If this does not happen: If bulk marking is used, first confirm every selected inquiry is safe to acknowledge.
- 3
Select inquiry rows
Leads > Inquiry selection
Select only the intended rows.
Expected result: The bulk toolbar shows the selected count.
If this does not happen: Clear the selection if any row should not receive the same action.
- 4
Apply one bulk inquiry action
Leads > bulk toolbar
Select Mark, Export, or Delete as offered.
Expected result: The action applies to the selected inquiry activities.
If this does not happen: Export before destructive cleanup when business policy requires a retained record.
- 5
Review NDA qualification
Leads > expanded NDA Signer
Read signer identity, answers, property context, and current pending/active/revoked state.
Expected result: You have the evidence needed for the access decision.
If this does not happen: If identity or answers are insufficient, leave access pending and follow up outside the decision controls.
- 6
Approve, decline, or revoke
Expanded NDA lead > access actions
Approve a qualifying pending request, decline a pending request that should not gain access, or revoke future protected access when needed.
Expected result: The status changes to the selected state and the decision remains visible.
If this does not happen: Do not use revoke as a substitute for controlling material already downloaded. Follow the signed agreement and firm policy.
NDA signed and access approved are separate facts
A signer can complete an NDA while access remains pending when the listing requires approval. Process the access decision explicitly.
Understand first-lead attribution and recovery
One first qualifying lead fact per contact
Today and lead reporting count the first qualifying lead capture, not every repeat event.
Qualifying lead events
Earliest qualifying fact
Repeat engagement
Remains on timeline
New lead count
Counted once
- Qualifying lead eventsEarliest qualifying fact
- Qualifying lead eventsRepeat engagement
- Earliest qualifying factNew lead count
Counting boundaries
- Imports and Add Contact do not create a qualifying new-lead fact.
- Add Lead records one manual lead activity without creating a separate person.
- Repeat inquiries or engagement remain visible but do not double-count the first lead.
- Lead reporting uses the first qualifying fact date.
The inbox looks empty while an error warning is present
Likely cause: One or more source requests failed and the page is showing partial state.
- Select Retry.
- Keep the warning visible in any shared status.
- Do not report zero leads until all requests succeed.
A lead is absent from Today New leads
Likely cause: It may be a repeat event, import, Add Contact, outside the selected scope, or outside the relevant fact window.
- Open the person timeline.
- Identify the earliest qualifying lead fact.
- Check Today scope and date context.
- Do not add another lead marker merely to change reporting.
Final verification
- Leads > Inquiry selection: The bulk toolbar shows the selected count.
- Leads > bulk toolbar: The action applies to the selected inquiry activities.
- Leads > expanded NDA Signer: You have the evidence needed for the access decision.
- Expanded NDA lead > access actions: The status changes to the selected state and the decision remains visible.
- No blocking warning, failed status, or unresolved validation message remains in the completed workflow.