Capture & Assign a Lead
Get a lead into CRM and give it an owner so someone is accountable for pursuing it.
#Purpose
Make sure every lead has a clear owner from the moment it is recorded.
#Business goal
Accountability on every lead — nothing sits unowned.
#At a glance
| Detail | Value |
|---|---|
| Estimated time | 2–5 minutes |
| Departments involved | Sales |
| Business modules used | CRM |
| AI departments used | — |
| Required permissions | Internal staff with CRM access |
| Prerequisites | CRM access. |
#Workflow at a glance
1
Create lead
Manual, import, or form.
2
Assign owner
Set who pursues it.
3
Notify owner
They pick it up.
4
Ready to qualify
In the pipeline.
#Step by step
1
Create the lead
Add it manually, by import, or from a website form submission.
2
Assign an owner
Set the salesperson responsible.
3
Confirm the owner has it
The lead shows in their view for follow-up.
4
Move to qualification
The lead is ready to qualify.
#Approval points
No formal approval gate
This workflow does not require a sign-off step, but you can still review before acting.
#Expected result
What you should see
A lead exists with a clear owner, ready to be qualified.
#Common mistakes
- Leaving leads unassigned.
- Duplicating leads that already exist.
#Troubleshooting
| If this happens | Try this |
|---|---|
| The owner cannot see the lead | Confirm the assignment saved and the owner has CRM access. |
#FAQ
Can I reassign a lead later?
Yes — change the owner at any time as workloads shift.
#Keep exploring
#Related workflows
#Knowledge base
#Business modules
#AI departments
Still need help?
Can’t find what you’re looking for? The DevSphere OS team is happy to help.
Was this page helpful?