Task Subject Field & Task Details Customization

Overview

The default Salesforce task subject dropdown is too limited for teams with varied, detailed workflows. The recommended approach is to keep the subject dropdown concise with a curated list of general categories, and supplement it with an optional free-text Task Details field on the task object for additional context and instructions.

This pattern was identified and agreed upon during a Salesforce workflow review with ^[1].

Problem

The default task subject dropdown in Salesforce offers a limited set of options that don't reflect the actual work being tracked. For a team like Quarra Stone's sales operation — which needs to assign tasks like developing estimates, releasing sample tickets, or routing work to drafters — the out-of-box options are insufficient.

Expanding the dropdown indefinitely is also not the solution: a bloated subject list becomes hard to scan and defeats the purpose of a structured field.

Solution

Two complementary changes address this:

Replace or augment the default subject options with a short, role-appropriate list of general task categories. Known candidates include:

Develop Estimate (confirmed)
(Additional options to be provided by the client — see ^[1] action items)

The goal is a concise list of high-level task types that cover the majority of use cases without becoming exhaustive.

2. Optional "Task Details" Text Field

Add a new optional free-text field called Task Details to the task object. This field:

Allows the task creator to provide specific instructions, context, or sub-steps
Keeps the subject dropdown short and scannable
Is not required — users fill it in only when additional detail is needed

Example usage:
- Subject: Develop Estimate
- Task Details: Release sample ticket per instructions to the drafter; coordinate with design team on material spec

Implementation Notes

The "Task Details" field should be added to the task object layout so it appears alongside the existing subject, due date, and assignee fields
The field should be optional (not required for save)
Subject dropdown options should be finalized by the client before implementation to avoid rework

This customization was discussed alongside the broader Salesforce workflow clarification for Quarra Stone: ^[2]
The Outlook-to-Salesforce email logging integration was discussed in the same session: ^[3]

Action Items (from originating meeting)

[ ] Lincoln Durham to draft and send desired task subject list to Karly
[ ] Karly Oykhman to add curated subjects to the dropdown and add the optional "Task Details" text field to the task object

Client Context

First identified during the 2025-10-31 Salesforce workflow call with ^[1]. Lincoln Durham noted the need while discussing plans to have the sales team manage all activity — emails, tasks, and follow-ups — directly through Salesforce leads and opportunities.