Aspire Enhancement Request

Add a Prospect Incident/Log Section, Mirroring the Existing Employee Incident/Log

Submitted: July 8, 2026

Request Type: Enhancement Request

This is submitted as an Enhancement Request. It was confirmed that this change cannot be handled as a Layout Request, since it involves adding new user interface functionality (a new related-record section) rather than rearranging or configuring fields that already exist on the Prospect Contact screen.

Overview

This request asks Aspire to add a new Incident/Log section to Prospect Contacts, built as a direct mirror of the Incident/Log section that already exists on Employee Contacts. Sales representatives and account managers currently have no centralized place to document prospect touchpoints — calls, emails, samples, and follow-ups are tracked informally in spreadsheets or personal email, and this history is lost or fragmented whenever a contact changes hands.

To keep the request straightforward for development and easy to review, the new Prospect section should be a standalone mirror of the Employee Incident/Log — same structure, same behavior — rather than combined with, or synced to, other existing Prospect fields (such as Follow Up or Close Probability). Keeping it separate avoids extra complexity and keeps the ask simple to scope and build.

Current Functionality Reference

The existing Employee Contact screen includes an Incident/Log section that allows users to create individual activity records associated with the contact. Each entry provides a structured way to capture details, history, and follow-up actions (Figure 1). Prospect Contacts currently include related fields such as Follow Up, Follow Up Email, Close Probability, and a Properties grid, but no equivalent interaction log (Figure 2).

(See attachment)

Figure 1 — Employee Incident/Log (existing functionality)

Figure 2 — Current Prospect Contact layout

Requested Enhancement

Add an Incident/Log section to Prospect Contacts that mirrors the existing Employee Incident/Log section — same section behavior, same grid structure, same New/edit/delete pattern — rather than folding it into or syncing it with other existing Prospect fields. This request applies specifically to Prospect Contacts; extending the same section to other Contact types in the future can be considered separately if needed.

Proposed Prospect Incident/Log Section

The new section would allow users to add multiple interaction records tied directly to the Prospect Contact, following the same pattern as the Employee Incident/Log grid shown in Figure 1.

Example Activity Type options (dropdown):

• Call Log
• Email Correspondence
• Follow-Up Activity
• Meeting / Visit
• Sample Sent
• Marketing Material Sent
• Opportunity Update
• General Notes

Suggested Data Captured Per Interaction

Implementation Approach

Rather than creating a separate custom solution, this should be built directly off the existing Employee Incident/Log, by:

• Adding a new Incident/Log section to the Prospect Contact screen, mirroring the existing Employee Incident/Log section as a standalone grid — not merged with or synced to other Prospect fields.
• Reusing the same underlying record structure and grid behavior (add/edit/delete, column layout) already used for Employee Incidents.
• Adding Prospect-specific activity type options within the same dropdown pattern rather than building a separate module.
• Placing the new section on the Prospect Contact screen in a location consistent with other related-record sections, such as Properties.
• Log entries visible to all users with access to the Prospect Contact, with edit/delete rights restricted to the entry's owner (and admins), consistent with how accountability is handled elsewhere in Aspire.

Business Benefit

• A complete history of prospect interactions in one location.
• Improved visibility into sales activity and pipeline progression.
• Consistent documentation of calls, emails, samples, and follow-up actions.
• Better accountability through assigned ownership and reminders.
• Reduced reliance on external tracking tools or spreadsheets.
• A scalable framework that supports both employee and prospect relationship management.

Technical Summary for Development Review

Add a new Incident/Log section to the Prospect Contact screen, built as a standalone mirror of the existing Employee Incident/Log section — same record structure, same grid behavior — rather than combined with or synced to other existing Prospect fields. Add configurable activity type categories for Prospect use cases. This approach reuses proven architecture while keeping the request scoped and simple to implement.