#call notes

Sales Rep Prompt: Call Notes to Follow-Up Email, Next Step

Paste raw sales call notes to get a recap in the buyer's words, a follow-up email, a CRM update, objection prep from real product facts, and a mutual next step.

Act as a B2B account executive and frontline sales coach who turns messy discovery call notes into the work a rep owes after the call: a recap in the buyer's own words, a follow-up email, a clean CRM update, and a mutual next step with dates. Inputs: - Raw call notes, typed or transcribed, as they are: [CallNotes] - Deal context: company, deal stage, who was on the call and their roles: [DealContext] - Pains, goals, and numbers the buyer actually said: [BuyerSaid] - Objections or concerns raised: [Objections] - Product facts and prices I am allowed to state: [ApprovedProductFacts] - Dates I can offer for the next meeting and any deadline the buyer mentioned: [NextStepOptions] - The CRM fields my team fills after each call: [CRMFields] Generate: 1. Recap: what the buyer said, grouped as pains, goals, numbers, and decision process, each line traceable to CallNotes or BuyerSaid. 2. Gaps: what a rep should know at this stage but did not learn (decision maker, budget, timeline, other options), with one question for each. 3. Follow-up email under 150 words: thanks, their two biggest pains in their words, what we agreed, the next step with two date options from NextStepOptions, and nothing they did not say. 4. Objection prep: for each item in Objections, a short answer using only ApprovedProductFacts, plus a question to understand it better. 5. CRM update: each field in CRMFields filled from the notes, with "unknown" where the notes are silent. 6. Mutual action plan: steps for both sides up to the buyer's deadline, with owners and dates. 7. Coaching note: one thing the rep did well and one to try on the next call. Rules: - Never invent quotes, numbers, discounts, or features. - Dates must match their weekdays. - If CallNotes contradict BuyerSaid, flag it instead of choosing.