Coordinate customer follow-up
Coordinate customer follow-up.
2 stages · 0 approvals
Roles and responsibilities
-
Step 1Coordinate activity
Activity NumberSubjectOwnerStart Time
-
Step 2Develop opportunity
Opportunity NumberNameStageAmount
Process steps
Follow the process from start to finish. Select a step to see who acts and what changes.
Coordinate activity
Keep meetings with EndTime after StartTime and tasks with explicit due dates. Sync only the authorized mailbox from its configured boundary, deduplicating provider messages. Match messages to accessible contacts and activities; unmatched private mail stays private. A message receipt does not mark a task complete or imply consent.
Develop opportunity
Advance an open opportunity through permitted stages with an expected revision. Record each transition in StageChanges. Use contacts from the accessible account and maintain one primary buying contact. Amount is the sum of product lines in the opportunity currency; a stage change preserves its history.
0 approvals required in this process
- Record ownershipKeep every reference and attachment in the authorized workspace and the acting person’s permitted scope. A copied link cannot grant access to another customer’s record.
- Current decisionsReview the latest saved state before changing work. If someone changes protected facts after approval, send the revised record through its required review again.
- Repeated actionsA retry returns the original result when the same action has already been accepted. Keep an uncertain external outcome visible until its original request is reconciled.
- CorrectionsRetain the earlier decision and the reason for correcting it. A report or automation should not hide a reversal by deleting the original evidence.
Follow the outcome
The receiving team needs the current owner, the next action and a traceable result. Use the linked operating records when investigating a delay rather than treating a status label as the complete explanation. If a required person is unavailable, route the decision through an authorized replacement who remains independent of its preparer. Resolve missing evidence before closing the handoff. A locally completed action may still require a confirmed response from its configured destination.
Deal stages. A rep moves an own open deal and sees the dated history. Reject a cross-team move or stale Revision.
Renewals. A renewal appears without changing its original closed deal. Repeating the scheduling command creates no duplicate renewal.
Activity logging. An owned meeting appears at its actual time and completion is explicit. Reject a reversed time interval or attaching another team private note.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Coordinate activity | ActivitiesMessageLinksMailboxConnections | Retain the stated outcome and its source evidence |
| 2 Develop opportunity | OpportunitiesOpportunityProductsOpportunityContactsStageChanges | Retain the stated outcome and its source evidence |
Process reports
All reportsPipeline Summary
Open amount and weighted amount by stage, owner and territory, separated by currency.
Win and Loss
Closed outcomes with loss reasons, source and dated stage history.
Activity Performance
Completed calls, meetings and tasks by permitted owner and reporting period.
Renewal Outlook
Upcoming renewal occurrences with their original deal, owner and expected amount.
Sales Cycle
Elapsed time between recorded stage changes and closing outcomes.
Agent support
An agent acts within the current user or service scope. It cannot provide its own independent human approval, restore a withdrawn contact purpose or turn an unknown external response into a confirmed result.