SuperAPI AI Directory
Partner中文AI newsFavorites
Skillssales-bliro

sales-bliro

Marketing & growth

View repository

Updated 10-16 10:14

About this skill

Bliro Platform Help

Step 1 — Gather context

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

Ask the user:

  1. What's your primary goal?
    • A) Set up Bliro for my team (configuration, rollout)
    • B) Integrate Bliro with my CRM or downstream tools (API, webhooks)
    • C) Evaluate Bliro vs alternatives
    • D) Troubleshoot a specific Bliro issue

  1. Which CRM?

    • A) Salesforce
    • B) HubSpot
    • C) SAP
    • D) Microsoft Dynamics 365
    • E) None / not relevant

  2. Meeting types?

    • A) Online only (Zoom, Teams, Meet)
    • B) In-person only
    • C) Both online and in-person

Skip-ahead rule: if the user's prompt already contains 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}
Comparing note-takers across vendors /sales-note-taker {user's question}
General CRM-to-tool integration patterns (Zapier, webhooks, iPaaS) /sales-integration {user's question}
Meeting scheduling (not note-taking) /sales-meeting-scheduler {user's question}

Otherwise, answer directly below.

Step 3 — Bliro platform reference

Read references/platform-guide.md for the full platform reference — capabilities, pricing, data model, integration recipes, code examples.

Answer the user's question using only the relevant section. Don't dump the full reference.

Step 4 — Actionable guidance

You no longer need the platform guide — focus on the user's specific situation.

Setup priorities:

  1. Install desktop app (Windows/Mac) + iOS app for in-person meetings
  2. Connect calendar (Google/Outlook) for automatic meeting detection
  3. Configure CRM integration — map AI summary fields to CRM objects (Task/Event/Call for Salesforce, Activity Timeline for HubSpot)
  4. Set up coaching playbooks if using the coaching module
  5. For API consumers: the "For Revenue Teams" plan bundles API + webhook access together with CRM integration (verified 2026-06-13). Bliro pricing is sales-led — there are no public euro figures on the official pricing page.

If you discover a gotcha, workaround, or tip not covered in references/learnings.md, append it there.

Gotchas

Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.

  • API + webhooks are bundled with CRM in the "For Revenue Teams" plan (verified 2026-06-13). Bliro moved to a sales-led 3-tier structure — Standard / For Revenue Teams / Enterprise — and no longer publishes euro prices or a public free tier. The "Standard" plan has no CRM, API, or webhooks; if you have CRM on the revenue-teams plan you already have API + Webhook Access. (Older Free/Professional €49/Unlimited €89 figures are no longer on any official page — confirm pricing with Bliro sales.)
  • Speaker recognition can be inaccurate. G2 reviewers report occasional speaker misattribution — review and correct before syncing to CRM on important deals.
  • No MCP server. Unlike Jamie, Circleback, or MeetGeek, Bliro has no MCP integration for AI coding agents. Use the REST API or webhooks instead.
  • API is currently read-only. Only GET /v3/calls is documented — you can pull call data out but can't push data in or trigger actions via API.
  • German-language UI by default. The platform originated in Germany. English UI is available but some help center articles are German-first.
  • Custom AI models are Enterprise-only. Fine-tuning for industry-specific terminology requires Enterprise plan with custom pricing.

Related skills

  • /sales-note-taker — Compare Bliro against other AI meeting note-takers, or build a transcript data pipeline
  • /sales-coaching — Build coaching programs that consume Bliro's anonymous coaching data
  • /sales-call-review — Review a specific call for coaching
  • /sales-integration — General CRM/tool integration patterns (Zapier, webhooks, iPaaS)
  • /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do

Examples

Example 1: Setting up Bliro CRM integration with Salesforce

User says: "I want Bliro to automatically update our Salesforce opportunities after every call." Skill does:

  1. Reads platform guide for Salesforce integration details
  2. Explains Bliro saves AI notes as Task, Event, or Call objects on Opportunities, Accounts, or Contacts
  3. Walks through field mapping configuration at app.bliro.io/settings/integrations
  4. Notes that CRM integration requires the "For Revenue Teams" plan (sales-led pricing, no public euro figure) — which also bundles API + webhook access Result: Working Salesforce auto-sync with field-level mapping.

Example 2: Building a webhook pipeline from Bliro to a data warehouse

User says: "I need to pipe all Bliro call transcripts into BigQuery for analytics." Skill does:

  1. Reads API reference for webhook payload schema
  2. Designs pipeline: Bliro webhook → Cloud Run → validate HMAC-SHA256 signature → extract callData.transcriptChunks and callData.summaries → write to BigQuery
  3. Provides working Python webhook receiver with signature verification
  4. Notes that webhooks require the "For Revenue Teams" plan (bundled with CRM + API; sales-led pricing) and deliver full transcript + summary in one payload. Critically: Bliro signs only the inner callData object (timestamp.JSON.stringify(callData)), NOT the raw request body — re-serialize callData to match Result: Production webhook pipeline architecture with code.

Example 3: Evaluating Bliro vs Jamie for an EU sales team

User says: "We need a GDPR-compliant bot-free note-taker. Bliro or Jamie?" Skill does:

  1. Routes to /sales-note-taker for cross-vendor comparison, but provides key differentiators first
  2. Compares: both bot-free and EU-hosted. Bliro has deeper CRM integration (Salesforce, HubSpot, SAP, Dynamics 365) and a coaching module, with CRM + API + webhooks bundled into its "For Revenue Teams" plan (sales-led pricing, 10-user minimum). Jamie has an MCP server, broader language-support marketing, and a lower self-serve entry price with no seat minimum
  3. Recommends Bliro for teams prioritizing CRM automation and coaching; Jamie for teams wanting AI workflow extensibility via MCP Result: Clear differentiation on the axes that matter for the decision.

Troubleshooting

Speaker recognition misattributing speakers

Symptom: Transcript shows wrong speaker names, especially in multi-participant calls Cause: System audio capture doesn't have per-participant audio streams like bot-based tools do — speaker diarization relies on voice fingerprinting Solution: Review and correct speaker labels before CRM sync on important deals. Use smaller meetings where possible. The iOS app may provide better diarization for in-person meetings since the microphone is closer.

CRM fields not syncing after meetings

Symptom: Bliro records the meeting but CRM objects don't get updated Cause: CRM integration requires the "For Revenue Teams" plan (sales-led pricing). Also check that calendar integration is connected (Bliro matches meetings to CRM records via calendar events) Solution: Verify plan tier at app.bliro.io/settings. Ensure calendar (Google/Outlook) is connected. Check CRM field mappings at integration settings. If using Salesforce, verify the connected user has write access to Task/Event/Call objects.

Webhook not firing after calls

Symptom: Webhook endpoint receives no POST requests after calls complete Cause: Webhooks are deactivated by default when created. Also requires the "For Revenue Teams" plan (API + webhooks are bundled with CRM there) Solution: Navigate to app.bliro.io/orgs/settings/webhook. Verify the webhook is activated (not just created). Use the "Test Webhook" button to verify endpoint connectivity. Ensure HTTPS with valid TLS 1.2+ certificate. Check that your endpoint returns 2xx status codes promptly.