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 · Operations overview
Example screen with sample data
Operations overview
Inspect authorized pipeline value, expected closing periods and operational exceptions.
OverviewWon Relationships×
B2C CRM · Operations overview
New
Won Relationships
Opportunities
| Record number | Subject | Counterparty | Owner | Organization | Won at | |
|---|---|---|---|---|---|---|
| OPP-20391 | Won opp-600 | ACC-140 | ORG-3183 | 04 Oct | ||
| OPP-75945 | Won opp-239 | ACC-150 | ORG-3328 | 14 Oct | ||
| OPP-94146 | Won opp-495 | ACC-130 | ORG-4656 | 20 Oct | ||
| OPP-70931 | Won opp-749 | ACC-110 | ORG-7692 | 20 Oct | ||
| OPP-81748 | Won opp-921 | ACC-150 | ORG-8988 | 22 Oct |
6 of 6 records
Won opp-600Opportunities · OPP-20391
CounterpartyACC-140
OrganizationORG-3183
Won at04 Oct
Expected value USD350
Revision250
What you can do
Bring the pipeline and its exceptions into the same review
Operations Overview helps the Sales Manager inspect relationship progress across authorized organizations. It shows open pipeline, weighted forecast, pending review decisions and failed operations, together with expected value by stage and an expected-close week distribution. A paged exception queue supports the follow-up conversation when an action needs attention.
The overview is useful when its totals lead back to an understandable relationship. An opportunity expected to close this week may still be waiting for review. A segment operation may need its result reconciled before the owner treats it as finished. The manager can use that context to decide which relationship or operational issue to examine first.
How the work is organized
- Pipeline expectation. Compare the recorded expected USD value across open stages. Inspect the assigned owner and expected close date when a relationship needs explanation. The weighted forecast uses the probability recorded against the opportunity.
- Review workload. Look at work awaiting a review decision and identify the owner who can supply any missing explanation. The Sales Manager should be able to connect a pending item with the relevant source revision and evidence.
- Execution follow-up. Inspect failed operations and items needing reconciliation. Open the receipt and source relationship to understand the discrepancy before deciding whether a correction or a fresh review is required.
What to agree during setup
Agree what owners mean by expected value and probability. Decide how to present missing probability values so a partially maintained opportunity does not quietly distort the forecast. Use the organization time zone consistently when grouping expected close dates into weeks, and rehearse a relationship near the week boundary.
Confirm each person’s authorized organizations before using the aggregate overview. A Sales Manager responsible for several organizations may need a wider picture than an owner working in a single operating team. App Administrator maintains the membership context; the team should test both the permitted overview and the underlying record access during setup.
Check the handoff on an actual case
Place the Rivera household opportunity in Proposal with an expected value of 1,000 USD and a probability of 60 percent. Its weighted contribution is 600 USD. The Sales Manager should be able to relate that contribution to the open opportunity and explain its expected close week from the recorded date.
Add another authorized relationship with an operation marked as needing review. Follow it from the overview’s exception queue to the receipt and inspect the discrepancy. Then sign in as an owner with a narrower organization scope and verify that the same operating review respects that access. Treat a Won outcome as a customer decision and use the connected financial system for booked revenue reporting.
What your team sees
- Operations Overview — Aggregate pipeline, review workload and execution health across the organizations the signed-in person is authorized to inspect.
- Open Pipeline — The open opportunities behind the stage and expected-value conversation.
- Operation Exceptions — Failed actions and reconciliation issues needing evidence-led follow-up.
Follow the work through
Use customer outcome review to verify a closing decision, and correction and reconciliation to resolve an operational exception.
What it keeps track of
Data model- 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.
- Operation receipts
- Stable operation keys and persisted results for every guarded action.
- Review decisions
- Independent reviewer decisions recorded against a specific source revision.
- Organizations
- Operating organizations that own accounts, opportunities and segment operations.
- Team members
- Authenticated platform identities with an active membership and role in an organization.
Who uses it
Permissions- Sales Manager
- , Relationship Owner, Auditor, App Administrator.
- The operating roles inspect authorized results; App Administrator maintains the organization and membership context that supports access.
Set up B2C CRM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.