16.1 Managing the State of a Lead

Lead management is more than editing contact information. AIUNIFY CRM tracks the prospect's operational state through Status, assignment, Tags, and special Lost and Junk states.

Use these controls consistently so that the Lead workspace reflects the actual condition of the prospect.

16.2 Updating Lead Status

A normal active Lead is associated with one of the existing Lead statuses available in your tenant.

Update the Status when the prospect genuinely moves to another stage in your process.

Kanban columns are based on these statuses, so status changes also affect where active Leads appear in the Kanban workflow.

16.3 Updating Lead Assignment

AIUNIFY CRM supports assigning a Lead to a staff user.

Update the assignment when responsibility for the Lead changes. This keeps ownership and visibility aligned with the person expected to perform follow-up.

16.4 Using Lead Tags

Tags provide an additional way to classify Leads.

Tags do not replace Status or Source. Use them for useful additional categories that your organization already uses consistently.

16.5 Marking a Lead as Lost

AIUNIFY CRM provides a Lost state for Leads that were active prospects but are no longer expected to proceed at the present time.

When a Lead is marked Lost, the system:

  • Stores the Lead's previous Status.
  • Sets the Lost state.
  • Records the status-change time.
  • Logs Lead activity for the change.

Mark a Lead Lost only when that classification accurately reflects the outcome.

16.6 Restoring a Lost Lead

A Lost Lead can be unmarked as Lost.

When the Lost state is removed, the CRM restores the Lead to its previously stored Status.

This means you should use the supplied Lost/restore workflow instead of manually trying to reconstruct the Lead's previous status.

16.7 Marking a Lead as Junk

The Junk state is intended for Lead records that should not remain part of the normal active prospect workflow.

When a Lead is marked Junk, AIUNIFY CRM stores the previous Status, applies the Junk state, records the change time, and logs the Lead activity.

16.8 Restoring a Junk Lead

A Lead can also be unmarked as Junk.

When restored, AIUNIFY CRM uses the stored previous status to return the Lead to its earlier active workflow state.

16.9 Lost and Junk Are Different

Use the classifications according to their business meaning:

Lost A legitimate prospect that did not proceed or is no longer expected to close at the present time.
Junk A record that should not be treated as a valid active prospect.

Do not mark a legitimate but unsuccessful Lead as Junk merely to remove it from active view.

16.10 Bulk Lead Changes

The Leads workspace contains bulk-action functionality for selected records.

Supported bulk data includes areas such as Status, Source, assignment, visibility, Tags, last-contact information, and Lost state. Mass deletion is separately permission-controlled.

Because a bulk update can change many Lead records at once, verify every selected Lead and every chosen replacement value before confirming.

16.11 Verify After a State Change

After changing a Lead's Status, assignment, Lost state, or Junk state:

  1. Reopen or refresh the Lead.
  2. Confirm the intended state.
  3. Review the Lead activity where applicable.
  4. Confirm the Lead appears in the appropriate active, Lost, Junk, or Kanban context.

16.12 Lead-State Best Practices

  • Use Status for normal pipeline progression.
  • Use Lost for legitimate prospects that did not proceed.
  • Use Junk for unsuitable prospect records.
  • Use the restore action if a Lost or Junk Lead becomes active again.
  • Keep the assigned user current.
  • Use Tags as supporting classification, not as a replacement for Status.
  • Review selections carefully before a bulk operation.
Write Your Comment