name	draft-outreach
description	Draft verified outreach; never send or use sensitive data.
metadata	{"short-description":"Draft relevant, evidence-grounded outreach"}

Draft Outreach

A concise outreach draft with a credible reason for contact and a low-friction next step.

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.

Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
Retrieve the minimum authorized evidence needed from the following inputs: Recipient identity, relationship and consent context, account facts, relevant trigger, value hypothesis, approved claims, channel, tone, and desired action.
Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.

Verify recipient and organization matches; do not silently choose among ambiguous people.
Use only relevant, attributable personalization and avoid sensitive, intrusive, or stale details.
Connect one evidence-backed trigger to one plausible business value and one clear call to action.
Respect the user's tone, channel length, local rules, suppression status, and communication preferences when available.

Draft only. Sending or enrolling the recipient in a sequence requires separate explicit approval.

draft-outreach