$npx -y skills add sales-skills/sales --skill sales-avomaAvoma platform help — AI Meeting Assistant, Scheduler, Lead Router, Conversation Intelligence, and Revenue Intelligence modules. Use when Avoma bot not joining calls or dropping mid-meeting, transcription inaccurate with accents or technical terms, meeting notes not syncing to Hu
| 1 | # Avoma Platform Help |
| 2 | |
| 3 | ## Step 1 — Gather context |
| 4 | |
| 5 | If `references/learnings.md` exists, read it first for accumulated Avoma knowledge. |
| 6 | |
| 7 | 1. **What are you trying to do?** |
| 8 | - A) Configure Avoma account/team/plan or understand pricing tiers |
| 9 | - B) Build a backend integration (API, webhooks, transcript pipeline) |
| 10 | - C) Set up or tune AI scorecards (MEDDIC, BANT, SPICED) |
| 11 | - D) Configure Lead Router (form qualification, round-robin, handoff) |
| 12 | - E) Troubleshoot bot joining / recording / transcription issues |
| 13 | - F) Push meeting data into CRM, warehouse, or Slack |
| 14 | - G) Evaluate Avoma vs alternatives — **route to `/sales-note-taker`** |
| 15 | |
| 16 | 2. **Which Avoma plan?** |
| 17 | - A) Startup ($19/seat) — AI Meeting Assistant only |
| 18 | - B) Organization ($29/seat) — adds custom topics, API, group scheduling |
| 19 | - C) Enterprise ($39/seat) — SSO, HIPAA, custom retention, concierge onboarding |
| 20 | - D) Not sure yet |
| 21 | |
| 22 | 3. **Which add-ons (if any)?** |
| 23 | - A) Conversation Intelligence ($29/seat) — AI coaching, scoring, playlists |
| 24 | - B) Revenue Intelligence ($29/seat) — deal risk, forecasting, win-loss |
| 25 | - C) Lead Router ($19/seat) — form routing, SDR→AE handoff |
| 26 | - D) Multiple / all |
| 27 | - E) None yet |
| 28 | |
| 29 | Skip-ahead rule: if the user's prompt already has the context, skip to Step 2. |
| 30 | |
| 31 | ## Step 2 — Route or answer directly |
| 32 | |
| 33 | | User situation | Route to | |
| 34 | |---|---| |
| 35 | | "Avoma vs Fireflies vs Gong — which should we pick" | `/sales-note-taker {question}` | |
| 36 | | "Review this Avoma recording and score it" | `/sales-call-review {question}` | |
| 37 | | "Build a coaching program using Avoma recordings" | `/sales-coaching {question}` | |
| 38 | | "Generic Zapier/Make/n8n workflow" | `/sales-integration {question}` | |
| 39 | | "Schedule meetings without Avoma" | `/sales-meeting-scheduler {question}` | |
| 40 | | Anything Avoma-platform-specific (API, webhooks, pricing, scorecards, bot, Lead Router) | Stay here | |
| 41 | |
| 42 | When routing, use the exact command: `/sales-{skill} {user's original question}`. |
| 43 | |
| 44 | ## Step 3 — Avoma platform reference |
| 45 | |
| 46 | **Read `references/platform-guide.md`** for the full platform reference — modules, pricing, integrations, data model, workflows. |
| 47 | |
| 48 | Answer the user's question using only the relevant section. Don't dump the full reference. |
| 49 | |
| 50 | If the question involves API endpoints or webhook payloads, also read `references/avoma-api-reference.md`. |
| 51 | |
| 52 | ## Step 4 — Actionable guidance |
| 53 | |
| 54 | You no longer need the platform reference — focus on the user's specific situation. |
| 55 | |
| 56 | - **Scorecard setup**: Start with a default methodology template (MEDDIC, BANT, SPICED), run it on 10-20 historical calls, then customize topic weights based on what actually predicts wins in your pipeline. Don't over-customize before you have baseline data. |
| 57 | - **CRM sync debugging**: Check Settings → CRM → Field Mapping. Avoma pushes to specific CRM fields — mismatched field types (text vs picklist) silently fail. Test with one meeting before enabling org-wide. |
| 58 | - **Bot reliability**: If the bot fails on Teams consistently (79% failure rate reported), switch to dialer integration or manual recording as fallback. Google Meet's March 2026 "potential risk" queue for third-party bots affects all vendors — host must manually approve. |
| 59 | - **API integration**: Use webhooks over polling. Queue outbound API calls — 60 req/min is tight at scale. |
| 60 | |
| 61 | If you discover a gotcha, workaround, or tip not covered in `references/learnings.md`, append it there. |
| 62 | |
| 63 | ## Gotchas |
| 64 | |
| 65 | > *Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.* |
| 66 | |
| 67 | - **API access is Organization plan and above.** Startup plan has no API — you must upgrade to build integrations. |
| 68 | - **Advertised $19/seat is just the base.** Conversation Intelligence ($29) and Revenue Intelligence ($29) are separate add-ons. A fully-loaded seat costs $77-97/seat depending on billing cycle. Budget the plan you'd actually run. |
| 69 | - **Bot reliability issues are well-documented.** 73% of G2 reviewers report recorder failures — late joins (48%), mid-call drops (31%), complete no-shows (27%). Microsoft Teams has the worst failure rate (79%). Buil |