1. E-commerce CRM
  2. Features
  3. Decisions and Evidence
Feature · Decisions and Evidence

Decisions and Evidence

Keep retention review reasons, supporting references and operation results connected to the customer opportunity.

OverviewDecision History
E-commerce CRM · Decisions and Evidence

Decision History

Review decisions

New
Parent opportunityRetention follow upSource revisionDecisionReviewerIndependent
OPP-76444RFU-7508210Approve
OPP-72258RFU-3559140Return
OPP-70673RFU-9514250Approve
OPP-55987RFU-2626210Return
OPP-51127RFU-1865580Approve
6 of 6 records
Approve rd-592Review decisions · RD-84516
Approve
Parent opportunityOPP-76444
Retention follow upRFU-7508
Source revision210
Independent✓
Decided at06 Oct
Example screen with sample data

What you can do

Explain the decision behind the recorded work

A review decision identifies the opportunity, reviewer and source revision considered. When it concerns retention work, the decision also links to the follow-up plan. Approve, Reject and Return record different conclusions, with a reason that helps the preparer understand the next step.

Operation receipts retain the type of action and its recorded result. Qualification, proposal submission and closing produce receipts that the Account Manager can inspect alongside the opportunity activity. Supporting evidence records can hold a reference link, captured date and notes, identified as a Photo, Document, Signature, Receipt or Note.

How the work is organized

  • Keep decisions identifiable. The Retention Reviewer links the decision to the intended follow-up and reviewed revision. Record the reason so another authorized team member can understand whether the plan was approved, rejected or returned for correction.
  • Read the operation in context. Inspect the operation type, recorded date, actor and evidence summary before interpreting its status. A successful proposal operation describes that action’s result; it does not by itself confirm external email delivery.
  • Preserve supporting references. Give evidence a useful title and kind, then link it to the opportunity or retention follow-up it explains. Keep the referenced material accessible under the team’s agreed access rules.

What to agree during setup

Agree how the reviewer records an independent decision and how the source revision is interpreted for retention work. Decide who investigates Pending, Failed or Needs Review receipts and who supplies any missing customer evidence. Keep the original action identity available when discussing a result across team handovers.

Choose where supporting documents and other evidence are stored. The reference record points to that material and retains notes; access to the destination needs its own deliberate setup. A Signature kind can identify signature-related evidence, but the actual signing process should be handled through the service the customer chooses.

Check the handoff on an actual case

Take a retention plan returned for correction and compare the review decision with the submitted revision. The Retention Specialist clarifies the purpose and the reviewer records the decision on the current plan. Locate the supporting document through its evidence reference and confirm that the authorized reviewer can open it.

Inspect a proposal operation marked Failed or Needs Review during the rehearsal. Compare its evidence summary with the opportunity and activity history before deciding what follow-up is required. Then have the Auditor explain the final record without changing it. The customer relationship should remain understandable even when an external communication result still requires confirmation through the chosen email process.

What your team sees

  • Operation Exceptions — Unresolved action results with their operation type and evidence summary.
  • Decision History — Review reasons linked to the opportunity, follow-up and source revision.
  • Retention Review Inbox — Plans awaiting a decision that will become part of the retained history.

Follow the work through

Follow evidence and exception review and retention review and contact to keep the recorded result connected to its customer purpose.

What it keeps track of

Data model
Review decisions
A record is a reviewer's call on a deal, used to log approvals, rejections, and the reasoning behind them.
Operation receipts
A record is proof a fulfillment step happened, used to confirm work on a deal was completed.
Record attachments
A record is a file or link kept with a deal, used to preserve supporting evidence for later reference.
Retention follow ups
Scheduled retention follow-up records: owner, contact date, quantity, reference number and review lifecycle.
Opportunities
A record is a deal in progress, used to track its value, stage, and chance of closing.

Who uses it

Permissions
Retention Reviewer
, Account Manager, Retention Specialist, Auditor, Admin.
Retention Reviewer
Records independent decisions, operational owners investigate their work, and Auditor reads the authorized evidence.

Set up E-commerce CRM your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started