These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
Feature · Review and evidence
Example screen with sample data
Review and evidence
Keep the reviewer decision tied to the source revision and the evidence considered.
OverviewSegment Submission Inbox×
B2C CRM · Review and evidence
New
Segment Submission Inbox
Approval conditions
| Id | Segment name | Parent | Organization | Revision | Consent basis | |
|---|---|---|---|---|---|---|
| IDD-995 | Segment 793 | OPP-52190 | ORG-8502 | 570 | CB-617 | |
| IDD-870 | Segment 446 | OPP-18624 | ORG-8289 | 390 | CB-275 | |
| IDD-871 | Segment 129 | OPP-56415 | ORG-5923 | 480 | CB-355 | |
| IDD-989 | Segment 720 | OPP-74102 | ORG-8226 | 350 | CB-833 | |
| IDD-509 | Segment 267 | OPP-54162 | ORG-7619 | 550 | CB-834 |
6 of 6 records
IDD-995Customer segments · CS-52070
SubmittedSegment nameSegment 793
ParentOPP-52190
OrganizationORG-8502
Revision570
Consent basisCB-617
What you can do
Give the reviewer a definite decision to make
The Sales Manager reviews eligible relationship and segment work independently of its preparer. The decision records the source revision, reviewer, time, reason and operation key against the opportunity. Approve, Reject and Return distinguish the recorded response while preserving the explanation the Relationship Owner needs for the next step.
Evidence files remain attached to the opportunity with a title, evidence type, uploader and visibility scope. The reviewer can examine that material alongside the activity history and prepared request. This gives the team a traceable basis for proposal advancement, segment approval or the final customer outcome.
How the work is organized
- Submitted scope. Identify the exact revision under review and the decision being requested. The Relationship Owner prepares the relevant evidence before the Sales Manager acts, so the reviewer can assess a definite version of the work.
- Decision record. Capture the reason with the review response. A rejection or return should explain the issue the owner needs to address, while an approval should remain associated with the evidence that supported it.
- File visibility. Use Internal and Shared visibility deliberately when attaching evidence. Agree the access policy for each scope during setup and verify it with the intended readers before the team relies on attachments for review.
What to agree during setup
Choose what qualifies someone to review each kind of decision, and confirm how independence from the preparer is checked. Agree how review coverage works when the usual Sales Manager is unavailable. Use separate accounts for preparation and review during rehearsal so the handoff reflects the real operating responsibilities.
Define useful evidence types and file titles. A customer acceptance file, a segment evaluation and a proposal scope should be distinguishable when someone opens the opportunity later. Agree retention and access procedures with the people who own that information, and test visibility through the same signed-in roles that will use it day to day.
Check the handoff on an actual case
The Relationship Owner prepares the Rivera household proposal and attaches the supporting scope. The Sales Manager reviews the submitted revision and records a decision with a reason. The Relationship Owner then follows that decision into the eligible next action, and Auditor traces the evidence without changing it.
Repeat the rehearsal while the owner changes the proposal after the review begins. The approval must remain tied to the version actually assessed, and the changed submission needs the current decision path. Also return a segment evaluation for clarification and check that the reason remains readable. The team should be able to explain what was reviewed, who decided and which evidence supported that decision.
What your team sees
- Segment Submission Inbox — Prepared segment revisions awaiting an independent review decision.
- Review Decision History — Review responses with the source revision, reviewer and reason.
- Internal Evidence — Opportunity attachments marked Internal for the agreed access policy.
Follow the work through
Use proposal review, segment review and customer outcome review for the corresponding decision rehearsals.
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions recorded against a specific source revision.
- Record attachments
- Uploaded evidence files linked to an opportunity with visibility scope.
- Opportunities
- Relationship opportunities with lifecycle, expected value and guarded revision control.
- Customer segments
- Opted-in audience segment refreshes prepared, reviewed and executed for an opportunity.
- Relationship activities
- Calls, meetings, emails and tasks logged against an opportunity.
- Team members
- Authenticated platform identities with an active membership and role in an organization.
- Operation receipts
- Stable operation keys and persisted results for every guarded action.
Who uses it
Permissions- Sales Manager
- , Relationship Owner, Auditor.
- The Sales Manager makes the independent decision, the Relationship Owner prepares its evidence, and Auditor examines the authorized record of the handoff.
Set up B2C CRM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.