Being asked a question does not mean you have to guess. A useful reply can be brief and still help the sender move forward: say plainly that you are not the right person to answer, share a reliable direction if you know one, and make no promises on someone else’s behalf. The key is to separate what you know from what you are assuming. That keeps the email courteous without turning a simple handoff into an unwanted commitment for you, a colleague, or the person who asked.
The useful bits
- State your limit directly instead of guessing or padding the reply.
- Give a next step only when you have a sound basis for it.
- Ask before forwarding or involving someone else, and don’t promise their response.
Name the boundary without overexplaining
Open with a short, neutral sentence that identifies the limit: you do not handle that subject, lack the relevant information, or are not the right person to confirm it. Be specific enough that the sender understands why you cannot give a dependable answer, but do not add a long apology or personal explanation.
Avoid softening the boundary until it becomes unclear. “I’m not able to confirm the delivery date” is more useful than “I’m not totally sure, but maybe…” If you have no reliable basis for an answer, say so rather than offering a guess that may be mistaken for a commitment.
I’m not the right person to confirm the delivery date, and I don’t want to give you an estimate that may be wrong.
Offer a direction only when you can stand behind it
If you know a relevant team, role, document, or process, point the sender there. Keep the direction concrete: identify the type of contact or information they need, rather than saying only “try someone else.” You can also suggest that they check a source you know is current, such as the project owner’s latest update.
Be careful with certainty. If you are not sure who owns the question, say that the route is a possibility, not a confirmed answer. For example, “The account team may be able to help” is appropriately cautious when you have reason to think so but have not verified it. Don’t invent an inbox, policy, or process to make the reply sound more complete.
The account team may be the right place to confirm this. I haven’t checked who is covering the request today, so please verify the contact before relying on that.
Don’t assign another person work without consent
A referral and a commitment are different things. Naming a colleague as a possible contact does not mean that person has agreed to take the question, reply by a certain time, or resolve it. Avoid wording such as “They’ll sort this out” or “I’ve asked them to respond today” unless you have actually made that request and have a sound basis for the promise.
Before forwarding a message or copying someone into a thread, consider whether the context is appropriate to share and whether you have permission or a clear reason to involve them. If you are unsure, ask the original sender whether they would like you to connect them, or give them the colleague’s contact route only if you are authorized to share it.
Make a handoff small and explicit
If you are willing to help with a limited next step, describe exactly what you will do and what remains for the sender. “I can point you to the team’s shared contact address” is a bounded offer. “I’ll make sure this gets handled” is broad and may create an expectation you cannot control.
When a handoff depends on another person, phrase it as a request rather than a result: “Would you like me to ask whether Jordan can take a look?” If the sender agrees, you can make that request, then report back accurately. Do not imply that the colleague has accepted until they confirm.
I can ask whether Jordan is the right contact, but I can’t promise they’ll be available. Would you like me to check?
Keep the reply proportionate to the question
A concise response is often enough: acknowledge the request, state your limit, give a verified direction if available, and close with a clear next step. You do not need to defend why you are not responsible for the topic. If the sender needs a decision urgently, say what you can confirm and what they should verify elsewhere, without inventing a deadline or escalation route.
For a complicated thread, answer the part you can address and mark the rest as outside your knowledge. This prevents a partial answer from being read as approval of every detail. If the question concerns dates, recipients, money, or a commitment, be especially precise about what is confirmed and what is not.
Check that the message leaves no false impression
Before sending, read the reply from the sender’s point of view. Can they tell that you are not answering the substantive question? Is any suggested contact or process something you actually know? Does the wording accidentally promise another person’s time, a response, or an outcome? Remove phrases that imply certainty you do not have.
After sending, confirm that the message went to the intended recipient and that any agreed action is clear. If you offered to ask a colleague, make that request only if the sender agreed and you are comfortable doing so. If the colleague declines or cannot respond, update the sender rather than letting an implied handoff appear complete.
- Boundary stated plainly?
- Direction verified or clearly qualified?
- No unapproved forwarding or promise?
- Next step and its owner clear?
Hi [Name], I’m not the right person to confirm [specific question], so I don’t want to guess. [Team or role] may be able to advise; I haven’t confirmed who is handling it today. You could contact [known route] to check. If you’d prefer, I can ask whether [Colleague] is the right contact, but I can’t promise they’ll be available. Best, [Your name]
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