Skip to content

Treat missing public feedback as an evidence gap

Treat missing public feedback as an evidence gap. Use public evidence, scope rules, citation checks and coverage limits for a bounded decision.

Use cases

What evidence would help you treat missing public feedback as an evidence gap?

An empty search result can mean no matching accessible material, not no users or no problems. Decide what a feedback brief can say when coverage is thin. Research the available source status and scope, keeping completed empty results separate from unavailable sources, partial pages and unsupported categories rather than turning missing observations into a confident positive or negative conclusion about product satisfaction, demand or the success of a recent campaign.

Example research prompt
Assess sparse feedback coverage by distinguishing completed empty results, unavailable sources and query exclusions, without treating missing public discussion as satisfaction or low demand.
01 / Use cases

Define the observation and counting unit

Define the question, time window and eligible public material. Include returned coverage information and exact inspected results. Exclude guessed posts or reconstructed prior outputs. Record whether a source completed, returned partial coverage or was unavailable, and preserve the distinction between a query with no allowed matches and a system that could not establish access or finish within its documented response behavior for the requested task and supported source context.

02 / Use cases

Trace the concrete task evidence

Inspect query specificity and inclusion rules for accidental exclusion. A narrow phrase may miss relevant task language, while a broad phrase may return unrelated material. Make one justified refinement at a time and keep its basis clear. Do not keep searching until a preferred conclusion appears, invent missing dates or infer private conversations from the absence of public statements that happen to match the wording originally supplied in the research prompt.

03 / Use cases

Challenge attribution and coverage

Compare available evidence with the conclusion the owner wants to draw. Silence cannot establish satisfaction, disinterest or the absence of a defect. If a category is unsupported, mark it unavailable instead of empty. Keep contextual badges from implying guaranteed coverage, and do not treat another agent client as a route around a missing source or authorization boundary that applies to the underlying service and the current workspace's documented limits regardless of interface.

04 / Use cases

Hand off a bounded interpretation

Return an evidence-gap statement with what was searched, what was inspectable and what remains unknown. Keep any authorized follow-up collection with the owner. Recommend a narrower question or consented research when needed, not a fabricated sentiment score. The output should make uncertainty usable without pretending that an empty or partial public result proves a market fact, a complete account population or the success of a campaign whose relevant audience behavior was not actually observed in the available sources.

Keep the boundaries clear.

  • For feedback silent coverage, reviewed public responses are not a representative customer sample.
  • The feedback silent coverage badges describe context, not guaranteed access or verified campaign reach.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-13. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage