update-opportunity

name	update-opportunity
description	Propose evidenced deal updates; not broad cleanup.
metadata	{"short-description":"Propose and apply evidence-backed deal updates"}

Update Opportunity

Outcome

A precise, auditable field-level update proposal grounded in recent customer or seller evidence.

CRM-neutral operating contract

• Discover available CRM, communication, calendar, knowledge, and file capabilities before choosing a retrieval plan. If no live CRM is available, use user-supplied exports when that still satisfies the request; never imply a live write is possible.
• Map records by meaning, not vendor labels: organization, person, lead, opportunity, activity, product, service record, user or team, and knowledge item. Inspect schemas and custom fields, preserve native IDs, stages, currencies, timezones, and fiscal periods.
• Keep observed facts, derived conclusions, and missing information distinct. Anchor consequential claims to record IDs, fields, timestamps, or named sources, and state access or freshness limits.
• Start read-only. Before creating, updating, assigning, sending, or scheduling, show the exact proposed action and obtain confirmation unless the current request already authorized that exact mutation.
• Obey connected-system permissions, resolve ambiguous records or people instead of guessing, check for duplicates before creation, and report partial failures without repeated retries.

Workflow

1. Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
2. Retrieve the minimum authorized evidence needed from the following inputs: Target opportunity, current field values, new call notes, transcript, email, document, or user instruction, plus schema and validation rules.
3. Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
4. Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
5. Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.

Analysis rules

1. Resolve the exact opportunity and retrieve current values immediately before proposing changes.
2. Map evidence to semantic fields; preserve configured stages, currencies, picklists, and required fields.
3. Show old value, proposed value, evidence, confidence, and any downstream consequence for every field.
4. Do not infer a stage, close date, amount, probability, or forecast category from weak or conflicting evidence.

Required output

• Target record
• Field-level diff
• Evidence and unresolved conflicts
• Optional task or note proposals
• Write result after approval

Actions and boundaries

Ask for confirmation on the complete diff, then update once, report exact successes and failures, and do not retry failed writes more than once.