Lead Follow-Up Template: 7 Fields Before Automation

A Lead Follow-Up Template should make ownership, the next action, and the due time visible before it automates anything. Copy the seven-field table below into a spreadsheet, use synthetic or approved non-sensitive information, and test one inquiry path manually. Add software only after a missed follow-up can be explained from the row itself.

The decision before the tool

This template was reviewed on 2026-07-30 under a narrow condition: one synthetic inquiry moves through one spreadsheet, no customer record is used, and no message is sent. The scope is operational visibility, not CRM selection and not a sales-performance test.

The practical decision is simple. If a row cannot tell a person who owns the inquiry, what should happen next, and when it becomes overdue, automation will only move an unclear process faster. A reliable first version is a shared row with a named owner and an explicit exception note.

Use the template for a small team that currently follows up from memory, inbox flags, or scattered notes. Do not use it as evidence that a particular cadence, script, or tool will improve conversion. No conversion, response-time, or revenue result was measured for this article.

Evidence boundary: demand signal, not demand volume

Google’s public autocomplete endpoint was checked on 2026-07-30 for the exact query “lead follow up template.” It returned four visible suggestions in that response.

The public autocomplete response is a reproducible source for the observed suggestions. It is not a keyword-volume report. The article therefore answers the visible template intent without making traffic or sales claims.

Copy the 7-field lead follow-up template

Use one row per inquiry. Keep free-form notes short enough that another person can scan the row without opening a separate document.

The table is intentionally tool-neutral. A spreadsheet is enough to expose missing ownership and ambiguous actions. If the team later moves to a CRM, these fields become a migration checklist rather than a reason to redesign the process around a vendor.

For a synthetic test, create an inquiry with no personal details. Assign an owner, write the next action, set the due time, and then simulate a duplicate or missing-consent condition. A reviewer should be able to explain the normal path and the stopped path using only the row.

Manual operating rule

Review active rows in a consistent order: overdue items first, then items due next, then items waiting on a named condition. The owner either completes the next action, changes it with a reason, or records an exception. Closing a row requires a status that explains why no further action is expected.

Keep automation outside the test. Do not send an email, create a customer record, enrich contact data, or change account permissions from this sheet. The first useful artifact is a readable queue and a short audit trail, not a connected stack.

Use this handoff note when responsibility changes:

Lead identifier:
Current status:
Previous owner:
New owner:
Next action:
Due time:
Reason for handoff:
Exception or consent note:

The handoff note does not replace the row. It makes the ownership change explicit and gives the new owner enough context to reject an unsafe or incomplete next action.

Failure modes and limits

A tidy sheet can still hide a broken process. Watch for these failure modes:

• The owner field names a department, so nobody is accountable.
• The next action says “follow up” without describing the actual decision or message.
• The due time exists, but no person is responsible for reviewing overdue rows.
• Duplicate inquiries receive separate outreach because the identifier is inconsistent.
• The exception note becomes a dumping ground for personal information.
• A closed status hides an unresolved consent, policy, or customer-service issue.

Do not place credentials, payment details, confidential records, regulated information, or unnecessary personal information in the template. If the inquiry path requires those inputs, this public template is not the right operating surface. Use an approved system and context-specific review.

The template also does not prescribe a contact cadence. Timing depends on the promise made to the inquirer, the channel, consent, business hours, and applicable rules. Record the due time that your real policy supports; do not borrow an unsupported benchmark from a marketing claim.

Final decision and stop rule

Adopt the template only if another person can read a synthetic row and identify the owner, next action, due time, and reason to stop. If ownership is shared, the next action is vague, or the exception cannot be understood without private context, stop and repair the manual process.

After the manual path is clear, automate only a reversible preparation step, such as flagging an overdue row for human review. Keep sending, deletion, payment, permission changes, and sensitive-data movement behind explicit approval.

Related build logs

• AI Agent Run Log Template: Track Cost, Failures, Evidence, and Approval
• AI Human in the Loop: 5 Stop Gates Before an Agent Acts