A client calls the firm after 8 pm, when nobody is left to pick up. An AI reception line takes the call instead, asks a few questions, books a slot and leaves a note in the CRM. Convenient — until someone asks exactly what ended up in that note, and who at the firm can open it. That question isn't a matter of taste; it follows from the law: whatever the client said about their case is covered by the attorney's or legal counsel's professional secrecy before it ever reaches any system.
Here's what you'll get from this page: what the laws on the legal profession and on legal counsel actually require, why a note and a recording from an AI reception line follow the same rules as a conversation in the office, what's safe to hand to a system versus what should stay visible only to the lawyer handling the case, and when a decision has to be made by a lawyer, not a system.
An after-hours call: who actually heard the client's case
At a small firm, an after-hours call usually goes to voicemail or is lost entirely. Deploying an AI reception line instead solves a real problem: someone answers, asks questions, books a time. The question that's easy to skip during rollout is a different one: since the call concerns a client's case, who — besides the client and the firm — heard it, where did its content go, and who can play it back later.
This isn't a technical question about a phone provider. It's a question of whether the firm still controls the secrecy it's legally required to protect — regardless of whether the phone is answered by a person, a machine, or an AI assistant. We cover a similar problem — one queue instead of scattered channels — in query handling automation, though without the professional-secrecy angle.
Attorney-client privilege: what Poland's law on the legal profession requires
Article 6(1) of Poland's Law on the Legal Profession (Prawo o adwokaturze) states that an attorney is obliged to keep secret everything they learned in connection with providing legal assistance (Prawo o adwokaturze, Journal of Laws 2024 item 1564). The wording is deliberately broad: it doesn't say "the content of the advice", it says "everything" — including the fact that a client called at all, the topic they raised, and the details they shared before the attorney gave any advice.
What the duty covers, and for how long
Paragraph 2 of the same article adds that the duty to maintain professional secrecy isn't limited in time — it doesn't expire when the case closes or the firm shuts down. Paragraph 3 goes further: an attorney cannot be released from this duty regarding facts they learned while providing legal assistance or handling a case. It's one of the few obligations in the legal system phrased this unconditionally.
The same duty applies to legal counsel
Poland's law on legal counsel (radcowie prawni) sets out an identical mechanism in different words: a legal counsel is obliged to keep secret everything they learned in connection with providing legal assistance, and the duty to maintain professional secrecy isn't limited in time (Ustawa o radcach prawnych, Journal of Laws 2024 item 499). For a client, the distinction between an attorney (adwokat) and a legal counsel (radca prawny) rarely matters in practice — from the standpoint of professional secrecy it's the same level of protection, just written into two separate laws.
That matters for mixed firms, where both attorneys and legal counsel work on the same team: access rules for notes and recordings need to be equally strict for both groups, since both are bound by the same duty, just under a different legal basis.
A recording and note from an AI reception line are covered by secrecy too
An AI reception line that answers the phone, qualifies the request and saves a summary along with the call recording in the CRM is exactly what AI reception and telephony does. Since the content of the call is the client's case, the summary and recording aren't an ordinary technical log — they're another place where professional secrecy exists, alongside paper notes and the case file.
The consequence is straightforward: a phone recording from the AI reception line needs the same access rules as the case file, not the rules usually applied to a general helpline recording — "anyone on the team can listen if they need to".
A note in the CRM is part of the secrecy, not just a note
The practical conclusion from all this: the content of a conversation about a client's case, saved as a CRM note, is covered by the same professional secrecy as a conversation in the office. The fact that a system wrote the note instead of a lawyer typing it by hand changes nothing about the duty itself — it only makes it easier to accidentally grant access to someone who shouldn't have it.
Why access can't be open to everyone
At many small firms, the CRM ends up as one shared account: reception staff, trainees and every lawyer see the same thing. Convenient for scheduling, dangerous for case notes — because then the content of one client's privileged conversation is visible to someone who never worked on that case and doesn't need to know its details to do their job.
A human before use: why an AI's output needs review
The recommendation for systems built on language models is: wherever possible, a human should review the model's output before it's used in practice — especially in high-stakes domains (OpenAI, Safety best practices). This principle, framed generally for AI deployments, applies directly to a phone-call summary at a law firm: before a summary becomes an official case note in the CRM, the lawyer handling the case should review it, rather than assuming an automatic summary is already a finished procedural document.
Human review isn't a formality — it's the moment a lawyer can remove anything the AI misunderstood, or narrow down what ends up in a field the whole team can see.
What's safe for a system to record, and what stays out of the general file
A sensible split looks like this: the fact that a client called, their contact details, and a one-sentence general topic ("inheritance matter", "employment dispute") can go into a view the whole front office sees — needed to plan the calendar and avoid calling the client back to ask what it was even about. The details of the case itself — what the client said about facts, documents, the other side of the dispute — is already privileged content and should only be visible to the people handling that specific case.
What stays out of the general file
In practice that means two levels within the same system: a general client card with contact details and a schedule, visible more broadly — the kind of thing Customer Data provides as one client card with a history of visits and orders — and a separate, restricted level holding the case content, visible only to the assigned team.
Example on assumed numbers — substitute your own: a firm employs 4 lawyers and 2 assistants. Without split access, the content of every case note is visible to 4 + 2 = 6 people on the team. When access to case content is limited to the lawyer handling it and their assigned assistant, the circle shrinks to 1 + 1 = 2 people per case — the rest of the team still sees the fact of the inquiry and the appointment time, but not the content.
Do it yourself: an audit of what ends up in the CRM after a call
- Listen to or read a few recent AI reception summaries and check how much case detail is actually in them.
- Check who has access to those notes in the CRM — only the lawyer handling the case, or the whole team by default.
- Decide which field in the CRM is "general" (visible more broadly), and move only the fact of the inquiry and the appointment time there, without case content.
- Set a rule that the lawyer handling the case reviews an AI reception summary before it becomes an official note in the file.
- Check call recordings — is access open to everyone by default, or limited to people assigned to that specific case.
This audit doesn't require changing your system — it only shows where your access settings drift from what the firm is legally required to do. It's the same kind of review we describe in what can realistically be handed over to a system, and what cannot — professional secrecy is one of the boundaries that convenience can't move. Before you calculate what this kind of order costs, 2026 automation cost ranges show what actually drives the price. We cover a related question — where client data physically ends up during automation — separately in automation and GDPR.
What this looks like when a system separates the fact from the content
Aura's system doesn't decide on its own what counts as professional secrecy — the firm sets that. The system's role is to enforce a split that's already been decided: AI reception and telephony answers the phone and saves a summary with the recording, CRM and automations collect the inquiry in one funnel, while the firm decides who can open the summary's content, and the general fact of the inquiry and the appointment time are visible more broadly in Customer Data. The overall flow:
- 01client calls
- →02note on topic
- →03content stays with lawyer
- →04team sees the fact
Which parts of each case go into the narrower circle, and which into the general calendar, is a decision the firm itself makes — it's a legal decision, not a technical one, and no system will make it for anyone. Just as a reminder about a deadline can become an ordinary task with a responsible person (Tasks), a review of who has access to case notes can be set up as a recurring checkpoint instead of a one-off decision. Weekly AI Reports, similar to what we describe in reporting automation, can show the number of inquiries and appointments — never the content of a case, since that's beyond what anyone besides the handling lawyer can safely see.
Frequently asked questions
Can an AI reception line at a law firm even answer calls from clients?
The laws on the legal profession and on legal counsel don't ban the use of supporting systems — they govern who has access to privileged information and under what rules. An AI reception line can answer the phone and save a summary, provided access to the case content stays as restricted as it would be for a handwritten note.
Is a recording of an AI reception call covered by professional secrecy?
Yes, if it concerns a client's case. The statutory duty of secrecy covers everything an attorney or legal counsel learned in connection with providing legal assistance — the form of the record (paper, a CRM note, a recording) doesn't change the fact that the content is protected.
Does every employee at a firm need access to every note in the CRM?
No, and usually they shouldn't. Access to the content of a specific case is worth limiting to the people handling it, while general data — the fact of the inquiry, contact details, the appointment time — can be visible more broadly, since the team needs it to plan its work.
Does an AI summary need to be checked before it goes into the case file?
Recommended practice for systems built on language models says the model's output should be reviewed by a human before it's used in practice, especially in high-stakes domains. A summary of a conversation about a client's case falls into that category, so the lawyer handling it should review it before treating it as an official note.
What's the difference between attorney-client privilege and legal counsel's professional secrecy?
In terms of what the duty covers — nothing significant. Both laws impose a duty to keep secret everything learned while providing legal assistance, with no time limit; each is just set out in its own professional law — the attorney's in the Law on the Legal Profession, the legal counsel's in the law on legal counsel.
When must the decision about what goes into the CRM be made by the lawyer, not a system?
Whenever it requires judging whether a piece of a conversation is part of professional secrecy or just an organizational fact. A system can enforce a role-and-access split that's already been decided, but the boundary itself — what's case content and what's just a calendar slot — is set by the lawyer handling the case.