On this page
Somewhere in your CRM, the customer records where sales keeps its call notes, there is a note like the first row below, from a buyer choosing a 3PL (a third-party logistics company). Somewhere in a spreadsheet, started the week someone asked whether AI assistants recommend your company, there is the second.
| Where it sits | What it says |
|---|---|
| A first-call note in the CRM | Their current 3PL misses the carrier cutoff in Q4, so orders ship a day late. "We need everything in by 2pm out the same day." |
| The AI tracking sheet | "best 3PL" |
Google reported in May 2026 that the average US search in AI Mode, its chat-style answer mode, runs triple the length of a traditional search. Tracking only a category can leave you measuring a shortlist your buyers never see.
Building that list from the notes by hand means reading a quarter of notes and emails and guessing which ones matter. Then someone reads what the list brings back: fifteen questions on two assistants, asked three times a week, is ninety answers a week to read and file before anyone decides anything.
At Qvery, we help 3PLs stop paying sales staff to rebuild tracking lists, with custom AI agents that turn call notes into buyer questions and flag those naming no one.
The agents read the notes and write one question per buyer situation, each tied to the note it came from. Everything below runs on sixteen invented notes from an invented fulfillment company of about 180 people with warehouses in Ohio and Pennsylvania; nothing in them is a real company, person or account.
A Short Query And A Buyer's Situation Get Different Shortlists
We compared answer pairs from the GEO Agent's daily records for August 2026, across every topic and country it tracked, to separate a change of question from a change of day.
A New Question Changes The Shortlist More Than A New Day Does
% of companies named again
View the data
| Label | ChatGPT | Google AI Mode |
|---|---|---|
| Same question, next day | 59.86% | 56.01% |
| Two situation questions, same topic | 45.90% | 41.70% |
| Short query and situation question, same topic | 23.09% | 23.07% |
A short query and a situation question shared no company at all in 36.59% of pairs on ChatGPT and 32.70% on Google AI Mode, against 7.81% and 5.50% for the same question a day apart.
Two different situation questions in the same topic shared 45.90% of their named companies on ChatGPT and 41.70% on Google AI Mode.
The sources the answers cited changed too: from 4 to 10 August, short-and-situation pairs shared 16.13% of them on ChatGPT and 17.93% on Google AI Mode, against 45.95% and 39.31% for repeat askings.
These records show overlap, not why a company gets named. A situation question changes the need as well as the length.
- A list of short queries measures a different shortlist from the one a buyer in each situation gets. The short comparison question tells you how you do on the general question, and nothing about the buyer who needs same-day shipping in November.
- Two situations in one topic still need two questions. They share fewer than half their names.
- One asking is a sample. Even the same question loses around two in five of its names overnight, so every question gets asked more than once before anyone reads a number.
People who run these checks by hand land in the same place:
Tips from Reddit
Instead of relying on a single prompt or a tool’s visibility score, I’d suggest tracking a fixed set of relevant customer queries
the run-to-run variance in AI answers is huge, so anything single-shot is unusable
So every question has to run every day, on both assistants, with every answer kept, before anyone reads a share of names.
What the Agents Write From a Quarter of Notes
The agents start where buyers describe their situation before anyone has sold them anything: first-call notes, lost-deal reasons, emails sent before a quote and prospects' questions to support. Four of the sixteen invented notes they read:
A buyer situation is a kind of company with a need that changes its choice of provider. The agents group the notes by situation before writing any question, so each question stays traceable to its note and duplicate needs stay together.
One row leans on an inference: the agents attached N01 to the hazardous-materials situation and added that N01 mentions two aerosol SKUs, but its need for hazmat handling is unknown. That is the row to rule on. The note never says the buyer asked about hazardous materials, so N01 comes out of it.
An unflagged inference becomes a question no buyer asked. That is why the agents write "unknown" wherever a note is silent, and list every note they left out with its reason; on this run, one: N10, a current client's billing question.
Piotr BabelPartner @ QveryEvery question the agents write carries the ID of the note it came from, and that ID is how anyone checks their work. Where a note is silent on the kind of company or the need, they write unknown instead of guessing. The aerosol row shows the failure to watch for, a guess that reads like a fact, and the owner catches it by opening the note beside the question. Wire the CRM export so every note keeps its ID, and that check takes seconds.
Then the agents turn each situation into the question a buyer in it would type before talking to anyone, in the buyer's own words where the note has them, and add one short search-box question per kind of provider, kept for comparison.
| Note | The buyer's own words | The question written from it |
|---|---|---|
| N01, first call | "We need everything in by 2pm out the same day." | I run a Shopify skincare brand that ships about 1,800 orders a day, three times that in November and December. Which fulfillment company can ship orders received by 2pm the same day, even in peak season, when our current one misses the carrier cutoff? |
| N04, email before a quote | "have to stay under 77 degrees" | Which fulfillment company can store and ship supplements so they stay under 77 degrees? Our last provider had a heat problem and we lost a pallet. |
| None: kept for comparison | none | best ecommerce fulfillment company |
Who Rules on Each Question
The agents hand every question, with its note beside it, to someone who sells to these buyers, who rules: keep, reword, reject, or add. On the invented run, four rulings went beyond keep:
| Question | Ruling | Why |
|---|---|---|
| Q03: a West Coast warehouse | Reject | We can't serve it today; tracking it measures a decision nobody has made |
| Q07: a low per-pallet receiving fee | Reject | The lost deal was two quotes compared, not a question asked |
| Q14: onboarding in 45 days | Reword | It asked "how fast", which invites a timeline instead of names. Now: "Which fulfillment companies can onboard us before Black Friday?" |
| "3PLs in Ohio" | Add | N11 says the buyer found us by asking ChatGPT for 3PLs in Ohio; no question kept it |
Vlad ShvetsPartner @ QveryA tracking question earns its place only if it describes a buyer you can serve and want this year. One about a West Coast warehouse you do not run measures a decision nobody has made, and every week it costs an owner reading time and puts a number on a report nobody will act on. Treat reject as the most useful ruling on the list, and give it to whoever sells into that kind of buyer.
A question a buyer reports typing stays in the note's words, even when it reads like a search. That is why "3PLs in Ohio" went back on the list.
Sixteen questions went in and fifteen came out: thirteen situation questions and two short comparison questions.
The agents file each question under the person who sells into that kind of buyer. Each segment gets one owner, who approves its questions monthly and reads its answers. The invented company's list:
| Question, shortened | Segment | Owner |
|---|---|---|
| Q01: same-day shipping for orders in by 2pm, in peak season | Speed and peaks | Head of sales |
| Q02: a system-to-system order feed (EDI) and retailer labels for a first wholesale account | Retail and marketplaces | Integrations lead |
| Q04: supplements stored and shipped under 77 degrees | Special handling | Operations director |
| Q09: returns processed within 48 hours and graded | Kitting and returns | Account manager |
| Q10b: 3PLs in Ohio (comparison question, reported by a buyer) | Speed and peaks | Head of sales |
What the Agents Check Every Monday
Each week the agents watch the stored answers for two things: questions whose answers name no company, and pairs of questions that keep naming the same companies. They flag both for the segment owner.
Read the week's stored answers
Every answer to every question on the list, with the companies it named, from the GEO Agent's records or the sheet your team keeps, plus this month's file with each question's segment and owner.
Run every Monday
On the previous week's answers, so each question has been asked several times on each engine before anything is flagged.
Apply two flags
A question whose answers named no company in most of the week's askings. Two questions in one segment whose answers shared four in five of their companies or more across the week; in the GEO Agent's August records, two situation questions in one topic shared under half on an average day.
Write one note per owner
Each flagged question with its flag, the week's answers behind it, and a suggested ruling: reword it, merge it with its twin, or keep it with a reason.
Change next month's file only
The owner rules in the note, and an approved change goes into next month's file, never the live list, so this month's numbers still compare like with like.

| The agents may | The agents never |
|---|---|
| Read your exported notes, stripped of names, contacts, prices and account numbers | Read anything beyond those notes, the stored answers and the list file |
| Read the answers already collected | Ask ChatGPT or Google AI Mode anything themselves |
| Flag a question and suggest a ruling in the owner's note | Change or delete a question on the live list |
The return is reading time. The ninety answers a week stop landing on one desk, and each owner gets a short Monday note with the flagged questions and the answers behind them. We count both sides every week: the reading hours your team got back, and the bad questions stopped before a list was approved.
Send Us a Quarter of Your Sales Notes
Send a quarter of first-call notes, lost-deal reasons and buyer emails, with the answers you have stored so far. The agents write the first list from last quarter's notes, and within two weeks of access each segment owner has their questions to rule on.
Frequently asked questions
What is an LLM tracking query?
A question you put to ChatGPT, Google AI Mode or another assistant on a schedule, to see which companies its answers name. Written from a buyer's situation, it measures the shortlist that buyer would see; written as a two-word search, it measures a different one.
Should our tracking questions include our company name?
No. A question with your name in it measures what the assistant says about you, and the answer repeats your name because the question did. Keep those on a separate list, and keep this one for questions a buyer asks before they know you.
Should we still track short queries, like "best 3PL"?
Keep one per category as a comparison question. In the GEO Agent's August 2026 records, only 23.09% of the companies ChatGPT named for a short query were also named for a situation question in the same topic (23.07% on Google AI Mode), so the short query can't stand in for the buyers' situations.
Why write tracking questions from sales notes rather than our own pages?
Your pages describe what you sell in your own words. A note records the need that made a buyer shop, like supplements that must stay under 77 degrees, and a question built from that need asks for the shortlist the buyer is shown, which is the one you want to be on.
Should a tracking question include the year?
No. Buyers write their need, not the year, and the month lives in the list's file name instead, so each question's history stays comparable from one month to the next.
What should a note hold for the agents to write a good question?
The buyer's own sentence where there is one, the kind of company, and the need that changed their choice of provider, such as a cutoff time, a temperature or a delivery area. A note with only the rep's summary still works, but the question comes out in the rep's words, with the missing details marked unknown.
Who should own the list?
Whoever owns the pipeline signs the file. Each segment of questions belongs to the person who sells into that kind of buyer, because they can tell a real situation from a plausible one.
What if we sell in more than one country?
Keep one list per country. The same question in two countries is two questions with two sets of answers, and the notes from each market should feed its own list.
Why can't we check each question once a month?
Because one answer is a sample. In the GEO Agent's August 2026 records, the same question asked a day later kept only about three in five of the companies it had named, so a monthly check reads one draw and calls it a trend.
Do we need different questions for ChatGPT and Google AI Mode?
No. The question is the buyer's, so it stays word for word on both, and the results stay in separate columns: a share blended across two assistants hides which one leaves you off.
Should lost-deal notes go into the tracking list?
Yes. A lost deal records a situation you were in and did not win, which is the shortlist most worth watching. The owner still rules on each one: on the invented run, a lost deal that was two quotes compared, with no question asked, was rejected.
Can the same list show us our competitors?
It already does. A question that names no company returns the providers the assistant picks, rivals included, so each row shows who is on that buyer's shortlist when you are not.
Can the agents change our tracking list automatically?
No. The agents flag questions and put a suggested ruling in each owner's note; rewording, merging or keeping a question is the owner's call, and an approved change waits for next month's file instead of overwriting the live list.
What happens to customer details in our call notes?
The export is stripped of names, contact details, prices and account numbers before the agents see it, and the work runs under a data processing agreement with Qvery AI OÜ, an EU company.