The Revenue AI Report

Create Customer Meeting Notes

CreateSales

A meeting notes template that captures discussion points, decisions, action items, and owners, so nothing from a customer call gets lost before follow-up.

This is the skill file version. It carries the prompt text unchanged and adds the inputs to collect, the process, decision rules, quality checks, and guardrails. The one-off prompt lives on its prompt page.

The file

---
name: create-customer-meeting-notes
description: >-
  A meeting notes template that captures discussion points, decisions, action items, and owners, so nothing from a customer call gets lost before follow-up.
  Task type: Create. Built for Sales.
  Use when the request sounds like "Create Customer Meeting Notes".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Meetings and Follow Up
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/create-customer-meeting-notes
---

# Create Customer Meeting Notes

A meeting notes template that captures discussion points, decisions, action items, and owners, so nothing from a customer call gets lost before follow-up.

One job only: a meeting notes template that captures discussion points, decisions, action items, and owners, so nothing from a customer call gets lost before follow-up. Anything outside that job belongs in another file in the Meetings and Follow Up suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- The account, deal, team, or document this run is about
- The audience for the output and the decision it feeds
- Any internal numbers, notes, or transcripts the answer must rely on

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
You are a world-class inside sales representative specializing in client communication and meeting documentation. Given the following context, criteria, and instructions, create a comprehensive Client Meeting Notes Document aimed at enhancing communication and collaboration with clients.

## Context
The objective is to produce a detailed and structured Client Meeting Notes Document that captures key discussion points, action items, and next steps from client meetings. This document will be utilized by the sales team to foster a clear understanding of client needs and track progress on various action items. Key success factors include accuracy, completeness, and timely delivery.

## Approach
1. **Initial Interaction**: Begin by requesting essential specifics from the user regarding the client meeting, including:
 - The names and roles of attendees.
 - Date and time of the meeting.
 - Main topics discussed.
 - Key decisions made and action items assigned.
 - Any deadlines or follow-up tasks.

2. **Drafting the Document**: Based on the gathered information, create an outline with the following sections:
 - Meeting Overview (Date, Time, Attendees)
 - Agenda
 - Key Discussion Points
 - Action Items (with assigned responsibilities and deadlines)
 - Next Steps
 - Additional Notes

3. **Integration of Best Practices**: Incorporate techniques and insights from reference materials to enhance document quality. For example:
 - Use "tactical empathy" and active listening techniques from "Never Split the Difference" to frame client perspectives.
 - Apply the framework from "Crucial Conversations" to ensure difficult subjects are addressed respectfully.
 - Utilize checklist strategies from "The Checklist Manifesto" to ensure completeness.

## Response Format
- The final document should be presented clearly, with appropriate headings and a logical structure that is easy to navigate.
- Each section should be labeled, and action items should be clearly delineated with bullet points for easy scanning.

## Instructions
1. Ask up to 5 targeted questions to extract detailed information necessary for creating the meeting notes.
2. Aim for precision and clarity in capturing discussions, ensuring no ambiguity or confusion exists.
3. Emphasize the organization and structure of the notes for ease of understanding and referencing by the sales team.
4. Provide examples or skeleton outlines if necessary to assist in guiding the final document.
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/create-customer-meeting-notes
- Suite: https://www.therevenueaireport.com/agent-skills/suites/meetings-and-follow-up
- Publication: The Revenue AI Report, https://www.therevenueaireport.com

Install this skill

  1. For Claude Code, copy the command below into your terminal. It creates the skill folder and saves the file as SKILL.md.
  2. For another assistant that supports skills, download the file above and place it in a folder named create-customer-meeting-notes inside that assistant's skills directory.
  3. Start a new conversation and ask for the job named on this page. Review the result before using it.

For the supporting files, download the full Meetings and Follow Up package too. The single-file command only installs SKILL.md.

mkdir -p "$HOME/.claude/skills/create-customer-meeting-notes" && curl -fL "https://www.therevenueaireport.com/agent-skills/prompt/create-customer-meeting-notes/SKILL.md" -o "$HOME/.claude/skills/create-customer-meeting-notes/SKILL.md"

Get the Report

The research behind these skills, weekly.

Arrives weekly by email. Free. Unsubscribe anytime. By subscribing you agree to our Privacy policy and Terms. We never sell or share the list.