Task and Activity Best Practices

How Sales should log calls, follow-ups, next steps, and lead activity quality in this project

Tasks are expanded in this Salesforce app. They are not just reminders. Lead Tasks drive Lead Performance reporting, conversion readiness, manager review, ownership handoff quality, and follow-up discipline.

Use Salesforce Tasks for customer-critical activity instead of keeping follow-up only in email, notes, Slack, or memory.

Task Flow

Which Action to Use

Need	Use	Why
Finished a call	`Log a Call`	Captures call outcome, buying context, product interest, risk, compliance, and next step.
Need to do something later	`Follow Up`	Creates an open follow-up Task with due date, owner, product context, and next step.
General lead/customer work	`New Task`	Captures structured task type and activity context.
Meeting-style calendar work	Event	Use only when the calendar event is the source of truth. Still log meaningful next steps.

Core Rule

A Task should answer:

Question	Field area
What happened?	Subject, Task Type, Call Type, Call Disposition, Call Summary.
Who did we reach?	Lead/Contact, Contact Role.
What are they interested in?	Product Group, Product Interest, Discussed Item, Use Case.
How serious is the buyer?	Lead Interest Level, Buying Stage, Primary Buying Signal, Decision Timeframe.
What is blocking the deal?	Objection, Current Supplier, Risk / Red Flags, Compliance Notes.
What happens next?	Next Step, Follow-up Required, Follow-up Due Date, owner, due date.

Required Patterns

For Lead work, enforced users should expect validation when required activity data is missing.

Task situation	Required behavior
Open Lead follow-up	Set `Task Type = Follow-up`, due date today or later, Product Group, and a concrete Next Step.
Completed Lead Task that is not a call	Set Task Type, Product Group, and a concrete Next Step.
Completed Lead call	Set `Task Type = Call`, Call Type, Call Disposition, Contact Role, Lead Interest Level, Product Group, Call Summary, and Next Step.
Connected, Qualified, Follow-up Needed, or Converted call	Add buyer intelligence: buyer type, stage, timeframe, buying signal, decision criteria, use case, license status, product interest, pain/need, supplier, objection, and red flags.
Follow-up required on a call	Set Follow-up Due Date today or later.
License status needs review	Add meaningful Compliance Notes.

Good Examples

Weak entry	Better entry
`Called customer`	`Call Type = Discovery`, `Disposition = Connected`, summary explains buyer need, product group, current supplier, objection, and next step.
`Follow up later`	`Task Type = Follow-up`, due date, owner, product group, and Next Step such as `Send updated quote for Mango Freeze case pricing by Friday`.
`Interested`	Buying Stage, Lead Interest Level, Primary Buying Signal, Decision Timeframe, Product Interest, and Estimated Monthly Order Value.
`Needs license`	License Status plus Compliance Notes explaining what proof is missing and who owns the next step.

Quality Status

The app maintains Lead Activity Quality Status on the Task.

Status	Meaning
`Complete`	Required structure is present.
`Incomplete`	The activity is missing required fields or meaningful detail.
`Follow-up Scheduled`	A completed call required follow-up and a future/current due date was captured.
`Follow-up Missing`	A completed call says follow-up is required but does not have a valid follow-up due date.
`Open Follow-up`	The Task is an open structured follow-up.

Lead Summary Fields

Task saves update Lead-level summary fields:

Lead field	What it means
`Last Sales Touch Date`	Most recent completed structured sales activity.
`Last Sales Touch By`	User who owned the latest structured sales touch.
`Last Sales Touch Disposition`	Outcome from the latest structured touch.
`Last Sales Touch Quality`	Quality status from the latest structured touch.
`Next Follow-up Date`	Earliest open structured follow-up due date.
`Open Follow-up Task Count`	Count of open structured follow-up Tasks.
`Lead Activity Compliance Status`	Whether the lead has recent complete activity and future follow-up discipline.

Best Practices

Put the customer-facing next action in Next Step; do not bury it in a paragraph.
Use Product Group even when the exact SKU is not known yet.
Use Discussed Item when the conversation names a specific catalog item.
Use Call Disposition for the outcome, not for the rep's opinion.
Use Lead Interest Level and Buying Stage together; one is enthusiasm, the other is process maturity.
Create follow-up Tasks instead of promising yourself you will remember.
Close the old follow-up Task when the action is complete, then create the next one if more work remains.
Keep Compliance Notes concrete when license status is not clean.
Avoid vague values like Other or Unknown unless the conversation genuinely did not provide the detail.
Do not bypass required fields just to convert a lead. The conversion gate exists to keep pipeline quality real.

Manager Review

Managers should use Lead Performance reports and Task list views to find:

Review surface	What it catches
Lead Calls Missing Intelligence	Completed calls with weak buyer/product detail.
Lead Connected Calls Without Next Step	Connected calls that do not tell the team what happens next.
Lead Open Follow-up Tasks by Rep	Open follow-up load and ownership.
Leads Without Future Follow-up	Leads that are open but have no future structured follow-up.
Lead Activity Quality by Rep	Rep-level completeness and activity quality.

Do Not Do This

Avoid	Why
Logging only a subject like `call`.	Reports cannot tell what happened or what to do next.
Marking a call complete without a next step.	Handoff, conversion, and manager review become unreliable.
Using old due dates on open follow-up Tasks.	Lead compliance becomes overdue and dashboards lose trust.
Putting compliance risk only in notes outside Salesforce.	Future quoting, shipping, and restricted-product review can miss the risk.
Creating duplicate Tasks for the same follow-up.	Open follow-up counts become noisy.

On this page