Handle Follow-Up Promises That Depend on Someone Else
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
You told a prospect you would answer their question this afternoon. The internal specialist has not replied, and the deadline is approaching. Sending another internal reminder may help obtain the answer, but it does not preserve the commitment you made to the prospect.
The practical response is to separate two promises: the answer you hope to provide and the update you can personally deliver. Set an internal checkpoint before the external deadline. At that checkpoint, decide whether you have a usable answer, a partial answer or no confirmed answer. Then communicate the actual state before the prospect has to chase you.
If you already promised a complete answer, an update does not retroactively fulfil that promise. It is a repair: acknowledge the gap, explain what remains unresolved and make a smaller commitment you can keep. The worksheet below makes that distinction explicit.
1. Identify exactly what you promised
Start with the message the prospect received, not your memory of the conversation. A vague internal task such as “get clarification” can hide a very specific external promise.
Record the requested information, the promised delivery time and what the prospect intends to do with the answer. Their intended use matters. A preliminary explanation might help them prepare questions, but it may be unsuitable for a decision that depends on confirmed capability.
Classify the existing commitment:
- Answer commitment: You said you would provide the requested information by a stated time.
- Update commitment: You said you would report progress by a stated time, whether or not the answer was ready.
- Ambiguous commitment: You used wording such as “I’ll come back to you tomorrow,” without making the expected content clear.
For an ambiguous commitment, consider what the prospect reasonably expected from the surrounding conversation. Do not reinterpret it as a status update simply because the answer is now late.
Also define what counts as complete. A reply from a specialist is not necessarily a usable answer. It may omit a condition, address a different scenario or offer an unverified impression. The dependency is resolved only when the information answers the prospect’s actual question with any necessary limitations attached.
2. Separate the answer target from the update commitment
An answer target describes the outcome you are working toward. An update commitment describes an action you control. Both can exist, but they should not be presented as equally certain.
For future commitments, make the difference explicit: aim to obtain the answer by a particular time, and promise to report back by that time even if confirmation is still pending. This gives the prospect a dependable communication point without pretending you control the specialist’s work.
For an existing answer promise, avoid silently replacing it with an update promise. Say that the answer remains unconfirmed and acknowledge that this falls short of what you committed to provide.
A useful external update contains four elements:
- What is confirmed, if anything.
- What remains unconfirmed.
- What that means for the prospect’s immediate decision.
- When you will next communicate, without implying that the answer will necessarily be ready.
The trade-off is straightforward: an honest update may expose uncertainty that a confident promise concealed. But it also lets the prospect distinguish usable information from an assumption. Do not transfer uncertainty to them disguised as a likely answer.
3. Put an internal checkpoint before the external deadline
The internal checkpoint is a decision point, not merely a reminder to chase someone. It must leave enough time to review any response and prepare the external message.
Work backward from the prospect’s deadline. Allow time to check whether the answer covers their scenario, clarify any ambiguity and write a useful update. A complex question needs more review space than a simple factual confirmation. There is no universal buffer that fits both.
At the checkpoint, choose one of three paths:
- Complete and confirmed: Prepare the answer, including relevant conditions.
- Partly confirmed: Separate the confirmed portion from the unresolved portion. Decide whether the partial answer is useful on its own.
- Still unconfirmed: Use the fallback brief to send an honest status update before the external deadline.
Do not let an internal estimate erase this checkpoint. A specialist expecting to reply soon is a reason to keep watching for the answer, not a reason to remain silent past the prospect’s deadline.
If the answer arrives after you send an update, review it before forwarding it. Speed does not remove the need to check that it addresses the original question.
4. Use a filled dependency worksheet
Fictional worked example: The people, situation, times and messages in this worksheet and the examples that follow are hypothetical. They illustrate a recommended operating practice, not a customer result or a claim about a particular product.
Suppose a salesperson, Maya, is helping a prospect assess whether a reporting workflow can distinguish records belonging to separate business units. Maya has promised a confirmed answer on Tuesday. An internal specialist, Jordan, still needs to check the exact scenario.
Filled hypothetical dependency worksheet
- Prospect and owner: Prospect contact Alex; salesperson Maya owns the external follow-up.
- Requested information: Can the proposed reporting workflow produce separate business-unit totals when a record is associated with more than one unit? If so, what conditions affect the result?
- Prospect’s intended use: Alex wants to decide whether to include this workflow in an internal evaluation discussion on Wednesday morning.
- Existing external promise: Maya said she would provide a confirmed answer by Tuesday at 4 p.m., using Alex’s agreed local time.
- Internal dependency: Jordan must confirm how the overlapping-record scenario is handled. Maya does not have enough evidence to answer independently.
- Definition of a usable answer: Explicit confirmation of whether the scenario is supported, the treatment of overlapping records and any conditions relevant to the requested totals.
- Current confirmed information: The requested scenario has been documented and sent to Jordan. No capability answer is confirmed yet.
- Internal checkpoint: Tuesday at 2 p.m. Maya checks for a usable response and identifies anything still missing.
- External update commitment: Maya will send Alex either the confirmed answer or an explicit delay update no later than Tuesday at 4 p.m. If the answer is unavailable, she will acknowledge that she missed the original answer commitment.
- Fallback message brief: State that the overlapping-record behaviour is still unconfirmed. Acknowledge the promised answer is not ready. Explain that Alex should treat this item as unresolved in Wednesday’s evaluation. Commit to another status update by Wednesday at 9 a.m., whether or not confirmation has arrived.
- Next internal action: At the checkpoint, ask Jordan specifically whether the treatment of overlapping records can be confirmed. Do not repeat a broad request for general reporting information.
- Closure condition: Alex receives the confirmed answer and its relevant conditions, with a clear statement of which earlier uncertainty it resolves.
The worksheet keeps the unknown narrow. Maya is not waiting for unspecified information; she is waiting for confirmation of a particular behaviour. That makes both the internal request and the external update more useful.
Keep this record wherever you reliably manage the prospect commitment. A note and a reminder may be sufficient. The important feature is that the unresolved question, checkpoint and external deadline remain visible together.
5. Write a fallback that informs rather than stalls
In the hypothetical example, the fallback could read:
I committed to confirming this by 4 p.m. today, but I don’t yet have a verified answer on how records associated with multiple business units affect the totals. I’m sorry I haven’t met that commitment.
For tomorrow’s evaluation discussion, please treat that behaviour as unresolved rather than confirmed. I’ll send another status update by 9 a.m. tomorrow, whether or not the answer is available.
This message does not provide an invented completion estimate. It also avoids making the prospect interpret an internal status report. The useful information is what remains unknown and how to treat it.
Compare that with a weaker hypothetical message:
Still waiting on our specialist. It should be fine, and I’m hoping to have something soon.
This combines blame, unsupported reassurance and an undefined next contact. It may sound friendly, but it gives the prospect little they can use.
You do not need to name the specialist or describe internal workload. Own the external commitment without claiming control over the answer. Keep explanations short unless the reason for the delay materially changes the prospect’s choices.
6. Handle partial answers and uncertain completion times
A partial answer is useful only when its boundaries are clear. In the hypothetical reporting example, confirmation that separate totals exist would not resolve how overlapping records are counted.
If you share that partial answer, separate the two points explicitly: the general reporting behaviour is confirmed, but the overlapping-record scenario is not. Do not lead with a broad positive statement that the prospect could mistake for confirmation of the whole requirement.
Withhold a partial answer when the unresolved condition could reverse its practical meaning. A short delay update is better than information that requires a later correction.
Completion estimates need similar care. Distinguish among:
- A specialist’s estimate: An expectation that may change.
- Your answer target: The time you are working toward.
- Your next update commitment: The time you will communicate regardless of progress.
If there is no credible completion estimate, say so. Then commit only to the next update. Do not replace the missed deadline with a second unsupported answer deadline just to make the conversation feel resolved.
Choose update frequency around the prospect’s decision needs. Repeated messages with no new information can become noise. A useful next contact may be tied to their next decision point, provided they know what to expect in the meantime.
7. Recover when the deadline has already passed
If you discover the missed commitment after the deadline, send the repair message promptly. Waiting for the complete answer can extend the silence and leave the prospect unsure whether the request is still active.
A recovery message should acknowledge the missed deadline, state the current information status and establish the next communication point. It should not require the prospect to comfort you or investigate your internal process.
For the hypothetical example, if Maya notices the miss on Wednesday morning, she could write:
I missed the answer deadline I gave you yesterday, and I should have updated you before it passed. The overlapping-record behaviour is still unconfirmed. I recognise that leaves the question open for your evaluation discussion. I’ll update you again by noon today, even if confirmation is still pending.
If delays repeat, reassess the usefulness of the proposed next step with the prospect. Ask whether they want to continue with the item marked unresolved or revisit it when confirmation is available. Do not imply that they should proceed on an assumption.
When the answer finally arrives, close the original question explicitly. Connect the answer to the requirement, include relevant conditions and distinguish it from any preliminary information previously shared.
8. Test the practice on your next open commitment
Choose one live prospect promise that depends on an internal answer. Before making another follow-up request, fill in the worksheet’s essential fields: exact question, usable-answer criteria, existing promise, internal checkpoint, external update deadline and fallback brief.
Then check the observable outcome:
- Was the internal checkpoint completed before the external deadline?
- Did the prospect receive an answer or an explicit status update by the committed time?
- If the answer was late, was that recorded as a missed answer commitment rather than a completed one?
- Did the message distinguish confirmed information from unresolved information?
- Was the next communication time kept?
Track answer timeliness separately from update timeliness. Otherwise, a timely holding message can conceal a pattern of promising answers too early.
Your immediate next action is small: select one outstanding dependency and schedule its checkpoint now. Prepare the fallback before the deadline becomes urgent. That will not make the specialist’s answer arrive sooner, but it gives you a practical way to keep the prospect informed without inventing certainty.
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