What should I say if I get called on in a meeting and I wasn't listening?
Ask for the question, not a recap. Say something short and true, like "Sorry, I lost the last bit — can you give me the question again?", then answer it. That costs the room a few seconds, gets you the one thing you actually need, and sounds ordinary, because everyone drifts. Don't bluff an answer to a question you didn't hear, don't blame your connection unless it really dropped, and don't apologise at length. If you were gone for a whole topic, ask for the one-line version rather than a full recap. Better still, set things up so you don't need the line: a live, multi-resolution meeting summary like Canary's shows what's being discussed right now and what was said in the last two minutes, so when your name is called you can glance, confirm the question in your own words, and answer in the space of a normal pause.
Last updated September 19, 2026
Ask for the question, not a recap. When you’re called on and you weren’t listening, the short honest line — “Sorry, I lost the last bit. Can you give me the question again?” — is almost always the right one. It’s true, it costs the room a few seconds, and it gets you the only thing you strictly need to answer. The rest of this page covers when a different line fits better, what never to say, and how to set things up so you can answer instead of asking.
This is the third page on this site about the same moment. What did I miss? is about finding out what happened. Why do I zone out? is about why you were gone. This one is about the words: what comes out of your mouth in the second after your name.
What you actually need in that second
To answer, you need two things: the question itself, and enough of the conversation around it to know what it means. “Can we do Friday?” is unanswerable if you don’t know what it is.
Most of the time you’re only missing the first. Your name is the one input that reliably drags attention back into a meeting — you surfaced because you heard it — so you often catch the tail of the question, or know the topic from earlier, and only lost the specific ask. That’s the good news, because the question is the cheapest thing to ask for. People restate a question in one sentence, and when they do, they tend to add the context without being asked: “the launch — can we move it to Friday?”
The harder case is when you were out for a whole topic and the question sits on top of ten minutes you didn’t hear. The question alone won’t rescue you there, and you need a different line.
Lines that work
Pick the smallest request that lets you answer. Every line here is true when you say it. That’s the point.
| Situation | What to say | Why it works |
|---|---|---|
| You heard your name but not the question | ”Sorry, I missed the question — can you say it again?” | Costs a few seconds; the asker usually restates it with context |
| You know the topic but not the specific ask | ”Just so I answer the right thing: is this about the date or the scope?” | A clarifying question you might ask anyway, and it shows you know the thread |
| You were out for a whole topic | ”I lost the thread for a minute — can someone give me the one-line version?” | Asks for one line, not a recap, and is honest about the size of the gap |
| You caught the question but need to check | ”Let me confirm and come back to you before we wrap.” | Buys time without guessing — only if you actually come back |
| You don’t know the answer, attention aside | ”I don’t know yet. I’ll find out and post it in the channel today.” | A committed follow-up beats an improvised answer every time |
| Your audio really did drop | ”You cut out for me — could you repeat that?” | Fine when it’s true, and only then (see below) |
Two notes on delivery. Say it once, plainly, and stop: the lapse is ordinary, so the line should sound ordinary. And don’t narrate where you went. “I lost the last bit” is complete. “Sorry, I was answering something in Slack” is more than anyone asked for, and it starts a different conversation.
What not to say
Don’t bluff. Answering the question you think was asked is the most tempting move and the most expensive. When you guess right, nobody notices. When you guess wrong — and you will, sometimes, because you’re guessing — you’ve answered a question nobody asked, and the room has to unwind that before it can re-ask. Asking takes a few seconds. A confident wrong answer takes longer to clear up and people remember it longer.
Don’t blame the connection when it wasn’t the connection. “Sorry, you froze for a second” is the classic remote-work cover story. It’s a small lie, but it’s easy to spot when it keeps happening, and the people who spot it quietly discount the other things you say. Keep that line for the times your audio actually dropped.
Don’t ask for a recap after a thirty-second lapse. “Can someone catch me up?” bills everyone for your gap when all you needed was the question. Save it for when you really were out for a whole topic, and even then ask for one line.
Don’t apologise at length. A paragraph of sorry turns a two-second lapse into a moment. One “sorry” is plenty. None is fine.
Better: answer instead of asking
The lines above are the fallback, and there’s nothing wrong with using them. The better position is to not need them: to glance, get the question and its context, and answer in the time of a normal pause.
That requires something that already holds the last few minutes of the conversation when your name is called. It has to exist before the question, because two seconds isn’t long enough to create it. Here’s what’s actually within reach in most meetings:
| What you could look at | Useful in the two seconds you get? | Why |
|---|---|---|
| Your memory | Only if you were half-listening | Nothing from the part you missed |
| The meeting chat | Sometimes | Only what someone happened to type |
| Live captions or a transcript pane | Rarely | Every word; reading back two minutes of dialogue takes far longer than a pause |
| Zoom’s or Teams’ AI assistant panel (where licensed and enabled) | Not really | You type a question and wait while the room waits for you |
| After-the-call AI summaries (Otter, Fireflies, Fathom, Granola) | No | They’re written after the meeting ends |
| A live rolling summary | Yes | The last few minutes, already condensed, one glance away |
The transcript row is the one people reach for first, and it’s the one that fools them. It has the answer, but as raw dialogue, and you’d be reading it while the room watches you read it. A live transcript and a live summary are different layers; re-entry needs the condensed one. The platform assistants are real in-meeting features, but they’re on-demand — you ask, then it answers — which is a second context switch in the exact moment you’re recovering from the first. The platform-native meeting AI entry and Canary vs Microsoft Copilot go into that difference, including where the bundled tools are the better choice.
Canary is a real-time, bot-free meeting summarizer. It captures your computer’s system audio (no bot in the call, no plugin) and shows a live, multi-resolution rolling summary — from what’s being said right now to the whole call — so you can catch up the instant your name is called. In practice, the called-on moment goes like this:
- Your name comes up. Even collapsed to a small pill, the widget shows a one-sentence headline of what’s being discussed right now, refreshed every few seconds. Often that alone tells you what the question is about.
- If it doesn’t, look at the card. Now covers roughly the last half-minute; 2 min covers what led up to it. If you’d toggled to another view, the Missed? button jumps straight back to Now.
- Confirm in your own words, then answer. “Just to check — you’re asking whether we can move the launch to Friday? Yes, if QA signs off by Wednesday.”
Step 3 matters. A summary is a condensed reading of what was said, and it can miss nuance or get a detail wrong — how accurate AI meeting notes are covers where that happens. Restating the question costs one sentence, catches a misread before you answer the wrong thing, and it’s honest: you’re checking your understanding, not claiming a memory you don’t have.
That’s the whole reason for the multi-resolution design. Now gets you the question, 2 min gets you its context, and the longer views tell you whether this is the thing you were waiting for. It works the same on Zoom, Google Meet, Teams, or anything else your computer is playing, because it listens to system audio rather than joining the call. If what you really want is a record for tomorrow rather than help in the moment, Canary vs Otter says plainly where Otter is the better fit.
If you run the meeting: say the name first
Half of this problem belongs to the person asking. “What do you think, Priya?” puts the name at the end, so by the time Priya’s attention arrives, the question has already gone past. Flip it: name first, then the question, with its context inside it. “Priya — on the launch date: can QA be done by Friday?”
A name is what pulls attention back, so put it where it can do that job, and put the question after it. If you can see someone’s lost, restate the question before they have to ask. It’s a small habit, and it saves everyone you call on from needing any of the lines above.
Making it happen less often
The lines are for the moment. The drifting behind them has its own fixes, and the zone-out page goes through them: give yourself a job in the meeting, take structural notes rather than verbatim ones, close the second monitor’s Slack, and leave gaps between calls. The back-to-back pillar covers the stacked-calendar version. None of these stop drift entirely. What changes the outcome is making the re-entry cheap, so a lapse costs a glance instead of the rest of the call — the context-switching cost is in coming back, not in looking away.
If you drift not just in meetings but in things you actively care about, and have for a long time, the ADHD page is a better starting point than this one. Nothing here is medical advice.
The line to say at the start of the call
If your recovery plan includes a summarizer, the sentence you say at the start of the meeting matters more than the one you say when you’re called on. Bot-free capture puts nothing in the participant list and no banner on anyone’s screen, so nobody knows it’s running unless you tell them — a smaller footprint, not a smaller obligation. One line covers it (here’s how to word it), and consent rules vary by region — some places need one participant’s consent, others everyone’s (one-party vs two-party consent) — so default to saying it. The widget also shows up in a whole-screen share like any other window. Recovering quietly from a lapse is fine. Capturing quietly isn’t.
Bottom line
When you’re called on and weren’t listening, ask for the question, not a recap: “Sorry, I lost the last bit — can you give me the question again?” Use the one-line-version request only when you were out for a whole topic, keep “you cut out” for when the audio really did, and never bluff. Better, keep a live summary running — and say so — so that when your name comes up you can glance, confirm the question in your own words, and answer. That’s what meeting situational awareness looks like in the two seconds that count.
Frequently asked questions
Is it OK to admit you weren't listening in a meeting?
Yes, briefly. Drifting in meetings is normal, and a short, honest line like "I lost the last bit, can you repeat the question?" sounds like what it is: ordinary. What damages credibility is the alternative — answering a question you guessed at, which goes wrong often enough that people notice, or a long apology that turns a small lapse into a moment everyone remembers. You don't have to say where you went; "I lost the thread" is complete. If it's happening in every meeting, that's worth fixing upstream, but in the moment one clean sentence is the whole job.
What should you never say when you're called on and weren't listening?
Three things. Don't bluff: answering the question you think was asked risks answering the wrong one, which costs far more than asking would have. Don't blame your connection or your mute button when it wasn't them; it's a small lie, it's easy to spot when it recurs, and people who notice it start discounting the rest of what you say. And don't ask for a full recap after a thirty-second lapse — "can someone catch me up?" bills the whole room for your gap when you only needed the question. Ask for the smallest thing that lets you answer.
How can I catch up in two seconds when my name is called?
Only by reading something that already exists, because two seconds isn't enough time to scroll a transcript, type a question into an AI panel, or ask. A live rolling summary is the thing that fits: Canary keeps summaries of the call at several time horizons while it happens, and even collapsed, its widget shows a one-sentence headline of what's being discussed right now. Glance at that, open the last-2-minutes view if the question builds on something earlier, then confirm in your own words — "just to check, you're asking whether we can ship Friday?" — before you answer. That's honest, and it catches a misread before it becomes a wrong answer. Tell participants at the start of the call if a notetaker is running.