Kalyvox vs LiteScribe

Vergleichen Sie Kalyvox und LiteScribe nach Funktionen, Rechtsraum, Nachweisen und Einsatzpassung.

Kalyvox

France· Meeting Transcription & Notes

Needs review

Shortlist Kalyvox when you need a French-operated AI receptionist for inbound SMB calls with keep-your-number forwarding, intent rules, live transfer, and calendar booking. Skip when you need omnichannel helpdesk workflows, self-hosted or on-device speech, or an EU-only subprocessor graph without US telephony/AI providers. Consider Intercom for multi-channel support, or LiteScribe when transcription locality matters more than live phone coverage.

EU-operated (France)AI phone receptionistKeep existing numberIn-call calendar bookingDPA on requestInbound-only (no outbound dialer)

Eintrag ansehen Webseite besuchen

LiteScribe

United Kingdom· Meeting Transcription & Notes

Needs review

Shortlist when you need bot-free capture and a real on-device speech plus LLM path on Windows, macOS, or Linux. Skip the cloud path when US transcription processors are unacceptable; use HappyScribe or Microsoft Teams instead depending on whether you want an EU cloud notetaker or a Microsoft 365-native workflow.

UK-operatedBot-free captureOn-device Local ModeFreemiumNot open source

Eintrag ansehen Webseite besuchen

Hervorgehobene Zeilen unterscheiden sich zwischen den Produkten.

Kalyvox vs LiteScribe: Überblick
Merkmal	Kalyvox	LiteScribe
Herkunftsland	France	United Kingdom
Kategorie	Meeting Transcription & Notes	Meeting Transcription & Notes
Open Source	Nein	Nein
Self-Hosted	Nein	Nein
Hauptsitz	France	United Kingdom
Rechtsträger	KALYVOX SASU, 6 place du Président Thomas Woodrow Wilson, 31000 Toulouse, France (SIREN 999 458 409)	Clinton Browne trading as LiteScribe (UK sole trader; no Ltd on Companies House)
Anwendbares Recht	French law; Toulouse courts (legal notice / terms)	Terms refer only to the jurisdiction where LiteScribe.ai operates; no explicit governing-law country clause found
US-Mutter / Kontrolle	Keine bekannte US-Mutter	Keine bekannte US-Mutter
CLOUD-Act-Exposition (indikativ)	Mittel	Mittel
EU-Hosting-Status	Teilweise	Teilweise
Hosting / Residenz	App/site on Supabase with AWS Europe Paris (eu-west-3) per legal notice. Privacy lists US-group Twilio (telephony), Stripe (payments), OpenAI/AI providers (voice/transcription), plus PostHog EU analytics and Google Analytics. SCCs claimed for non-EU transfers.	Vendor claims European storage for recordings/transcripts. Cloud transcription uses AssemblyAI (US). Default AI note features use Google Gemini. Infrastructure and support stack publicly includes Supabase, Cloudflare, Stripe, and Google Analytics. Desktop Local Mode keeps audio and on-device AI on the user machine.
Zusammenfassung	French AI phone receptionist SaaS that answers inbound business calls, qualifies intent, books appointments, transfers when needed, and delivers structured call tickets.	Bot-free meeting and interview transcription with speaker-labelled notes. Desktop Local Mode runs speech and LLM models on-device; the cloud path uses AssemblyAI in the US.
Tags	AI receptionist voice AI business telephony call qualification appointment booking GDPR France	meeting transcription meeting notes offline on-device AI no bot privacy

Auf einen Blick: Kalyvox vs LiteScribe
Auf einen Blick	Kalyvox	LiteScribe
HQ	Toulouse, France	Nicht angegeben
Legal entity	KALYVOX SASU (SIREN 999 458 409)	Nicht angegeben
Founded	2025 (About); registry inscription early 2026	Nicht angegeben
Product type	SaaS AI inbound phone receptionist	Nicht angegeben
Self-host	No	Nicht angegeben
Open source	No	No
Commercial model	Monthly subscription + per-minute usage; free trial	Nicht angegeben
HQ / entity	Nicht angegeben	United Kingdom (sole trader; registrant Hampshire, GB)
Capture model	Nicht angegeben	Local system audio + mic (no meeting bot)
Local Mode	Nicht angegeben	Desktop on-device speech + LLM (Pro/Business)
Cloud transcription	Nicht angegeben	AssemblyAI (US)

Key capabilities: Kalyvox vs LiteScribe
Key capabilities	Kalyvox	LiteScribe
EU-operated (France)	Ja	Ja
AI phone receptionist	Ja	Nicht angegeben
Keep existing number	Ja	Nicht angegeben
In-call calendar booking	Ja	Nicht angegeben
DPA on request	Ja	Nicht angegeben
Inbound-only (no outbound dialer)	Ja	Nicht angegeben
Bot-free capture	Nicht angegeben	Ja
On-device Local Mode	Nicht angegeben	Ja
Freemium	Nicht angegeben	Ja
Not open source	Nicht angegeben	Ja

Kalyvox

Inbound AI answering with keep-your-number forwarding
Kalyvox provides a number you can forward to, or answers on its line, so you keep the public business number. You choose continuous coverage, unanswered-only, or after-hours forwarding. Best for SMBs that cannot staff every ring; limit: outbound dialling and automated calling campaigns are out of scope.
Intent qualification with custom questions and priorities
Per call reason you define questions, business facts the bot may share, and priority rules. The assistant extracts contact details, repeats critical fields, and builds an intent-tagged ticket. Useful when emergencies, bookings, and sales calls must not share one script; answers outside your configured facts are supposed to be declined rather than invented.
Rule-based live transfer to humans
Configured reasons can offer or force transfer to a named teammate when available. If nobody accepts, the bot continues, captures the request, and escalates context for callback. Fits practices and field teams that want humans only for the hard cases.
Calendar booking during the call
With Google Calendar or Outlook connected, the assistant checks allowed availability, proposes a slot, and writes the event with caller context. Also supports sending an external booking link by SMS or email. Appointment sync is part of the core commercial model; confirm plan inclusion on the vendor pricing page.
Structured tickets, transcripts, and team alerts
Each handled call produces a dashboard card with summary, full transcript, priority, and next action, plus email and optional SMS notifications. CSV export and multi-user roles support follow-up without replaying voicemail. Transcript retention defaults to a rolling year and is configurable.
Zapier, webhooks, and ChatGPT analysis connectors
Qualified call payloads can flow to CRM, Slack, or Sheets via Zapier or webhooks, and authorised call data can be queried from a ChatGPT connector. Suited to teams that already automate ops; Zapier is documented as available from the Pro tier upward.

LiteScribe

Bot-free local meeting capture
Records system audio and the microphone on the device so no extra participant joins Zoom, Teams, Meet, Webex, or Discord. The same capture path works for in-person meetings without a meeting link.
Desktop Local Mode (on-device speech + LLM)
On Windows, macOS, and Linux (Pro and Business), both the LiteScribe Local Transcription Engine and Local LLM models run on the user's CPU/GPU. Audio is not uploaded; mark local transcripts private or disable sync if the text must stay on the device too.
Speaker-labelled notes and exports
Produces speaker separation, summaries, decisions, and action items, then exports to formats including PDF, DOCX, and SRT. Cloud and Local Mode both target note drafting, not raw text alone.
Multilingual transcription surface
Vendor claims 100+ transcription languages, with a product UI shipping in English plus additional locales (including several major European languages). Exact language coverage should be verified against the live language list for your use case.
BYOK / multi-model AI chat on transcripts
Web and enrichment features can use a model picker and optional bring-your-own API keys. Default cloud enrichment uses third-party providers; Local Mode keeps enrichment on-device instead.

Assurance & compliance: Kalyvox vs LiteScribe
Assurance & compliance	Kalyvox	LiteScribe
Independent security / no-logs audit	Not found Privacy mentions regular security audits and penetration tests; no public third-party audit report located.	Not found No public independent audit report located.
ISO 27001	Not found Privacy references ISO 27001-certified AWS infrastructure; no Kalyvox-owned ISO certificate page found.	Not found
SOC 2 / SOC 3	Not found	Not found
GDPR / EU data protection	Vendor claimed French controller entity, GDPR rights section, CNIL complaint path, processor role in terms.	Vendor claimed UK entity; privacy policy includes GDPR rights section. Vendor explicitly says it is not a GDPR certification. Cloud path uses US processors.
US CLOUD Act exposure (indicative)	Partial EU entity / no known US parent, but Twilio, Stripe, OpenAI/AI providers, and AWS-group hosting appear in public disclosures. Not legal advice.	Partial No known US parent, but cloud transcription uses AssemblyAI (US) and default AI uses Google; Stripe and Google Analytics also listed. Local Mode avoids content transfer to those AI/transcription processors. Indicative only, not legal advice.
Data processing agreement (B2B)	Vendor claimed Terms Art. 8: DPA available on request; customer is controller for caller data.	Not found No public self-serve DPA page found; ask sales/support.
EU AI Act	Partial AI-centric phone assistant; vendor publishes responsible-AI limits (no advice, no improvisation, AI disclosure). No public AI Act conformity statement found; buyers should classify the use case themselves.	Unknown AI-centric product; no public AI Act classification statement found.

Considerations & known limitations: Kalyvox vs LiteScribe
Considerations & known limitations	Kalyvox	LiteScribe
US-group telephony, payments, and AI providers	Medium Even with AWS Paris application hosting, Twilio, Stripe, and OpenAI-class providers process call or account data paths. Sovereignty-sensitive buyers must review SCCs and whether voice audio leaves the EU.	Nicht angegeben
No public independent audit package	Medium Security claims (encryption, pen tests, AWS ISO) are first-party. Request audit reports, pen-test summaries, and a signed DPA before handling sensitive caller data.	Medium No public ISO 27001, SOC 2, or independent audit was found, which blocks many enterprise security reviews until documents are provided under NDA.
AI qualification and transcription errors	Medium Terms explicitly warn that AI may misinterpret calls. Critical medical, legal, or emergency workflows still need human escalation rules and monitoring.	Nicht angegeben
Young company / thin public assurance trail	Low Entity is newly registered (2025 to 2026). Expect lighter public cert history than long-established EU SaaS vendors; validate financial and support commitments in procurement.	Nicht angegeben
Cloud path uses US transcription (AssemblyAI)	Nicht angegeben	High If users take the cloud path, meeting audio is processed by AssemblyAI in the United States. Local Mode is the mitigation; web/mobile are not.
EU storage claim vs named US processors	Nicht angegeben	Medium Privacy policy claims European storage/endpoints while also naming AssemblyAI and stating audio is sent there. Diligence should not rely on the softer EU-endpoints wording alone.
Thin public imprint	Nicht angegeben	Low Terms/Privacy do not publish a registered office or company number. UK sole trader status is consistent with no Companies House Ltd, but buyers may want contractual identity clarified.

Passung

Kalyvox

Best fit when

French or EU SMBs whose revenue still depends on inbound phone calls
Field and clinic teams that need after-hours or overflow coverage without hiring a full receptionist
Buyers who want configurable intents, human transfer rules, and structured tickets with transcripts
Teams ready to connect Google Calendar or Outlook for booking during the call
Organisations that can accept Twilio, Stripe, and OpenAI-class subprocessors under SCCs

Poor fit when

Enterprises needing a full omnichannel helpdesk (chat, email, in-app) comparable to Intercom
Procurement that requires EU-only subprocessors with no US-group cloud, telephony, or model providers
Buyers who need self-hosted or fully on-device voice AI
Use cases centred on outbound calling, diallers, or automated prospecting campaigns

Consider instead when

When: You need omnichannel customer messaging and helpdesk workflows rather than phone reception
Consider: Intercom (US incumbent in catalog)
Different product class: support suite vs AI receptionist
When: You mainly need meeting or interview transcription with optional on-device processing
Consider: LiteScribe or HappyScribe
Speech-to-notes tools, not live call answering
When: You need bulk SMS, WhatsApp, or voice messaging APIs for campaigns and OTP
Consider: Afilnet
Messaging API platform, not an AI front desk

LiteScribe

Best fit when

Consultants and managers who refuse a visible meeting bot in Zoom, Teams, or Meet
Teams that can use the desktop app and need Local Mode for confidential interviews or board recordings
Buyers who want speaker-labelled transcripts plus drafted summaries, decisions, and action items
Users who need the same capture path for remote and in-person meetings

Poor fit when

Organisations that require all cloud transcription to stay with EU-only processors (cloud path uses AssemblyAI)
Buyers who need a published ISO 27001/SOC 2 pack and a self-serve DPA before pilot
Enterprises standardised on Microsoft 365 who only want tenant-native Teams transcription
Teams that only use web/mobile and assume the whole product is local

Consider instead when

When: You want an EU-operated cloud meeting notetaker with auto-join style workflows rather than on-device Local Mode
Consider: HappyScribe
Irish peer in this catalog; stronger cloud EU story, different capture model.
When: You need transcription inside an existing Microsoft 365 tenant with admin residency controls
Consider: Microsoft Teams
Incumbent path for regulated Microsoft shops; not bot-free system-audio capture.

Open questions for due diligence

Kalyvox

Will Kalyvox sign your DPA and provide a current subprocessor list with regions for voice audio and transcripts?
Which exact model providers process live audio versus anonymised text, and can processing be limited to EU regions?
Are independent pen-test or ISO/SOC reports available under NDA?
What fair-use or concurrency limits apply on each plan for simultaneous inbound calls?

LiteScribe

Will LiteScribe sign a B2B DPA and provide a dated subprocessor list with regions?
Which exact cloud regions host Supabase/primary storage, and how does that reconcile with AssemblyAI processing?
Are ISO 27001 or SOC 2 reports available under NDA?
What is the contractual governing law and contracting party name on paid invoices?