1. CRM with Call Tracking
  2. Features
  3. Completion and Reconciliation
Feature · Completion and Reconciliation

Completion and Reconciliation

Check the retained action outcome before retrying work or making a correction to completed scope.

OverviewReceipt Reconciliation
CRM with Call Tracking · Completion and Reconciliation

Receipt Reconciliation

Operation receipts

New
IdParentOperation keyActionExpected revisionResult state
IDD-762OPP-65736OK-650ACT-855640Pending
IDD-247OPP-90495OK-331ACT-101780Failed
IDD-937OPP-22456OK-886ACT-722450Needs review
IDD-139OPP-11484OK-338ACT-252490Pending
IDD-414OPP-43671OK-755ACT-449760Failed
6 of 6 records
IDD-762Operation receipts · OR-65075
Pending
ParentOPP-65736
Operation keyOK-650
ActionACT-855
Expected revision640
Occurred at03 Oct
Example screen with sample data

What you can do

Follow an action to its recorded result

A call attachment is complete when the approved action has retained its receipt and the session is marked Completed. The receipt identifies the action, expected version and resulting state. Sales Manager can use that record to investigate work that remains Pending, has Failed or needs further review.

Reconciliation starts by reading the existing result and linked evidence. Where an authoritative external reference is configured, the review compares it with the intended scope. A matching result can be recorded as Completed. A discrepancy stays at Needs review with a specific explanation so the team knows what remains unresolved.

How the work is organized

  • Completion evidence. The receipt stays linked to its opportunity and action. Check the referenced effects before deciding that a screen message or repeated request represents a new piece of work.
  • Exception review. Pending and Failed results need investigation against the existing evidence. If the scope or outcome differs from what was expected, record the discrepancy and leave the item for review.
  • Authorized correction. Unexecuted scope can be cancelled through its responsible path. Already executed scope needs a reviewed corrective action that preserves the original identity and result rather than silently replacing the history.

What to agree during setup

Agree who investigates incomplete actions and which external source is authoritative when a provider reference is present. Set a clear handoff between Relationship Owner and Sales Manager when the owner cannot establish whether an action finished. The next person should receive the opportunity, action and discrepancy, not just a request to try again.

Define the correction process before the first live call attachment. Keep the original completion and its review evidence available when a correction is required. Agree how to distinguish an unexecuted request from work that already took effect. A retry should follow reconciliation of the existing outcome so the team does not duplicate a completed call.

Check the handoff on an actual case

Relationship Owner submits an approved call for completion but does not receive a clear confirmation. Sales Manager opens the existing receipt and checks the linked result before another execution is attempted. If the expected effect is already present and agrees with the reviewed scope, reconciliation can establish completion without creating another attachment.

Repeat the exercise with an external reference that identifies a different call. The discrepancy must remain visible for review instead of being marked Completed simply because a provider record exists. The explanation should identify the mismatched scope so the owner can resolve the right problem.

Finally, ask for a correction after a valid call has completed. Review the existing activity, decision and receipt evidence, then prepare the authorized corrective action. Preserve the opportunity’s expected value and customer outcome throughout: correcting a call attachment does not create a sale, invoice or payment.

What your team sees

  • Receipt Reconciliation — Pending, failed and review-needed outcomes show the recorded action and discrepancy.
  • Completed Call History — Completed sessions provide the call identity for the result check.
  • Decision History — The reviewer can confirm which decision authorized the action being investigated.

What it keeps track of

Data model
Operation receipts
Idempotent receipts for guarded operations, with stable operation keys and result state.
Opportunities
Revenue opportunities with lifecycle, expected value and expected close date.
Call sessions
Call sessions that attach a completed call to a relationship, with provider identity and consent.
Relationship activities
Line-level activity history attached to exactly one opportunity parent.
Review decisions
Independent reviewer decisions recorded against a frozen source revision.

Who uses it

Permissions
Sales Manager
Reconciles outcomes and reviews corrections.
Relationship Owner
Provides the action context and executes eligible reviewed work.
Auditor
Follows the retained evidence.

Set up CRM with Call Tracking your way.

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

How to get started