1. Technology CRM
  2. Features
  3. Relationship activities
Feature · Relationship activities

Relationship activities

Keep calls, meetings, emails and tasks attached to the opportunity they move forward.

OverviewActivity Follow-up
Technology CRM · Relationship activities

Activity Follow-up

Relationship activities

New
ParentLine numberActivity typeDue atCompleted atOutcome
OPP-96428720Call07 OctOTC-867
OPP-84654260Meeting04 OctOTC-279
OPP-69536910Email15 OctOTC-408
OPP-9829650Task10 OctOTC-555
OPP-78725780Call14 OctOTC-961
6 of 6 records
OTC-867Relationship activities · RA-66082
Call
ParentOPP-96428
Line number720
Due at07 Oct
Revision840
Example screen with sample data

What you can do

Record the result of the customer discussion

A sales activity should explain what happened and what the team needs to do next. Relationship Owner records a Call, Meeting, Email or Task against the opportunity, with an outcome that gives the next person enough context to act. The activity retains its line number and revision so it can be followed alongside the opportunity’s history.

Due and completion dates help distinguish follow-up work from completed actions. Sales Manager uses the activity evidence when assessing qualification, proposal scope or a closing request. Logging an Email records the interaction; any connection that retrieves messages from a mailbox is agreed separately during implementation.

How the work is organized

  • A specific opportunity. Each activity belongs to the opportunity discussed. The parent reference keeps a customer meeting attached to the commercial case it supports, including when the same account has more than one opportunity.
  • A useful outcome. Relationship Owner describes the result of the call, meeting, email or task. An empty outcome cannot support a guarded activity action. Write the customer’s response and the next step clearly enough for Sales Manager to evaluate the evidence later.
  • Follow-up timing. A due date identifies when attention is needed, and a completion date records that the work concluded. The team reviews overdue follow-up alongside the expected opportunity closing date without treating either date as evidence of a successful sale.

What to agree during setup

Agree the difference between logging a completed discussion and creating follow-up work. Decide what an outcome should contain for each activity type and when a completion date is appropriate. Keep the wording useful to the next Relationship Owner or reviewer who opens the opportunity.

Also agree how activities support qualification and closure. A casual customer comment should not be mistaken for verified acceptance. Attach supporting files when the decision needs a document beyond the activity outcome. New activity actions are refused on closed opportunities, so establish the correction path for evidence that needs attention after Won or Lost has been recorded.

Check the handoff on an actual case

Use a customer evaluating a software platform. Relationship Owner records a Meeting with the outcome that the customer will test the agreed environment and return security questions. Add the follow-up Task with a due date and an outcome describing the requested action. When the discussion concludes, record the appropriate completion evidence.

Ask Sales Manager to explain which activity supports qualification and which item still needs follow-up. Try logging an activity with an empty outcome and confirm that it is refused. Repeat the exercise after a reviewed Lost outcome: the owner must use the agreed correction process rather than silently appending new sales work to a closed case. Auditor should still be able to follow the earlier activity sequence.

What your team sees

  • Activity Follow-up — Due activities without a completion date that need attention.
  • Relationship Activity Log — The recorded discussion and task outcomes for each opportunity.
  • My Open Opportunities — Open sales work whose next actions need an accountable owner.

Follow the work through

Use qualification and activity, then carry the relevant evidence into reviewed win or loss.

What it keeps track of

Data model
Relationship activities
Calls, meetings, emails and tasks logged against an opportunity.
Opportunities
Sales opportunities with lifecycle, expected value and expected close date.
Record attachments
Evidence files attached to an opportunity with visibility scope.
Operation receipts
Durable receipts for guarded operations with stable operation keys.

Who uses it

Permissions
Relationship Owner
, Sales Manager, Auditor.
Relationship Owner
Records the work; Sales Manager examines its meaning when making an independent decision.

Set up Technology CRM your way.

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

How to get started