Common questions › Improving your visibility
What if the assistants are right about us?
Then we say so. If buyers genuinely dislike something and the assistants have correctly noticed, that is a product problem and we report it as one rather than dressing it up as a content opportunity.
This is the finding nobody markets, and it is one of the more valuable things a scan produces.
How it shows up
The pattern is recognisable: the assistants raise the same reservation about your product across many different questions, and the buyer evidence underneath — reviews, forum threads, the things people actually complain about — says the same thing. The assistants are not confused. They are summarising a consistent view.
Why we refuse to convert it into a content task
Because publishing copy that argues against a real defect does three bad things at once. It does not work, because the assistants are reading the sources rather than your marketing. It wastes the quarter. And if it does move the answer, you have persuaded an assistant to recommend a product to somebody who will be disappointed by it, which comes back as returns and worse reviews.
A tool that turns every finding into something billable will eventually make that recommendation. Ours is built not to.
What we do instead
We report it as what it is, with the evidence attached: this is the reservation, this is how often it appears, these are the sources it comes from, and here is what buyers say in their own words. That is a document for a product meeting rather than a marketing one.
The narrower case worth separating
Sometimes the assistants are working from something that used to be true — an old formulation, a discontinued version, a problem you fixed two years ago that the web never caught up with. That is not a product problem, it is an outdated-evidence problem, and it is one of the most tractable things we find. Telling the two apart is a matter of looking at the dates on the sources, which is why we keep them.
See the intended experienceExplore a static example of the intended experience. Public app access and client onboarding are not available.
Explore example report