sales-note-taker

name	sales-note-taker
description	Sales meeting note-taker and conversation-intelligence strategy — platform selection across 150+ tools (Fathom, Fireflies, Gong, Otter, Avoma, Grain, tl;dv, Read.ai, MeetGeek, Granola, Krisp, Circleback, Plaud, and the full long tail in references/platforms.md) plus backend API integration for auto-downloading transcripts into CRM, data warehouse, or Slack. Use when choosing an AI note-taker (pricing, features, compliance), deciding between webhook and polling, wiring transcripts into HubSpot or Salesforce, building a call-intelligence data pipeline, normalizing transcript formats, choosing a batch transcription service, a hardware AI voice recorder for in-person meetings, a bot-free / local-first / GDPR-hosted recorder, a real-time playbook-adherence tool, a meeting translation (RSI) platform, or a voice-note-to-text app, or debugging note-taker API rate limits and auth flows. Do NOT use for reviewing a single call for coaching (use /sales-call-review) or building a coaching program (use /sales-coaching).
argument-hint	[describe your note-taker selection or API integration question]
license	MIT
version	1.0.0
tags	["sales","note-taker","conversation-intelligence","api","integration","strategy"]

Sales Note-Taker & Conversation-Intelligence Strategy

Help the user (a) pick the right AI meeting note-taker for their sales team, and/or (b) wire its API into downstream systems (CRM, warehouse, Slack, internal tools). This skill is tool-agnostic — it references specific platforms for selection and integration patterns but focuses on cross-vendor strategy.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated knowledge.

Ask the user:

1. What's your primary goal?

   • A) Pick a note-taker for my team (selection/comparison)
   • B) Integrate an existing note-taker's API (transcripts → somewhere)
   • C) Both — evaluating a platform AND planning the integration
   • D) Debugging a specific API/webhook issue

2. What's your use case?

   • A) Sales org — discovery/demo calls, pipeline intelligence, coaching
   • B) Customer success — onboarding, QBRs, renewal health
   • C) Cross-functional — sales + CS + internal meetings
   • D) Specific workflow — e.g., auto-log transcripts to HubSpot, push action items to Slack, pipe everything to Snowflake

3. If integrating, where are transcripts going?

   • A) CRM (HubSpot, Salesforce, Attio, Pipedrive)
   • B) Data warehouse (Snowflake, BigQuery, Redshift, Databricks)
   • C) Internal app / database
   • D) Slack / notifications only
   • E) Multiple destinations (fan-out)

4. Scale?

   • A) <50 meetings/week (single team)
   • B) 50-500/week (mid-market sales org)
   • C) 500+/week (enterprise, multi-team)

Skip-ahead rule: if the user's prompt already has enough context, skip to Step 2.

Step 2 — Route or answer directly

Problem domain	Route to
Reviewing a specific call for coaching or scoring	/sales-call-review {user's question}
Building a coaching program or training cadence	/sales-coaching {user's question}
General CRM-to-tool integration patterns (Zapier, webhooks, iPaaS)	/sales-integration {user's question}
Salesloft Conversations config