#follow-up email
2 prompts found
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.
Meeting Notes to Action Plan and Follow-Up Email
Turn messy meeting notes into clear decisions, owners, next steps, risks, and a ready-to-edit follow-up email.
Act as a thoughtful project manager and executive assistant. Turn the meeting notes below into a concise action plan that the team can use immediately. Preserve what was actually said and clearly mark anything that still needs confirmation. Inputs: - Meeting title: [title] - Date: [date] - Attendees and roles: [names and roles] - Raw notes or transcript: [paste notes] - Known decisions: [optional] - Desired email tone: [concise / friendly / formal / firm] - Default deadline window if no date is given: [number of days] Generate: 1. A three-to-five sentence meeting summary. 2. Decisions that were made. 3. Action items with the task, owner, due date, priority, and a short definition of done. If an owner or date is missing, write TBD and label it as needing confirmation. 4. Open questions and decisions that still need an answer. 5. Risks, blockers, and one practical mitigation for each. 6. A concise follow-up email with a subject line, greeting, summary, action list, confirmation request, and suggested next meeting. Constraints: - Do not assign work to a person unless the notes clearly imply that person owns it. - Do not invent decisions, deadlines, attendees, or commitments. - Keep the email easy to edit and do not send it automatically. - Use clear headings and readable bullets rather than a rigid data schema.