Back to all articlesFollow-up operations

Decide Whether a Follow-Up Has Enough New Value to Send

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A follow-up task becomes due, so someone opens the prospect record and writes another version of “checking whether you have had a chance to review.” The task gets completed, but the prospect receives the same decision burden as before.

A sales follow-up is worth sending when it fulfils a relevant promise, answers an unresolved question, or enables a specific next decision. It does not always need new information. A requested reminder can be useful because it arrives at an agreed moment. But an internal reminder becoming due is not, by itself, a useful contribution to the recipient.

Before sending, finish this sentence: “This message helps the prospect ___ by providing ___.” If the second blank contains only “another reminder,” check whether the prospect actually requested one. If not, defer the message until you can establish a clearer purpose.

1. Separate the review trigger from the reason to contact

A scheduled task tells staff when to examine a conversation. It does not establish what the next message should do. Keeping those functions separate prevents a calendar from becoming the main reason for contacting someone.

At review time, look at the last meaningful exchange, not just the last outbound message. Find what the prospect asked, what the sender promised, and what is preventing the next decision. A sequence of unanswered outbound messages is not evidence that another one is useful.

Use three questions:

  • What is owed? Identify any promised answer, document, introduction or agreed reminder.
  • What is unresolved? Name the prospect’s question or uncertainty, using their stated concern rather than a guessed objection.
  • What can move forward now? Identify a decision that the recipient can reasonably make with the information available.

If all three answers are blank, the appropriate result may be “defer: no useful contribution identified.” That is a completed review, not an unfinished sending task. Record the reason so another staff member does not simply restart the same contact pattern.

2. Test for one of three useful contributions

Fulfil a relevant promise

If you promised to provide something, delivering it has a clear purpose. Check that the promised item still fits the conversation and that it is actually ready. A message saying the answer is still being investigated can also be appropriate when the prospect is expecting an update, but it should explain what remains unresolved and what happens next.

A missed commitment is not repaired by replacing the deliverable with a request for a meeting. Either provide what was promised or acknowledge the gap accurately.

Answer an unresolved question

A useful answer reduces uncertainty. It might establish whether a requirement can be met, explain a constraint, or distinguish what is confirmed from what still needs checking.

A related attachment is not necessarily an answer. If the prospect asked about a specific operational requirement, sending a general overview leaves them to find the answer themselves—or discover that it is absent. State the answer and its limits before pointing to supporting material.

Enable a specific next decision

A decision-enabling follow-up makes the next choice clearer or easier. It could identify the missing input needed for a proposal or present an option that addresses a previously stated constraint.

Adding “Would you like to book a call?” does not automatically create value. Ask what that call would resolve and why it is the appropriate next step now. The request should follow from the contribution, not substitute for one.

3. Apply a send-or-defer gate, not a points score

A points system can let several weak signals outweigh one decisive problem. Instead, use a short gate with conditions that must all be met.

  1. There is a named contribution. The message fulfils a promise, answers a question or enables a decision.
  2. The contribution is grounded. It comes from the conversation, an agreed milestone or verified information—not an invented need.
  3. The timing is relevant. Something is due, ready or actionable for the recipient, rather than merely overdue in the sender’s task list.
  4. The message is accurate and appropriate to send. Claims are verified, uncertainty is visible, and the recipient’s contact preferences are respected.

If the purpose is sound but the answer is not ready, hold the message for verification. If the purpose itself is missing, defer it. If the recipient has opted out, stop rather than looking for a stronger justification to contact them.

For a deferred message, record a reopening condition. “Review when the requested information is confirmed” is useful. “Try again later” simply moves the same judgment problem to another date.

4. Filled hypothetical send-or-defer worksheet

Fictional worked example: The following worksheet describes a hypothetical supplier’s sales conversations. Every proposed message, timing detail and business situation below is invented for illustration, not an Alactic customer result. Use the entries as a model for reviewing your own queue.

Entry A: An unanswered proposal

  • Conversation evidence: A proposal was sent. The prospect has not replied and did not request a reminder.
  • Proposed message: Ask whether they have reviewed the proposal and want to discuss it.
  • Useful contribution: None identified. The same document and broad request remain in place.
  • Decision: Defer.
  • Revised brief: No outbound brief yet. Check whether the proposal omitted an answer to a stated requirement. If it did, prepare a correction rather than another review request.
  • Reopening condition: A relevant omission is found, new verified information becomes available, or the prospect’s agreed review point arrives.

Entry B: A promised implementation outline

  • Conversation evidence: The sender promised an outline showing the customer inputs needed before implementation. The outline is ready.
  • Proposed message: Ask whether the prospect is ready to move ahead.
  • Useful contribution: The promised outline, not a general readiness question.
  • Decision: Send after checking that the outline matches the discussion.
  • Revised brief: Deliver the outline, distinguish confirmed requirements from assumptions, and ask the prospect to identify who owns the required inputs.
  • Observable outcome: The promised item is delivered; any reply can clarify ownership or expose a missing dependency.

Entry C: A requirement that is still unverified

  • Conversation evidence: The prospect asked whether a particular requirement can be supported. An internal answer has not yet been confirmed.
  • Proposed message: Send a general product overview and suggest a demonstration.
  • Useful contribution: The overview does not resolve the question.
  • Decision: Hold the substantive answer for verification. Send a status update only if one is owed or the prospect is waiting on a stated commitment.
  • Revised brief: If an update is due, acknowledge that the requirement remains unconfirmed, identify the check underway, and avoid implying support. Once verified, answer directly and explain any limitation.
  • Reopening condition: The responsible person confirms the answer, or a promised update becomes due.

Entry D: A requested reminder

  • Conversation evidence: The prospect asked to be contacted after an internal planning meeting. That agreed point has arrived.
  • Proposed message: Send the proposal again with a generic checking-in line.
  • Useful contribution: The requested reminder at a relevant milestone. No new attachment is needed unless something changed.
  • Decision: Send.
  • Revised brief: Refer to the agreed planning milestone and ask whether the discussion established a next step or whether the project remains paused.
  • Observable outcome: The prospect can confirm readiness, explain a continuing dependency or keep the project paused without repeating the whole conversation.

Entry E: An option that addresses a stated constraint

  • Conversation evidence: The prospect could not proceed because they lacked capacity for the proposed scope. A smaller scope has now been verified as feasible.
  • Proposed message: Announce that another option is available and request a call.
  • Useful contribution: A concrete alternative linked to the stated capacity constraint.
  • Decision: Send if the alternative is genuinely relevant and its limitations are clear.
  • Revised brief: Explain what the reduced scope includes, what it excludes and which customer responsibilities remain. Ask whether that trade-off makes further evaluation worthwhile.
  • Observable outcome: The prospect can assess the alternative rather than accepting a meeting just to discover what it is.

Entry F: A message intended only to clear the pipeline

  • Conversation evidence: Several outbound messages have received no response. No commitment, open question or agreed milestone is recorded.
  • Proposed message: Ask for a reply so the sender can close the opportunity.
  • Useful contribution: Primarily internal record maintenance.
  • Decision: Defer the message and update the record internally.
  • Revised brief: None. Do not make the recipient responsible for completing the sender’s administration.
  • Reopening condition: A meaningful conversation signal or relevant new contribution, subject to contact preferences.

5. Handle the cases where “new value” is easy to misuse

A requested reminder does not need a novelty requirement. Entry D is useful because it fulfils an agreement. Requiring a fresh insight in every message would cause staff to miss legitimate commitments or add irrelevant material.

New information is not necessarily relevant information. An updated presentation or changed company detail may be new to the prospect but unrelated to their decision. Connect the information to a stated need; otherwise, it does not pass the purpose test.

A deadline is not useful just because it creates urgency. If a real, verified timing constraint affects the prospect’s options, explain that effect. Do not turn an internal sales target into a recipient-facing deadline.

Silence is not a diagnosis. It does not establish that the prospect is confused, uninterested or waiting for a discount. Keep “no reply” separate from any interpretation. When evidence is thin, defer rather than constructing an objection to answer.

6. Make deferral operationally safe

Deferral fails when it hides an outstanding promise or leaves nobody responsible for obtaining the missing answer. A useful record needs the decision, the reason, the next internal action, an owner and a reopening condition.

For hypothetical Entry C, that could mean: “Hold requirement answer; confirmation missing. Assigned owner to verify with the responsible team. Reassess when confirmed; provide the promised status update if confirmation is still pending.” The internal work continues even though the sales message is held.

If repeated checking-in messages have already been sent, do not automatically send an apology that adds another unnecessary contact. First inspect whether anything is owed. Repair a missed commitment directly when appropriate; otherwise, stop repeating the request and correct the internal workflow.

A useful purpose also does not override channel requirements. For WhatsApp, recipient permission matters and opt-outs must be honoured. Approved templates are used to initiate Platform conversations and outside the customer-service window, which opens or resets with a user message and lasts 24 hours. Template approval does not guarantee delivery. Check the current WhatsApp Business Messaging Policy for precise requirements. Purpose review and channel eligibility are separate checks.

7. Review decisions, not just message volume

A completed-task count cannot distinguish a useful answer from an unnecessary nudge. Review a small sample of proposed messages alongside the conversation evidence and the send-or-defer decision.

Track whether sent messages had a named contribution, whether promised items were actually supplied, and whether deferred items had an owner when internal work remained. Where replies arrive, note whether they clarify a decision, answer a focused question or reveal that the message was irrelevant.

Do not treat fewer messages as automatic success. Deferring every difficult follow-up could conceal missed commitments. Equally, a lack of reply does not prove that a promised document was worthless. Judge purpose and execution separately from the recipient’s response.

8. Use the worksheet on the next review queue

For a hypothetical first exercise, review ten upcoming follow-ups before sending any of them. Record the conversation evidence, proposed contribution, send-or-defer decision and revised brief. Give every held item that needs further work an owner and reopening condition.

Then check two concrete outcomes: whether any repetition-only messages were stopped, and whether every due commitment still has a clear delivery action. If reviewers disagree, return to the prospect’s actual question or agreement rather than debating which wording sounds more persuasive. The goal is a defensible reason to send—not a more polished version of a message with no purpose.

Follow-up operationsSales workflowsProspect communicationCRM practices

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications