Design a customer or sales lead follow-up tracker

Author: AILesson8 min setupTested with:ChatGPTReviewed: 2026-08-28

Quick answer

Track consent, ownership, last interaction, agreed next step, due date, and closure without manufacturing urgency or commitments. Provide: Follow-up workflow and boundaries, Fields, systems, and examples, Status, reminder, and privacy rules. Expected result: A reviewable follow-up workbook with state rules, queues, formulas, and privacy controls.

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

Follow-up workflow and boundariesFields, systems, and examplesStatus, reminder, and privacy rules

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Design an Excel follow-up tracker for the stated customer or sales workflow.

Types, stages, outreach authority, consent, owners, handoffs, timing, closure, and supported decisions:
[workflow]

Grain, IDs, customer data, source, consent, stage, value, interactions, next step, dates, owner, outcome, refresh, and samples:
[data]

States, required fields, overdue, time zone, staleness, suppression, duplicates, access, retention, and reports:
[rules]

Use one stable record per lead/opportunity/customer case at the stated grain and keep interaction history in a separate append-only table if multiple contacts occur. Distinguish observed interaction, customer request, seller proposal, agreed next step, and internal task. Never infer consent, buying intent, authority, value, deadline, or commitment from silence, email opens, or stage labels. A follow-up can be due only when an approved cadence or explicit next step supplies the date. Suppression, closed status, missing owner, and privacy restrictions must outrank ordinary overdue reminders. Return: workbook architecture; data dictionary; state transition rules; required-field matrix; formulas for NextActionStatus and data quality; owner queues; validation lists; conditional formatting; duplicate and handoff workflow; privacy/access/retention controls; dashboard counts with denominators; sample rows; and tests for new, due, overdue, waiting, suppressed, closed, missing consent, missing owner, duplicate, and conflicting dates.

Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Follow-up workflow and boundaries: B2B inbound demo requests and existing opportunities. One row per OpportunityID, not per contact. Email follow-up only when ConsentStatus is Allowed or an existing-business rule is documented; Suppressed means no outreach. Stages New, Discovery, Evaluation, WaitingCustomer, Won, Lost. Owner accepts handoff explicitly. Standard cadence: New leads first response in one business day; after that, only an agreed next date or owner-created internal review date. The tracker supports daily owner queues and manager workload review, not automatic emails or lead scoring.
Fields, systems, and examples: Opportunities fields OpportunityID, AccountName, ContactName, WorkEmail, Source, ConsentStatus, ConsentEvidence, Stage, EstimatedValue, Currency, Owner, OwnerAcceptedAt, LastInteractionAt, LastInteractionType, LastInteractionEvidence, AgreedNextStep, NextActionDate, NextActionType, WaitingOn, SuppressedAt, ClosedAt, OutcomeReason, UpdatedAt. Interactions table contains InteractionID, OpportunityID, At, Direction, Channel, Summary, EvidenceLocator, RecordedBy. Example O-104: inbound form, Allowed with form record F-88, New, owner Mei accepted 28 Aug, no interaction, created 28 Aug 15:00 Shanghai. O-107: Evaluation, last call 27 Aug, customer said they would review security document and reply after internal meeting but gave no date; owner Leo. O-109: Suppressed on 26 Aug after opt-out, old follow-up date 29 Aug remains.
Status, reminder, and privacy rules: Review date 31 Aug 2026 Asia/Shanghai. Business-day calendar in Holidays table. Required New: consent evidence, owner acceptance, created time. Evaluation: last interaction evidence; NextActionDate only if agreed or explicitly internal. WaitingCustomer does not invent a date. Suppressed and Won/Lost never overdue. Missing owner is Data issue. Duplicate WorkEmail does not automatically mean duplicate opportunity; duplicate OpportunityID is invalid. Limit workbook access to sales operations; retain per policy not supplied, so mark pending.

Example output

Workbook: Opportunities current state, Interactions append-only history, ValidationLists, BusinessCalendar, OwnerQueue, DataIssues, Dashboard, and ChangeLog. Keep EstimatedValue/Currency optional and never derive probability from Stage.

Status precedence: duplicate ID or required-field conflict → Data issue; Suppressed → Do not contact regardless of old dates; Won/Lost → Closed; missing/ unaccepted Owner → Handoff required; New with no interaction → calculate first-response due by WORKDAY.INTL from CreatedAt under the approved business-calendar convention; WaitingCustomer with no date → Waiting, no overdue; explicit internal or agreed NextActionDate before review date → Overdue; equal to review date → Due today; future → Scheduled; no valid next basis → Needs plan, not overdue. O-109 is Do not contact and its stale date should be cleared only with a logged change. O-107 is Waiting/Needs internal review; the customer's “after our meeting” is not a calendar commitment. O-104's exact due requires the approved rule for time-of-day and weekend cutoff; do not silently reduce a timestamp to a date.

Required-field matrix: every open record needs stable ID, source, consent status/evidence, owner/acceptance, stage, and UpdatedAt. Evaluation needs interaction locator. A customer-agreed NextActionDate requires evidence in Interactions; an internal date needs NextActionType Internal and owner. Conditional formatting follows status text, with suppression highest priority and no color-only meaning. Dashboard shows eligible open denominator, due/overdue by owner, waiting, handoff required, data issues, suppressed, and closures; never calculate “conversion” without cohort and time-window definitions. Access is restricted as stated; retention remains an explicit unresolved policy, so the workbook cannot claim compliance until an owner and period are supplied. Tests cover every precedence branch, date at boundary, old date on suppressed/closed record, missing consent evidence, duplicate ID, and two opportunities sharing an email.

Why this works

1
Separating interactions from agreed next steps prevents a conversation from being recorded as a customer commitment.
2
Precedence rules ensure consent and suppression controls cannot be overridden by an overdue color.

Check the result

Are consent, suppression, source, owner, stage, last interaction, agreed next step, and next date evidenced rather than inferred?
Do suppression, closed state, missing authority, privacy, and missing owner outrank due/overdue reminders?
Can every dashboard count reconcile to mutually exclusive record states and visible denominators?

Use it with confidence

Frequently asked questions

Practical answers about when to use this recipe, what to provide, and where human review still matters

What should I prepare before using “Design a customer or sales lead follow-up tracker”?

For “Design a customer or sales lead follow-up tracker,” prepare Follow-up workflow and boundaries, Fields, systems, and examples, and Status, reminder, and privacy rules. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Design a customer or sales lead follow-up tracker” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A reviewable follow-up workbook with state rules, queues, formulas, and privacy controls—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Design a customer or sales lead follow-up tracker”?

The published test record for “Design a customer or sales lead follow-up tracker” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

More ways to explore