Activities and proposals

Relationship Owner records calls, meetings, emails and tasks against the opportunity. The activity outcome explains what happened, while due and completion dates provide context for follow-up. A useful record lets the next person understand the customer discussion without asking the owner to reconstruct it from memory.

Proposal submission uses the proposed scope and a next relationship activity. The submission action checks the assigned opportunity, organization and revision before recording its outcome in the activity history. That gives the team a way to follow the proposal discussion without treating submission as a successful sale.

• Interaction history. Each activity belongs to the opportunity it concerns. Its line number and revision help the team follow the sequence of customer work. Record an outcome that explains the result of the interaction and why a further action is needed.
• Proposal scope. Relationship Owner prepares the customer scope and supporting evidence before submitting the proposal. Keep the next activity clear enough that the team knows what response or discussion it is waiting for.
• Follow-through. Due activities bring unfinished customer work into the next review. A promised follow-up that requires independent review has its own commitment record, while the general activity history retains the broader conversation.

Agree what the team records as a Call, Meeting, Email or Task and when a completion date is appropriate. Decide how proposal scope will be retained with the opportunity, including the supporting files and a useful submission outcome. A proposal with no next activity leaves the customer discussion without a clear continuation.

Keep email logging and message delivery responsibilities clear. If the team needs mailbox synchronization or document sending, configure the relevant connection during implementation. Agree what evidence the CRM should retain from that system. Do not assume that recording an Email or submitting proposal scope proves that an external message reached the customer.

Use an opportunity for a customer requesting a service package. Relationship Owner records the discovery meeting and attaches the scope document. Prepare the proposal submission with a follow-up call as the next activity, including an appropriate due date and an outcome explaining the planned discussion.

Submit the current revision and ask Sales Manager to find the scope, next activity and operation result. Attempt another submission without the required next activity and confirm that it cannot proceed. Repeat the original request to check that the existing result is retained without duplicate effects. When the customer asks for a revised document, record the changed discussion and prepare the relevant current revision before taking the next action.

• Due Activities — Activities whose due date has arrived and whose completion date is still empty.
• Activity History — Calls, meetings, emails and tasks with their recorded outcomes.
• Proposal Follow-through — Opportunities in Proposal or Negotiation that need the next customer action.

Use qualification and proposal and promised follow-up review for a customer promise requiring a decision.