Users with the appropriate Lead access can create prospects directly in AIUNIFY CRM.
You can begin from the Leads workspace or use the Lead Quick Action when that shortcut is available to your account.
Before creating a Lead, search the existing Leads and, when appropriate, Customers and Contacts for the same person or company.
This is particularly important when you already know the prospect's email address or company name.
Duplicate Leads can divide notes, activities, assignments, proposals, attachments, and follow-up history between multiple records.
The Lead record supports prospect identity information such as the Lead name and other person/company details presented by the form.
Use the fields according to their labels rather than placing all prospect information into the description field.
Confirmed Lead data includes information such as:
Enter only information you have reasonably verified. Accurate Lead contact information becomes especially important when the Lead is later converted to a Customer.
The Lead record can store:
Complete the applicable information when it is relevant to your organization's prospecting process.
Use the Lead Description for useful prospect context that does not belong in a dedicated structured field.
A good description can help another authorized user quickly understand the opportunity without replacing the formal activity, note, or task history.
The Lead record supports an existing Source value.
Select the source that accurately represents where the Lead originated when an applicable source is available in the CRM.
This manual covers selecting an existing source, not configuring the organization's Lead Source catalog.
Choose the appropriate existing Lead Status for the prospect's current position in the business process.
Status should represent the Lead's actual state. Do not advance the Lead simply to make the pipeline appear more complete.
The Lead record supports assignment to a responsible staff user.
When your workflow allows assignment, choose the person who is expected to manage or follow up with that Lead.
Assignments can also influence which Leads users are permitted to access.
Lead workflows support Tags where available.
Use existing Tags consistently to add useful classification without replacing the Lead's Source, Status, or assigned owner.
The Leads workflow contains validation for fields that are expected to be unique.
If AIUNIFY CRM reports that a value is already in use, investigate the existing Lead instead of changing the value merely to force creation of another record.
When you have permission to edit a Lead, open the existing record and update only the information that has actually changed.
Use status/activity workflows for process changes rather than overwriting permanent identity fields with temporary comments.