Sales reps spend an average of 21% of their day writing CRM notes — time that should go toward selling. AI can write those notes for you, automatically, in the format your CRM expects. Here is exactly how to build that workflow, from the core prompt to a fully automated Make.com pipeline.
The real value is not just speed. It is consistency. When every call note follows the same structure, managers can review deals faster, handoffs get cleaner, and your future self is no longer stuck decoding vague notes written at the end of a long day.
Bad CRM notes create silent revenue leaks. When a deal changes hands, when you come back to a prospect six months later, or when your manager reviews a pipeline, the notes are the only record of what actually happened. Vague entries like "had a call, following up" give future-you nothing to work with. AI-generated notes, properly prompted, capture pain points, next steps, objections, and buying signals in a consistent structure every single time.
The cost of inconsistency compounds over time. A sales team with poor CRM discipline loses deal context on handoffs, can't run accurate pipeline forecasts, and spends more time in catch-up calls that should never be necessary. Fixing note quality is one of the highest-ROI operational changes a sales team can make — and AI makes it nearly effortless. For more on how AI fits into the full sales workflow, see our guide on AI tools for sales teams.
There is also a leadership benefit here: once notes are reliably structured, you can spot patterns across the pipeline much more easily. Objections repeat. Buying signals repeat. Missing information repeats. Those patterns are hard to see when every rep writes notes differently.
Start with this prompt after every sales call. Paste your rough transcript or bullet-point notes into the input:
You are a CRM note writer for a B2B sales team. Based on the call notes below, produce a structured CRM entry with these exact sections: **Contact:** [Name, Title, Company] **Call Date:** [Date] **Summary:** 2–3 sentences on what was discussed **Pain Points:** Bullet list of problems the prospect mentioned **Objections:** Any concerns or blockers raised **Next Steps:** Specific follow-up actions with owners and deadlines **Deal Stage:** [Discovery / Qualification / Proposal / Negotiation / Closed] **Sentiment:** [Hot / Warm / Cold] — with one sentence of reasoning Call notes: [PASTE YOUR NOTES HERE]
This structure works in HubSpot, Salesforce, Pipedrive, or any CRM that accepts free-text notes. The consistent formatting means you can later search or filter by sentiment, stage, or pain point across your entire pipeline.
If your team already has a qualification framework like MEDDIC, BANT, or SPICED, work that directly into the prompt instead of layering it on afterward. The closer the AI output is to the fields your managers actually care about, the more likely the workflow is to stick.
Manual copy-paste is still work. The real win is wiring this into an automated pipeline. With Make.com, you can build a flow that triggers on a completed call, sends the transcript to an AI model, and writes the formatted note directly to your CRM — zero human steps required.
Here is the basic scenario structure in Make.com:
Trigger: Calendly / Google Meet / Zoom "call ended" webhook ↓ Step 1: Fetch transcript (Fireflies.ai or Otter.ai API) ↓ Step 2: OpenAI / Claude — run the CRM note prompt with transcript as input ↓ Step 3: Parse AI response into structured fields ↓ Step 4: HubSpot / Salesforce — create or update deal note ↓ Step 5: Slack — post summary to #sales-updates channel
Setup time is roughly 2–3 hours the first time. After that, every call gets a CRM note within 90 seconds of hanging up. If you are new to Make.com automation, start with our step-by-step guide to building Make.com workflows before tackling this scenario.
Start small if needed. Even a semi-automated version — transcript comes in, AI formats the note, rep pastes it into the CRM — is a huge improvement over writing from scratch. Full automation is the goal, but partial automation still buys back real selling time immediately.
Different scenarios need different prompts. Here are three variations worth keeping in your toolkit:
For discovery calls — focus on MEDDIC qualification:
Extract MEDDIC criteria from these call notes. For each field, write "Unknown" if it wasn't discussed. Be concise. Metrics: [quantifiable impact prospect mentioned] Economic Buyer: [who controls budget] Decision Criteria: [how they'll evaluate vendors] Decision Process: [internal steps to buy] Identify Pain: [core business problem] Champion: [internal advocate, if identified] Notes: [PASTE]
For follow-up emails — generate the email alongside the CRM note:
Based on these call notes, write: 1. A 3-bullet CRM note (plain text, under 100 words) 2. A follow-up email (subject line + body, under 150 words, referencing the specific pain points mentioned) Tone: Professional but conversational. No fluff. Notes: [PASTE]
For renewal or upsell calls — track expansion signals:
Analyze these renewal call notes. Output: - Renewal risk: [High / Medium / Low] + one-sentence reason - Expansion signals: [Any mentions of new teams, use cases, or budget] - Action required: [Immediate / Within 1 week / Routine follow-up] - Suggested next offer: [Based on pain points mentioned] Notes: [PASTE]
These prompt variants are worth saving as templates by call type. Discovery, demo, renewal, and executive follow-up calls each deserve slightly different outputs. That small bit of specialization makes the notes far more useful than a one-size-fits-all summary ever will.
If your team runs internal deal reviews or strategy calls alongside prospect calls, you can extend this workflow to capture those as well. The same Make.com pipeline that writes CRM notes can simultaneously write a Slack-formatted meeting summary for internal review. This means your prospect call generates a CRM note in HubSpot and a deal-review summary in your #sales channel — all from one automated flow. For a deeper look at automating internal meeting notes, see our guide on building an AI meeting summarizer workflow.
The biggest failure mode with AI sales tools is adoption. Reps revert to old habits the moment friction appears. Three things that drive consistent usage: (1) build the AI step into existing tools rather than asking reps to use a new interface, (2) show the output quality in a team demo before rolling out, and (3) give reps permission to edit the AI notes rather than treating them as sacred. The AI writes a draft — the rep refines it in 30 seconds. That framing makes adoption feel safe rather than threatening.
If your team uses Notion as a secondary knowledge base alongside your CRM, you can use the same Make.com flow to write AI notes to a Notion database simultaneously — giving you a searchable archive of every conversation outside your CRM.
Once the team trusts the output, this workflow can become the backbone for more advanced reporting too: objection tracking, expansion-signal dashboards, and better forecast reviews all get easier when the raw notes are structured from the start.
💡 Want to automate the full CRM note workflow? See all recommended AI tools →
Practical prompts and automation ideas — no fluff.