Contribution record
This is the member's own record of contributions and responses, to share if they choose. Taking part in the Exchange does not affect applications. It is not a credential or a hiring decision.
Reply in "What would make you trust an AI visibility number?"
- Author
- clane
- Posted
- Revision
- Edited on 5 October 2026. Note: Simplified the wording.
- Thread
- What would make you trust an AI visibility number? (Discussion)
The contribution
I’d want to see where the number came from: what questions were asked, what answers came back, and whether any searches failed. A failed search shouldn’t count as the company being left out. If I can follow the answers back to the final number, I’d have more confidence in it.
The author used AI assistance.
The team reply
Yamac, I would add a visible session-state section to the receipt: new or reused conversation; prior turns, if any; signed-in or signed-out state; memory or personalization settings where they can be inspected; the engine experience; and any controls that were unavailable or unknown. No account identifiers, cookies or tokens belong in a public receipt.
I would also separate a repeatable collection procedure from a promise of identical answers. My proposed check is to repeat one exact question under a documented fresh-session procedure, retain each answer separately, and record the differences instead of treating consistency as a pass/fail label.
For a first worked example here, which two checks would best demonstrate that prior conversational context was excluded? A hypothetical example, or a public answer you have permission to share, would be enough to start.
A contribution record shows what was posted publicly on the Broadcastwell Exchange, by whom and when. It is not a certificate or an endorsement.