The questions that never got a direct answer
Four things can happen to a question. Only one of them is an answer.
Last updated
Situation archetypes
A question that never got a direct answer is one of the few things in a text thread you can count exactly — the question is there, the reply is there, and whether the second addresses the first is checkable line by line. Not a lie detector. Inconsistency is not proof of deception. A question can go unanswered because it was buried third in a message, because the answer has not been decided yet, or because answering starts a conversation the other person is too tired to have — and those are more common than concealment. What follows is how to separate a question that was dodged from a question that was merely lost, and how to tell when the difference has stopped mattering.
What are the four things that can happen to a question over text?
A question sent over text gets answered, gets partly answered, gets turned back on the asker, or gets nothing — and those four outcomes carry completely different amounts of information.
Answered means a reply came back that would settle the question if you quoted it to a stranger. It does not have to share any words with the question. “What did you do last night?” answered with “went to the shop then came home” has no word in common with what was asked and is a perfect answer. This matters more than it sounds, because the instinct at 1am is to scan a reply for the words you used and conclude they were avoided; most good answers reuse none of them.
Partly answered means the reply engaged and did not settle it. “What time are you finishing?” answered with “not sure yet, I will let you know” is a real reply to the right subject that leaves you exactly as unable to plan as before. Partial answers are the largest category in most threads and the one that causes the most damage, because they feel like progress and produce none — you stop asking because you got a response, and a week later you still do not have a time.
Turned back means the reply is about the asking rather than the subject. “Why are you asking me that”, “does it even matter”, “here we go again”. These are the ones that feel worst and they are also the ones most often misread, because a reply can contain one of those phrases and a real answer at the same time — “I already told you, I was at Dave’s until eleven” is an answer delivered with irritation, and the irritation is not the finding.
Nothing means no reply came at all. This is the weakest evidence of the four and the one people weight most heavily. A question with no reply is usually a message with no reply, and a message with no reply is a phone put down. Before treating silence as an answer, check whether anything else in that message got answered either.
Why the four categories beat a yes-or-no reading
Reading each exchange as answered-or-not collapses the two useful middle states into whichever pole you already believed. A partial answer read as “answered” means you never notice that you have asked about the same weekend four times and still do not have a date. A partial answer read as “dodged” means you go into the next conversation carrying a grievance about a message that genuinely engaged with you. Sorting into four buckets takes about ten minutes on a month of thread and produces a picture neither of those readings can.
How do you tell a deflection from a question that just got missed?
You tell a deflection from a missed question by checking whether the message containing it was replied to at all: a question inside a message that got no reply was never really asked, while a question inside a message that got a long friendly reply about everything else was read and passed over.
Run the check in that order, because it disposes of most cases immediately. Find the unanswered question in your thread and look at what happened to its message. If the whole message sank — no reply, or a reply arriving hours later that starts a fresh subject — you are looking at a phone that was put down, a notification that was cleared while walking, a message read on a lock screen and mentally filed as dealt with. That is not evasion and no amount of re-reading will make it into evasion. If instead the reply came promptly, at length, and worked its way through the jokes and the plans and the how-was-your-day while stepping cleanly around the one direct question, the person read the question. What they did with it after that is the open matter.
The second check is position. Note where the question sat inside its message. A question that was the third of three, or that sat in the middle of a paragraph with content after it, is a question with a structural excuse. People reply to text messages by scanning for the thing that is easiest to respond to, and a question buried mid-paragraph is genuinely, routinely invisible. A question that was the entire message, sent on its own, with nothing before or after it, has no such excuse — and the difference between those two placements is usually the whole explanation for why one of your questions keeps vanishing and another one never does.
The isolation test
When the first two checks leave you unsure, run the isolation test: ask the question again, on its own, in a message containing nothing else, at a time when they are visibly replying to other things. This is the single most informative move available and it costs one message. A question that gets answered the moment it is isolated was never being dodged — it was being lost, and now you know the packaging was the problem. A question that comes back unanswered even when it is the only thing in the message has passed the only test that could have exonerated it, and you can stop wondering whether you asked badly.
Does asking three questions in one message stop them getting answered?
Asking three questions in one message reliably gets you one answer, because people reply to texts from the bottom up and from the easiest item to the hardest, and the two that lose are the ones that needed thought.
Watch what a stacked message does to a reply. “Did you see my message earlier? Are we still on for Friday? And did you book the thing?” goes out as one notification and comes back as “yeah”. That single word is a complete answer to one of those three questions and no answer at all to the other two, and nobody involved has done anything evasive. The reply was composed while walking, the reader held the last question in memory, answered it, and the first two were gone before the phone went back in the pocket. If you then read “yeah” as an answer to all three, you have booked a Friday that is not booked.
This has a direct diagnostic use. Go through your unanswered questions and note how many of them were the second or third item in their message. If nearly all of them were, your thread does not show a person avoiding you; it shows a habit of batching, which is yours to change and which will change the results within a week. If your unanswered questions are spread evenly across positions — some asked alone, some buried — the packaging is not the explanation and you can move on to the harder reading.
Why the important question should go last if it goes in at all
If you are going to put more than one thing in a message anyway, put the question you actually care about at the end. The last question in a message is the one held in working memory when the reply is composed, and it is the one most likely to survive. This is the opposite of how most people write a difficult message — the hard question goes first, followed by three softening paragraphs, and by the end of that the reply is a response to the softening. Better still, send it alone. A question worth an answer is worth its own notification.
What does it mean when the same question gets asked three times and never answered?
A question asked three separate times, each time clearly, and still never directly answered has stopped being an accident: three independent chances to answer, each one taken and each one used for something else, is a pattern rather than a run of bad moments.
This is the strongest single signal available in a text thread, and it is strong for a reason that has nothing to do with reading anyone’s mind. Any one instance has a large supply of ordinary explanations: tired, distracted, mid-shift, message read on a lock screen, question buried, phone died. Those explanations are individually likely and they do not stack. The probability that three isolated askings, spread across different days and different moods, all met a different innocent circumstance is much lower than the probability that any one of them did — and unlike any single instance, the pattern is visible in the thread itself rather than in your memory of how the messages felt.
Count carefully, because it is easy to inflate. A clean asking means the question was the whole message or clearly the point of it, phrased plainly, at a moment when the other person was replying to other things. Four half-asked versions folded into arguments do not make four askings; they make one long argument in which the question was never actually put. Wording that shifts between askings also weakens the count, because a person can honestly believe they answered the first version and not recognise the third as the same question. Three clean, consistently worded askings is the bar, and most threads that feel like ten askings turn out on inspection to contain one or two.
What the pattern still does not tell you
A question answered three times with a non-answer tells you the answer is not coming. It does not tell you what the answer would have been. The most common content behind a persistently unanswered question is not a secret — it is a decision the person has not made and does not want to be pinned to, or an answer they believe will end something, or an answer they think you will not accept and so would rather not spend. Treating a three-times-unanswered question as a confession is the mistake this whole method exists to prevent. What you have is a person who will not answer, which is enough to act on without inventing what they are concealing. You can read how the analysis handles that distinction if you want the reasoning behind it.
Is answering a question with a question always a deflection?
Answering a question with a question is a deflection only when the return question changes the subject — a return question about the same subject is almost always a request to clarify, which is what someone does on the way to answering.
The test is what the return question is about, and it is easy to apply. “Which Saturday, this one or next?” is about the thing you asked. It shares its subject with your question, it narrows rather than widens, and answering it moves you forward. “Why do you want to know?” is about you. It shares no subject with what you asked, it widens the conversation to include your motives, and answering it moves the conversation away from the thing you needed. Both are questions and they are not the same move at all.
There is a third case worth naming because it gets misfiled constantly. Some people return a question because they genuinely do not understand the frame of yours — “what do you mean, where do we stand?” from someone who thought the answer was obvious and is now alarmed that it was not. That reads on the page as identical to a dodge and is nearly its opposite: it is a person discovering a gap between two understandings. The way to separate it from a dodge is to answer the return question in one sentence and see what happens next. A person who was clarifying now answers. A person who was deflecting now has a new subject to talk about, and the original question has quietly left the conversation.
What are the innocent reasons someone never answers a direct question?
The innocent reasons a direct question goes unanswered are that the answer has not been decided yet, that answering is expected to start a fight, that the question is unanswerable as phrased, and that the person believes they already answered it — and between them these cover most of what looks like evasion.
Undecided is the biggest and the least considered. “Are we exclusive”, “do you want this to go anywhere”, “are you moving back” all ask for a position, and a person without one has nothing honest to say. The available replies are a lie, an admission of not knowing that sounds like rejection, or a swerve — and the swerve is the one most people take, not because they are concealing an answer but because they do not have one and do not want to be held to whatever they say under pressure. The signature is that the swerve is warm rather than cold, and that the person stays engaged with everything else in the conversation.
Expecting a fight produces the same silence from a different place. If the last three times a subject came up it ended badly, the fourth time it comes up the reply gets composed with the ending in mind, and a non-answer is the cheapest way to avoid a repeat. This one is uncomfortable to look at because your own thread contains the evidence for it: scroll back to the previous times the question was raised and see how those conversations finished. If they finished with an argument every time, you are looking at a learned avoidance that the two of you built together, and it will not be solved by asking harder.
Unanswerable as phrased covers questions that do not have the shape of something a person can answer. “Do you even care?” has no true answer that will land — yes sounds defensive, no is a bomb, and anything longer reads as an excuse. The same is true of any question that includes its own accusation. Questions like these do not get answered by anyone, honest or otherwise, and finding a run of them in your thread tells you about the questions rather than about the person.
The one that is nobody’s fault
Text is an interruptible medium and some people cannot hold a question across the interruption. A message read while a name is being called, a reply started and abandoned when someone walks in, a conversation resumed forty minutes later from the last visible line — none of these leave any trace in the thread, and all of them delete questions permanently. If the person you are asking loses things in exactly this way in the rest of their life, the unanswered questions in your thread are the same phenomenon and not a message about you. The way to test it is the isolation test above: a question with nothing around it survives an interruption that would have eaten it inside a longer message.
How do you ask a question so that it is hard not to answer?
You make a question hard not to answer by sending it alone, phrasing it so that a one-word reply completes it, and saying explicitly that either answer is fine.
Each of those three does a specific job. Alone means the message contains the question and nothing else — no preamble, no context, no second question — so there is nothing else in it to reply to instead. One-word-answerable means closed rather than open: “are you seeing anyone else” can be finished with a word, while “how do you feel about us” cannot be finished at all, and an open question sent into an avoidant thread produces a paragraph that answers nothing. Either-answer -is-fine is the part people skip and it is the part that does the most work, because most non-answers are a prediction about your reaction rather than a concealment of a fact. “Genuinely fine either way, I just want to know where I am” removes the reason not to answer, and it has to be true when you write it.
Timing is the fourth element and the one that quietly decides the rest. Ask when they are already replying to other things, so that a non-answer cannot hide behind a busy day. Do not ask at 1am at the end of an argument; a question asked there is answered by the argument, not by the question. Do not ask immediately after a non-answer either — the same question twice within an hour reads as pressure and gets a defensive reply that tells you nothing. A day’s gap between askings makes each one a separate event, which is exactly what you need if you are going to count them.
What to do with the answer you get
When an answer does arrive, take it. The failure mode at this point is asking a clean question, receiving a clean answer, and then immediately testing whether the answer is true — which converts a resolved question into an open investigation and teaches the other person that answering you does not end anything. If the answer is one you doubt, that doubt is a separate matter with its own evidence, and it belongs in a different conversation on a different day. The question you asked is closed. Close it.
What does your own answer rate say about the thread?
Your own answer rate — the share of questions asked of you that you answered directly — is the number most people never look at, and in a large minority of threads it turns out to be the lower of the two.
Count it the same way you counted theirs. Find the questions the other person asked you, and sort your replies into the same four buckets. The result is frequently uncomfortable in a specific way: people who feel stonewalled often have a high rate of partial answers of their own, because a thread where one person is anxious and the other is avoidant produces evasion on both sides. The anxious side evades differently — answering a question about plans with a statement about feelings, answering “are you ok” with “are you?”, replying to a direct question with three paragraphs that never contain a yes or a no — and it registers to the other person as exactly the same experience you are having.
There is a second reason to do this and it is strategic rather than moral. If your own rate is high and theirs is low, you can say so with a number instead of an accusation, and a number is much harder to argue with than “you never answer me”. If your own rate is low too, you have learned that the thread has a shared problem, which is a repairable thing, and you have avoided walking into a conversation with a complaint that can be answered by scrolling up. Either result is worth knowing before you start the conversation, and both are visible in the same ten minutes of counting.
When should you stop re-asking and decide instead?
You should stop re-asking after the third clean asking, because at that point the missing information is no longer the answer — you have it, and it is that the answer is not coming.
Name what the fourth asking is for before you send it. If the honest answer is that you want a different result from the same input, the fourth asking will not produce it and will cost you something: each re-ask lowers the price of the next non-answer, and a question asked six times is a question the other person has learned they can leave alone. If the honest answer is that you want the conversation on the record so that you can decide with it, that is a real reason, and it argues for one final message that says what you have noticed rather than asking again — “I have asked this three times and not had a straight answer, and I am taking that as the answer” is a sentence with a decision behind it, which is the only kind that changes anything at this stage.
Then answer the question that was underneath the question. Nobody counts unanswered messages for the pleasure of counting; the count is a proxy for something you are trying to decide, and the decision does not actually require the answer you were chasing. Being told nothing, three times, in response to a fair question asked plainly, is itself information about how much weight your questions carry here — and that is a thing you can act on today, without knowing what was behind the silence. If you want the same audit run properly on a real thread rather than by eye, put the conversation through the analyser, and if you want the wider method first, the situationship hub covers what else your thread can be made to show.
Check the neighbouring situation the same way
- Situationships: how to tell where you actually stand — the method this page uses, step by step.
- Long distance: what evidence you actually have — Distance removes the checking that used to happen without anyone doing it.
- First-month red flags, and the innocent version of each — Every flag, printed next to its best innocent explanation, at equal length.
Free tool · runs in your browser
Not a lie detector. Inconsistency is not proof of deception. This counts what is in your thread — timestamps, gaps, wording. It cannot tell you whether someone is lying.
Nothing you paste leaves this browser. No account, no upload, no model call.
This counter is deliberately generous. A reply that answers the question in completely different words — “what did you do last night” → “went to the shop then came home” — is scored as answered, because it is one. Only a reply that turns the question back on you, or leaves it untouched, is scored lower. A tool tuned the other way would flag half of ordinary conversation, and you would be arguing on its behalf.
This counted the gaps. It cannot read the messages. Run the actual conversation →
Common questions
- What does it mean when he avoids answering your questions over text?
- Avoiding a question over text most often means the question was structurally hard to answer rather than deliberately dodged — it arrived third in a message of three, or it landed at the end of a long paragraph, or it needed a decision the other person has not made yet. Deliberate avoidance has a different shape: the message gets a reply, the reply engages with everything except the question, and the pattern repeats when the same question is asked again on its own. One skipped question is noise. The same question skipped three times, each time asked alone, is a finding.
- How can you tell if someone is deflecting or just missed the question?
- You tell a deflection from a miss by checking whether they replied to the message at all. A message that got no reply is a missed message, and the question inside it was never really asked. A message that got a warm, detailed reply answering the small talk while leaving the one direct question untouched is a different event, because the person demonstrably read it. The strongest version of that check is asking the question again on its own, with nothing else in the message: a question that survives being isolated and still comes back unanswered was not lost.
- Does asking several questions in one message stop them getting answered?
- Yes — a message carrying three questions usually gets one answer, and the other two disappear with no intent involved on either side. People reply to text messages from the bottom up and from the easiest to the hardest, so the question most likely to be answered is the last one asked and the least demanding one. If your unanswered questions keep turning out to be the second or third thing in a message, the problem is the packaging, not the person. Re-ask the important one on its own and see what comes back.
- Is answering a question with a question always a deflection?
- No — answering a question with a question is only a deflection when the return question is about something else. “Which Saturday do you mean?” is a request to clarify and is what a person does when they intend to answer. “Why are you asking me that?” is a question about you rather than about the subject, and it leaves the original question exactly where it was. The test is subject matter, not form: does the return question move toward an answer or away from one?
- Can a thread of unanswered questions prove someone is hiding something?
- No, a thread of unanswered questions cannot prove someone is hiding something. This is not a lie detector, and inconsistency is not proof of deception — the most common reasons a direct question goes unanswered are that the person has not decided, that they expect the answer to start a fight they lack the energy for, or that answering means admitting something embarrassing and unrelated to you. What a run of unanswered questions does prove is that you still do not have an answer, which is a real problem with a real solution, and a smaller one than the accusation you may be tempted to make instead.
- How do you ask a question so it is hard not to answer?
- You ask one question, put it alone in its own message, phrase it so a short answer completes it, and say out loud that either answer is acceptable. “Are you seeing anyone else? Genuinely fine either way, I just want to know” is answerable in one word and costs the other person nothing to answer honestly. The versions that fail are the stacked message with three questions in it, the question buried under a paragraph explaining why you are asking, and the question phrased so that one of the two answers is obviously the wrong one to give.
- How many times should you re-ask a question before you stop?
- Three clean askings is the practical limit — meaning three times where the question was alone in its message, plainly phrased, and asked at a moment the other person was replying to other things. After the third, the information you are missing is no longer the answer to the question; you already have it, which is that they are not going to answer it. Re-asking a fourth time changes nothing about them and reliably makes you feel worse, so the next move is deciding what a permanent non-answer means to you rather than collecting a fourth instance of it.
A suspicion score, not a lie detector. It measures what does not line up — nothing more. Everything else is your call, which is the only place it can honestly sit.