Call prep: [person] — [company]

Purpose

Build a concise call brief from dated person, account, deal, task, and interaction evidence. Keep sourced context separate from suggested questions and unknowns.

Usage

• /call-prep [person]
• /call-prep [company]

Evidence, authority, and recovery

Set the call brief's as-of timestamp, timezone, participant, and call time. Make freshness relative to that as-of time. For each interaction, commitment, signal, account field, objective, and objection, record its source path or record ID and event date. File modified time is not an event date.

• Treat an unknown objective and unknown objection as unknown. Write Unknown — ask; do not infer intent, buying stage, sentiment, priority, or likely objection from role, company, silence, or a generic sales pattern.
• Separate sourced facts, the user's stated goals, hypotheses, and suggested questions. A useful question is not evidence that its premise is true.
• Show contradictory sources and dates side by side. Do not silently choose one.
• Never invent facts, quotes, commitments, dates, outcomes, customer counts, product capabilities, prices, ROI, payback, rollout time, or integration claims.
• Keep call prep read-only by default. A recommendation is not permission to update a person, account, deal, or task.
• Preview any requested change, require explicit confirmation from the authorized human, then read back the saved record. If a write or read-back fails, report possible partial state and stop before retrying.

Method

1. Resolve identity and call scope

Confirm the exact person/account and disambiguate duplicate names. Confirm:

• scheduled call time and timezone;