Krisp AI Meeting Assistant

How the conversation gets in and how faithfully it is written down: a bot that joins Zoom, Microsoft Teams, Google Meet and Webex, botless capture from a desktop or mobile app, in-person meetings and phone calls, file upload, live transcription, speaker identification and names, the languages supported with German stated, meetings that switch language, custom vocabulary for names and jargon, timestamps linked to the recording, and editing of the transcript.

0 — Does not record or transcribe meetings; a note template or agenda tool without capture.

3 — A bot that joins one or two conferencing tools and produces a transcript; languages, speaker names, in-person capture and accuracy are basic or not described.

5 — A bot for Zoom, Teams and Google Meet, a desktop or mobile app for in-person meetings, file upload, speaker identification, German among the supported languages, timestamps linked to the recording, and an editable transcript.

8 — Botless capture documented next to the bot, Webex and phone or dialer calls, live transcription, mixed-language meetings handled, custom vocabulary, speaker names learned across meetings, and the transcription engine or its accuracy per language stated.

10 — Capture a regulated team relies on: every channel above with accuracy published per language and method, dialects and specialist vocabulary documented, on-device or customer-hosted transcription as an option, and how errors are corrected and fed back stated.

What the tool makes of the transcript: summaries and minutes by meeting type with editable templates, decisions and action items with owners and due dates, summaries in the meeting's language or a chosen one, follow-up emails, clips and highlights, search across all meetings, questions answered over the archive with citations back to the transcript passage, shared team folders or channels, and the minutes exported to Word, PDF or a wiki.

0 — No summaries of any kind; only the raw transcript or recording.

3 — One generic summary per meeting; templates, action items, search across meetings and citations are basic or not described.

5 — Summaries with templates per meeting type, action items and decisions extracted, the summary language selectable with German available, search across meetings, questions answered over one or several meetings, and sharing or export of the minutes.

8 — Custom templates per team, action items with owners pushed to task tools, answers that cite and link the transcript passage they rest on, topic or keyword tracking across meetings, team libraries with permissions, and the AI models used for summaries named.

10 — Meeting knowledge a company can audit: every generated statement traceable to its source passage, hallucination handling and human review documented, summary quality by language stated, and the archive queryable through an API or MCP server with the same permissions as in the app.

How the notes reach the place where work happens: calendar connection with rules for which meetings are recorded, CRM fields filled from the call (HubSpot, Salesforce, Pipedrive, Microsoft Dynamics), project and task tools, Slack and Microsoft Teams channels, Notion, Confluence and SharePoint, Zapier, Make or n8n, a documented REST API and webhooks, an MCP server for AI assistants, and browser extensions and native apps.

0 — No integrations and no export; the notes stay in the app.

3 — A calendar connection and an email or Slack summary; CRM, API and task tools are basic or not described.

5 — Google and Microsoft calendars, a native CRM integration (HubSpot or Salesforce), Slack or Teams, a task or wiki tool, Zapier or Make, and a documented API or webhooks.

8 — CRM field mapping per meeting type, several CRMs including Microsoft Dynamics or Pipedrive, a full REST API with webhooks and reference documentation, an MCP server, SharePoint or Confluence export, and recording rules per calendar or meeting type.

10 — An integration layer a company builds on: every object reachable by API with rate limits and versioning stated, granular OAuth scopes, data residency kept across integrations, and the integrations administered centrally with logs.

Whether every person in the meeting knows and can decide, and whether the tool can be introduced under German co-determination: a recording notice to all participants including external guests, consent or opt-out before the recording starts, a visible bot or a stated notice for botless capture, rules for when the assistant joins automatically, stopping and deleting a recording on request, per-person analytics (talk time, sentiment, engagement scores) off by default or switchable per organisation, material or a template for a works agreement (Betriebsvereinbarung, § 87 (1) no. 6 BetrVG), and support for a data protection impact assessment.

0 — Built to record people without their knowledge, or sells covert recording or individual performance scoring as a feature.

3 — A general privacy statement and a bot that appears in the participant list; notices to guests, opt-out, per-person analytics and works councils are basic or not described.

5 — A recording notice to participants by chat message, email or the bot's name, a way for a participant to stop the recording or opt out, admin rules for when the assistant joins, recordings deletable on request, and per-person analytics described with how to switch them off.

8 — Consent collected before recording starts for external participants, per-person analytics off by default or switchable per organisation, botless capture with its notice method documented, a works-council information pack or works-agreement template published, DPIA support, and the EU AI Act classification stated.

10 — Co-determination built into the product: every analytic and its granularity documented for the works council, consent and opt-out logged per participant, configuration changes logged, minimum group sizes for any team statistics, and references of works-council-approved rollouts published.

What the employer can govern: retention periods and automatic deletion of recordings, transcripts and summaries, whether audio and video can be discarded after transcription, sharing defaults and link permissions, customer content excluded from model training by contract, the AI and transcription providers named with their region and their own retention, encryption, single sign-on (SAML), SCIM, roles and workspaces, admin policies on auto-recording and sharing, audit logs, export of the whole archive, and security certifications such as ISO 27001 and SOC 2.

0 — No administration and no deletion; every user decides alone and recordings are kept indefinitely.

3 — Users can delete their own recordings and a security page exists; retention policies, model training, SSO and audit logs are basic or not described.

5 — Retention settings per workspace, customer content excluded from model training, team workspaces with roles, single sign-on, admin control over sharing and auto-recording, encryption at rest and in transit, and ISO 27001 or SOC 2 stated.

8 — Automatic deletion by policy with audio discardable after transcription, the AI and transcription subprocessors named with region and zero retention, SAML with SCIM, granular roles, audit logs, legal hold or export of the full archive, and certifications with their scope published.

10 — Governance an auditor accepts: every retention, sharing and recording policy enforceable centrally and logged, models run on the vendor's own or the customer's infrastructure as an option, audit logs exportable to a SIEM, and the deletion of every copy, including at subprocessors, documented.

Who the contracting entity and the parent company are, where recordings, transcripts, summaries, voice profiles and account data are stored and processed, which language model and transcription providers read them and where, and who the other subprocessors are (hosting, email, support, analytics and payment tools). Independently sourced by the sovereignty pipeline. A conferencing platform outside Europe that the customer already uses is part of the meeting, not counted against the notetaker; where the notetaker stores and processes the conversation is.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (language models, transcription, email, support, payment) run through non-EU providers without a stated safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessors including the AI providers listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, with transcription and language models run in Europe by European operators, data export and deletion documented, and certifications published with their scope rather than implied.

Whether a buyer can compute the real annual cost from public pages alone: price per seat and tier, what counts as a seat (every invited user, only recording users), transcription minutes or credits included, storage limits, which features (CRM integrations, API access, SSO, custom retention, EU hosting, AI credits) cost extra, the free tier and its limits, monthly versus annual billing, minimum seats and VAT.

0 — No public prices at all; every customer is a sales call.

3 — A starting price or a free tier exists, but how cost scales with seats, minutes or features is unclear.

5 — Tiers are public with their seat price and main inclusions, but at least one commonly needed piece (SSO, CRM integration, API, custom retention, EU hosting, minute or credit limits) is unpriced or "on request".

8 — Every tier priced publicly with its scaling rule (seats, minutes, credits, storage), add-ons priced, what counts as a seat stated, overage handling stated, minimum term and VAT treatment stated.

10 — Complete price computability: annual cost derivable for a given team size and meeting volume, with every add-on, overage and support fee and the cancellation and data-return terms published.