17.1 The Lead Profile as a Follow-Up Record

The Lead Profile stores more than contact information. It provides operational areas for preserving the history and supporting material associated with the prospect.

Use these areas so that Lead follow-up remains connected to the Lead instead of being scattered across private notes and disconnected files.

17.2 Lead Activity

AIUNIFY CRM records Lead activity for a variety of Lead operations.

For example, state changes such as marking a Lead Lost or Junk are logged as Lead activity.

The Lead workflow also contains functionality for adding custom activity when the interface provides that operation.

17.3 Why Activity History Matters

Activity provides context about what has happened to the Lead over time.

Before taking over or following up on an existing Lead, review the available activity history so that you do not repeat work or contradict a prior action.

17.4 Lead Notes

The Lead Profile includes a Notes area.

Use Notes for internal prospect information that should remain available with the Lead record.

Notes are appropriate for context such as:

• Important follow-up details.
• Conversation context.
• Qualification observations.
• Information needed for a future interaction.

Keep notes factual and useful to authorized users who may later review the Lead.

17.5 Lead Attachments

The Lead Profile includes an Attachments area with an upload workflow.

Use Attachments when a file should remain associated with the Lead, such as prospect-supplied material or another relevant working document.

When an attachment is added through the normal Lead workflow, AIUNIFY CRM can also log activity indicating that an attachment was added.

17.6 Downloading All Lead Files

When a Lead has attachments, AIUNIFY CRM provides a Download All function.

The system collects the Lead attachments and downloads them together as:

files.zip

If the Lead has no attachments, there is nothing for the bulk download function to package.

17.7 External File Choosers

The Lead Attachments interface can expose external file-provider controls when those integrations are available in the deployed environment.

Use only providers shown and enabled in your interface. Availability of an integration does not mean every user has the same access to the underlying external account.

17.8 Lead Reminders

The Lead Profile includes a Reminders area.

The Reminder workflow supports information such as:

• Reminder description.
• Reminder date.
• Staff user associated with the reminder.
• Whether the reminder notification has been sent.

17.9 Setting a Lead Reminder

1. Open the correct Lead.
2. Open Reminders.
3. Select the option to set a reminder.
4. Enter a clear reminder description.
5. Select the intended reminder date.
6. Select the appropriate staff user when the workflow allows it.
7. Save the reminder.
8. Confirm it appears in the Lead's reminder list.

17.10 Notes, Reminders, Tasks, and Activities Serve Different Purposes

Note	Stores internal contextual information about the Lead.
Reminder	Prompts follow-up at an intended date.
Task	Represents formal work that may require assignment, status, dates, collaboration, or tracking.
Activity	Provides historical context about actions associated with the Lead.

17.11 Lead Record Best Practices

• Keep prospect context in the Lead record.
• Use Notes for useful narrative information.
• Use Reminders for date-based follow-up.
• Use Tasks when formal work tracking is required.
• Attach files to the correct Lead.
• Review activity before contacting an existing Lead.
• Download important attachments before destructive record cleanup when retention is required.