Skip to article
BITTUMailPOWERED BY BITTU ICLOUD
The Mail BlogEmail etiquette

How to Reply When You Cannot Yet Confirm the Information Asked For

A practical guide to separating confirmed facts from open questions, setting a realistic update time, and avoiding accidental promises in email.

Sunlit desk with a laptop, notebook, blue cup and olive tree.
Original BITTU Mail editorial artwork. Illustrative image.

A request for information can arrive before you have enough evidence to answer it. A rushed reply may sound certain even when you are still checking, or leave the other person unsure when they will hear from you again. The useful middle ground is to state what you know, name what remains unconfirmed, and give a specific time for your next update. That time is a commitment to communicate, not a promise that every question will be resolved. Clear wording helps the reader plan without mistaking a possibility for a decision.

The useful bits

  • Label confirmed facts and unresolved points separately.
  • Give a realistic time for an update, even if the answer may still be pending.
  • Describe tentative outcomes as possibilities, not promises.

Separate the confirmed from the pending

Before replying, split the request into individual questions. For each one, ask: What can I verify now? What am I inferring? What still depends on someone or something else? Answer the first category plainly. Label the other categories rather than blending them into a confident-sounding summary.

Useful phrases include “I can confirm that…” for a checked fact, “I have not yet confirmed…” for an open point, and “My current understanding is…” for information that may change. If a detail came from another person, say that it is their current estimate unless you have independently confirmed it. Avoid making a guess sound official by leaving out its source or uncertainty.

Name the dependency without overexplaining

A brief explanation can make uncertainty understandable: you are waiting for approval, checking a record, or asking the relevant team to verify a detail. State only what the reader needs to understand why the answer is not final. Do not imply that a check has happened if it has not, or suggest that another person has agreed when you are still waiting for a response.

When possible, say what would settle the question. For example, you might be checking the latest delivery status rather than merely “looking into it.” This gives the recipient a clearer picture of the open issue without exposing unnecessary internal discussion.

Promise a time to communicate, not an outcome

Give a date and, when useful, a time and time zone for your next update. Choose a point you can realistically meet, allowing room for the source of information to respond. If you cannot estimate when the answer itself will be available, say so directly. You can still commit to checking back with the recipient at a stated time, even if the status remains unresolved.

This distinction matters: “I will send an update by [date and time]” is a promise about your communication. “The approval will be complete by then” is a promise about an outcome you may not control. Make only the first commitment unless the second has actually been confirmed and you have authority to make it.

Keep tentative answers visibly tentative

Words such as “likely,” “expected,” and “proposed” can help, but only when the sentence also identifies what is uncertain. “The current estimate is [date], pending confirmation from [source]” is clearer than “It should be ready [date].” The second wording can sound like a firm deadline, especially when the reader is making plans around it.

If the recipient needs to act before confirmation arrives, separate the possible scenario from the safe next step. For instance, say that a date is being considered, but advise them not to make a nonrefundable arrangement based on it until you confirm. Do not add caution that is irrelevant to the request; focus on the decision the recipient actually faces.

A reply that keeps the boundary clear

This example answers part of a request while leaving the unresolved point explicit. Replace the bracketed fields with details you have checked, and use a follow-up time you can meet.

EXAMPLE / ADAPT TO YOUR SITUATION
To: [Name] <jordan@example.com>
Subject: Re: [Requested information]

Hi [Name],

I can confirm that [verified fact]. I have not yet confirmed [open question]; I am checking with [relevant person or source]. The current estimate is [tentative detail], but please treat it as unconfirmed for now.

I will send you an update by [date and time, including time zone]. If I do not have a final answer by then, I will let you know what is still pending and when I expect to check again.

Best,
[Your name]

Follow through and check what your message promises

Before sending, read the email from the recipient’s point of view. Can they tell which facts are confirmed, which are open, and when they will hear from you next? Look for accidental certainty in phrases like “we’re all set,” “it will be,” or “I’ll have the answer,” and replace them if they overstate what you know.

Put your promised update time somewhere you will notice it, such as your calendar or task list. When that time arrives, send the update even if the answer has not changed: say what you checked, what remains unresolved, and the next time you will communicate. You can confirm the reply worked by checking that it was sent to the intended recipient and that its wording matches your actual certainty. If the recipient’s response shows they understood a tentative point as final, clarify promptly rather than relying on the earlier wording.

About this guide

Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.

View current plans · Security information · Suggest a correction