Question detection
Detect questions during calls automatically
No hotkey, no wake word, no “hey copilot”. Trippi Cue follows the conversation and speaks up on one thing: the moment somebody asks you something — and stays quiet the rest of the time, which is most of it.
Trippi Cue
Question
Karl · “…so that is the timeline from our side.”
Anna · “Right, that works.”
Karl · “And how would you handle the migration window on your side?”
Suggested answer · asked by Karl
Over a weekend, with the old system readable for a week and a one-hour path back if anything looks wrong.
A mock-up of the window, not a screenshot: the real one goes here once the extension is in the store.
What counts as a question
Five shapes, and only one of them has a question mark.
Recognised speech arrives without reliable punctuation, so a question mark is a bonus rather than the signal. These are the shapes that actually get through.
A direct question
“What does the migration window look like on your side?”
The obvious case — and the only one where punctuation helps, when the recognised text has any.
A question without the question mark
“So you would keep the old system readable for a week”
Recognised speech often arrives unpunctuated. The opening word carries the signal instead: what, why, how, can, would, do, is, have.
An instruction
“Walk us through how the pricing works for fifty seats”
Never has a question mark and is still a request for an answer. Imperatives are their own branch: tell me, describe, explain, show us, take us through.
A question with your name in it
“Anna, is there anything blocking the release?”
Your name — the first name, the one people actually use in calls — is one of the strongest signals there is.
A follow-up to a follow-up
“And if the volume doubles?”
Short, contextless on its own, and still yours to answer. The model sees the previous lines, so the thread is not lost.
What it ignores
The quiet is the feature.
A copilot that reacts to everything gets closed in the first ten minutes. Four kinds of line never become a card.
Small talk and agreement — “yeah”, “sure”, “makes sense”, “absolutely”
A line made entirely of these is never a question. This is most of what is said in a meeting, and dropping it locally is what keeps the window quiet and the cost sane.
Your own words — Anything you said yourself
Cue does not answer the question you just asked somebody else — checked twice, in the filter and again when the answer comes back.
Questions aimed at other people — “Karl, can you share your screen?”
The model is given the participants and your name, and asked exactly this: was this addressed to the user? If not, no card.
Rhetorical questions — “Who wouldn’t want that?”
A question in form, not in function. This is the judgement a keyword list cannot make, which is why the decision belongs to a model and not to a regular expression.
How the decision is made
Three stages, two of them filters.
-
1
Local filter, on your machine
Runs on every recognised line, costs nothing and sends nothing anywhere. Deliberately generous: it throws away the obviously empty, not the doubtful. A missed question costs more than an extra check.
-
2
The model decides ownership
The recent lines, the participant names and your own name go off as one prompt. The model answers whether the closing turn was addressed to you, what type it was, who asked, and how sure it is.
-
3
The gate on the way back
Below the confidence threshold — nothing is shown. Same question again within a minute — merged into the existing card instead of a second one. Automatic answers switched off — only your own questions get through.
When it gets it wrong
What to do about a false positive — or a miss.
Both happen. Neither needs support: every fix here is one click inside the window.
It answered something not meant for me
Dismiss the card — one click, and the window is clean again. If it keeps happening in a particular call, the likeliest cause is that your name never appears in the meeting: set it in the window so the model knows who you are.
It stayed silent when I was asked
Ask it yourself in the field at the bottom: the same card, on demand, with the meeting still as context. That path skips every filter on purpose.
It answers too often
Turn off automatic answers in the settings. The window then reacts only to what you type — some people run it that way from the start.
It heard the question wrong
The strip of recognised lines under the cards shows what it actually heard. A name mangled by recognition is the usual culprit, and it is visible right there.
Timing
Why it arrives when it does.
A card lands a few seconds after the question is finished — the time it takes to recognise the closing words and get an answer back. It is not instant, and it does not need to be: an answer that arrives while the room is still looking at you is on time.
Waiting for the turn to end is deliberate. Answering half a question produces an answer to something nobody asked, and the correction costs more attention than the wait.
Privacy
What detection sends, and where.
Detection itself starts on your machine: the local filter reads the line and sends nothing. Only what passes it — a dozen recent lines, the participant names, your name — goes to our backend and on to the model, and is dropped with the answer.
FAQ
About detection, specifically.
How long does detection take?+
A card appears seconds after the turn ends. The delay is mostly recognition and the model call — there is no polling interval and no batching to wait for.
Does it need a hotkey or a wake word?+
No. There is nothing to press and nothing to say: the last click you make is the one that starts the session.
What if two people ask me things at once?+
Each request gets its own card. Three are on screen at a time; the fourth pushes out the oldest.
Does it work when the meeting is not in English?+
Recognition follows the language of the call. The local filter’s word lists are English, so in other languages the model does more of the work — which means slightly more calls, not fewer cards.
Can it tell a task from a question?+
Yes, and it says which: a question gets an answer you can say out loud, a task gets how to approach it rather than what to say.
Why is confidence not shown on the card?+
Because a number next to an answer invites you to argue with it instead of reading it. It is used as a threshold: below it, the card never appears at all.
Does it store the questions it detected?+
No. The lines live in the tab’s memory during the call and are dropped with the answer. Nothing about the content reaches our database.
The next question aimed at you, caught while it still matters.
Trippi Cue is free in the Chrome Web Store. Ten minutes of live answers without an account.