Methodology
What Customer-Verified guarantees
Step 01 · Session start
The customer wrote it.
Before the customer answers the first question, they see a clear disclosure of how their words will be used. They agree to participate by accepting the consent terms. Anonymous participation is available throughout the session if the customer prefers not to be attributed.
The session-start consent is the first architectural moment in the verification chain. It captures the customer’s understanding that their responses may become a deployable asset, names the company that will be using the proof, and confirms their willingness to proceed. The consent record stores the customer’s identifier, timestamp, and the terms version they agreed to. If the customer chooses anonymous participation, their identity is captured in the consent record but excluded from any deployable asset.
Step 02 · Proof confirmation
The customer confirmed it.
During the session, ProofBridge analyses each response and generates targeted follow-up questions when more depth is useful. The customer is in the session throughout, answering and refining their own words. This is not passive content generation. It is guided capture with the customer as the source.
The proof confirmation layer happens continuously through the session. As the customer responds to questions, AI follow-up questions extract depth when answers lack specifics (numbers, timelines, comparisons). The customer responds to follow-ups in their own words. At any point, the customer can end the session, modify previous answers, or choose anonymous participation. The session does not generate any deployable asset until the customer reaches the final submission step.
Step 03 · Final submission
The customer chose its use.
At the end of the session, ProofBridge generates a Customer Story and a Proof Moment from the full session. The customer reviews both, edits anything they want changed, selects their consent state (approved_external or internal_only), and submits. The badge applies only after this final confirmation.
Final submission is the only moment a Customer-Verified asset is created. The customer reviews the structured outputs, can make any edits they want, and explicitly chooses how the asset can be used. If the customer does not submit, no asset exists. If the customer chooses internal_only, the asset is created but the architecture prevents external deployment. If the customer chooses approved_external, the asset becomes available for deployment in customer-facing surfaces. The consent record at this step includes the final asset content, the consent state, the timestamp, and the customer’s identifier (or anonymous marker).
The verification process
Step 01 · Session start
Session-start consent
Before the customer answers the first question, they see a clear disclosure of how their words will be used. They agree to participate by accepting the consent terms. Anonymous participation is available throughout the session if the customer prefers not to be attributed.
The session-start consent is the first architectural moment in the verification chain. It captures the customer’s understanding that their responses may become a deployable asset, names the company that will be using the proof, and confirms their willingness to proceed. The consent record stores the customer’s identifier, timestamp, and the terms version they agreed to. If the customer chooses anonymous participation, their identity is captured in the consent record but excluded from any deployable asset.
Step 02 · Proof confirmation
Proof confirmation
During the session, ProofBridge analyses each response and generates targeted follow-up questions when more depth is useful. The customer is in the session throughout, answering and refining their own words. This is not passive content generation. It is guided capture with the customer as the source.
The proof confirmation layer happens continuously through the session. As the customer responds to questions, AI follow-up questions extract depth when answers lack specifics (numbers, timelines, comparisons). The customer responds to follow-ups in their own words. At any point, the customer can end the session, modify previous answers, or choose anonymous participation. The session does not generate any deployable asset until the customer reaches the final submission step.
Step 03 · Final submission
Final submission consent
At the end of the session, ProofBridge generates a Customer Story and a Proof Moment from the full session. The customer reviews both, edits anything they want changed, selects their consent state (approved_external or internal_only), and submits. The badge applies only after this final confirmation.
Final submission is the only moment a Customer-Verified asset is created. The customer reviews the structured outputs, can make any edits they want, and explicitly chooses how the asset can be used. If the customer does not submit, no asset exists. If the customer chooses internal_only, the asset is created but the architecture prevents external deployment. If the customer chooses approved_external, the asset becomes available for deployment in customer-facing surfaces. The consent record at this step includes the final asset content, the consent state, the timestamp, and the customer’s identifier (or anonymous marker).
Honest disclosure
Objective truth of customer claims.
The badge guarantees the customer made and confirmed the claim. It does not independently verify whether revenue figures, outcomes, or comparisons stated are objectively accurate.
Company endorsement of every story.
The customer wrote and confirmed the asset.
The consent record is documented.
Every Customer-Verified asset has a consent record traceable to a specific session, with timestamps, consent state, and the final confirmed asset content.
The consent state is enforced architecturally.
Procurement and compliance
Asset-specific verification
Built for your team
ProofBridge works differently for every team.
Product
Learn
Compare
© 2026 ProofBridge. All Rights Reserved.
Free Tools
Legal