Parloa: the compliance stack is the product
Berlin-based, voice-first, with deep contact-centre integrations and a certification list that runs to DORA. Project volumes are typically six figures, there are no public prices and no trial, which tells you exactly who it is for.
Parloa
Parloa is a Berlin company building AI for customer service, with a voice-first design and deep integrations into contact-centre infrastructure like Genesys and Avaya. It is technically serious and it is not a product you evaluate on a Tuesday afternoon.
The most useful thing to understand about it is what its buying process tells you about its intended buyer.
The signals in the commercial model
Six figures per project. No public price, no trial, long evaluation cycles.
Parloa’s commercial model, checked July 2026
None of that is a criticism. It is a coherent description of a company selling into regulated enterprise procurement, where a self-service tier would be noise and where the customer expects a scoped project rather than a subscription.
It does mean the qualification question answers itself: if that process sounds disproportionate for your company, the product is disproportionate for your company. Not worse, differently sized.
What the money buys
Voice done properly. Handling interruptions, background noise, dialect, people changing subject mid-sentence, and sub-second latency because a conversation that pauses is a conversation that fails. This is genuinely hard and it is the reason building your own telephone agent is a worse idea than it sounds.
Contact-centre integration. Genesys and Avaya are not systems you connect to casually. That integration depth is a large share of what an enterprise is paying for.
A compliance stack that shortens the review. ISO 27001:2022, SOC 2 Type I and II, GDPR, HIPAA, PCI DSS, DORA.
That last list deserves the headline treatment it gets. For a bank, an insurer or a healthcare provider, the certification list is not a trust badge: it is weeks of review that do not have to happen. DORA in particular matters for EU financial entities, where third-party ICT risk requirements are specific and unavoidable. A vendor that arrives with the file already assembled is materially cheaper to buy than one that does not, and that cost never appears in a price comparison.
Where it is the right answer
Regulated sector, voice channel, real volume. All three. Remove any one and something else is a better fit.
When the buying process is itself the constraint. If your procurement will take four months regardless, buying from a vendor whose documentation anticipates that is a genuine advantage.
Where it is not
Mid-market service teams. Four people in customer service do not need this, cannot use most of it, and would spend more on the evaluation than on the alternative. The comparison sets out where the threshold sits (auf Deutsch).
Text-first inbound. If most of your volume arrives by email and web form, voice depth is capability you are not using. Automate the text channel in the systems you already run.
When the answer needs your data. Like any platform, Parloa answers from what it can reach. The questions that actually drive automation rates (order status, contract terms, delivery dates) need a live lookup into your systems. That is buildable and it is a project, not a feature.
What to verify
- Processing location per deployment, not only the storage region: separate answers
- The model provider underneath, named in the DPA as a sub-processor
- Retention for audio and transcripts, in days, including backups
- The escalation path, designed before the automation rather than after
- Works council engagement, before the pilot: recording and evaluating conversations is generally co-determined under § 87 BetrVG
The criminal-law point outranks all of them in Germany: recording the non-publicly spoken word without authorisation is an offence under § 201 StGB. An announced, acknowledged and logged consent at the start of the call is not a formality, it is the control.
Since 2 August 2026, disclosure that the caller is speaking to an AI is separately required under Article 50 of the AI Act (auf Deutsch), regardless of risk class. In a voice channel that belongs in the opening line.
The read
Parloa is a good example of a product whose price is mostly not about the technology. You are buying voice engineering that is genuinely difficult, integration into systems that are genuinely closed, and a compliance file that genuinely removes weeks of work.
For an organisation that needs all three, that is a fair trade and there are few alternatives. For an organisation that needs one of the three, it is an expensive way to get it, and the honest version of that advice is the reason we would rather write this than pretend the threshold does not exist.
Frequently asked questions
What does Parloa cost?
There is no public pricing. Projects typically run into six figures, scoped by deployment size, integrations, languages and call volume.
Is Parloa GDPR-compliant?
It carries the relevant certifications and hosts in Germany. That eases your review; it does not replace your lawful basis, your DPA or your own documentation.
Why does the certification list matter so much?
For regulated buyers it converts directly into review time not spent. DORA in particular is unavoidable for EU financial entities, and a vendor arriving with it in place is cheaper to buy than one that does not.
Can we start small?
Not really: the commercial model is not built for it. If a small start is what you need, that is a signal about fit rather than a negotiating position.
What is the alternative for a mid-sized company?
Automate the text channel first, in the systems you already run, with a named owner and a measured before-state. If volume and results justify voice later, this evaluation will be better informed.
Sources: Parloa product and compliance material, checked July 2026; § 201 StGB; § 87 BetrVG.
Strategy Call