Find what your data can't answer yet
Esta página aún no está disponible en español. Se muestra la versión en inglés.
Find the questions your data really can’t answer yet, tell them apart from the ones that only need a view, and turn the real gaps into a short list of what to connect next.
Before you start
Section titled “Before you start”- Permissions: anyone in your organization can read question badges, Inbox cards and review verdicts. Anyone who’s signed in can connect a system from Connect in the rail.
- Data you need: some connected data, and questions in your Library. The example uses the Curio Library in these docs.
- Credits this uses: reading badges, cards and verdicts costs nothing. Each message to the Librarian uses a credit.
Say someone asks the Librarian, “How many support tickets did we close last month?” The answer reads Query declined. Nothing is broken. Curio has never connected a helpdesk, so there’s nothing to count.
1. Don’t mistake No view yet for a gap
Section titled “1. Don’t mistake No view yet for a gap”Two sets of labels look alike and mean different things:
| Where | Labels | What they tell you |
|---|---|---|
| A collection page | Answered, Answerable, No view yet | Whether a view answers the question |
| The Questions tab and a question’s panel | ANSWERABLE, PARTIAL, UNANSWERABLE | Whether your data reaches the question at all |
No view yet only means that no view answers the question. The data may be sitting right there. A real gap shows up as UNANSWERABLE or PARTIAL on the Questions tab.
2. Check the Questions tab
Section titled “2. Check the Questions tab”Open Library, then Questions, and read the badge on each question:
- UNANSWERABLE: the data isn’t there. The question’s Ask button stays off until you connect a source or refine the question.
- PARTIAL: some of the data is there, so an answer may be incomplete.
- No badge: not checked yet. The Librarian works it out as it answers.
Write down each UNANSWERABLE and PARTIAL question, and the data it would need.
3. Read Can’t answer this yet cards
Section titled “3. Read Can’t answer this yet cards”Your Inbox files a Can’t answer this yet card when Querri finds a question your data can’t answer, and the digest counts them as “questions your data cannot answer”. Open Evidence to see why.
Accepting the card records a fact. It doesn’t build a view or connect anything.
4. Look for gap verdicts
Section titled “4. Look for gap verdicts”Below the cards, the latest review of your team’s questions can mark a group of questions gap: the data to answer them isn’t in the Library. Connect the data takes you to connect a source. Nothing connects by itself.
Why put these near the top of your list? They come from questions people actually asked, again and again.
5. Notice declines in chat
Section titled “5. Notice declines in chat”When nothing in your Library relates to a question, the answer reads Query declined, and its route row says Searched your library. The Librarian may then try to build a table and report that it couldn’t, as it does for Curio’s support tickets.
A decline is often a gap. Before you add it to the list, check that you’re in the workspace where the data lives, because that decides what the Librarian can find. Then ask once more, naming the table or KPI you’d expect it to read.
6. Turn the list into your next connection
Section titled “6. Turn the list into your next connection”Next to each gap, write the system that holds the data. Curio’s support tickets would need a helpdesk. Then count. The system that closes the most gaps, or the one behind the gap people hit most often, goes first.
Decide what to connect first walks through the counting, and through choosing between a file and a connection.
7. Build views for the questions that aren’t gaps
Section titled “7. Build views for the questions that aren’t gaps”A question marked Answerable on a collection page has the data but no view. Its card offers + Build a view to answer this, which opens Librarian chat with the request written out. Nothing happens until you send it, and sending uses a credit.
Check your work
Section titled “Check your work”- Every question on your list reads UNANSWERABLE or PARTIAL, or came from a Can’t answer this yet card, a gap verdict or a decline.
- None of them is only No view yet.
- Each gap has a system written next to it.
- Once you’ve connected that system and the data has settled, those questions read ANSWERABLE or PARTIAL.
Troubleshooting
Section titled “Troubleshooting”A question still reads UNANSWERABLE after you connected the data. Querri marks the questions new data can answer once it settles, so give it a little while. If it still doesn’t change, refine the question so it names what the data covers.
Accepting a Can’t answer this yet card didn’t change anything. It records a fact and nothing else. The question stays unanswerable until the data is in.
The collection page says No view yet, but the Questions tab says ANSWERABLE. That isn’t a gap. Ask the question, or ask the Librarian to build a view for it.
Every question reads UNANSWERABLE. No data may be connected yet. Questions set up in onboarding exist before any data does. See Decide what to connect first.
Next steps
Section titled “Next steps”- Decide what to connect first: pick the system that closes the most gaps.
- Anchor and refining questions: what each question badge means.
- How Querri answers a question: why an answer gets declined.
- Work through your Inbox: cards and review verdicts, gap included.