AI voice assistant for business: when it makes sense, what it costs and what the law says
When an AI voice assistant that answers phone calls makes sense, what the AI Act and the GDPR require from 2 August 2026, a ready-made greeting to copy, per-minute prices and the break-even point.
The phone rings when the hairdresser has scissors in hand, the mechanic is under a car and the physiotherapist is in the middle of a treatment. A customer who can’t get through often looks for the next business on Google Maps. An AI voice assistant picks up such a call, answers simple questions and books an appointment.
Here I write about when an AI voice assistant makes sense for a business, what the AI Act requires from 2 August 2026 and what the GDPR says about recording calls. You will also find a ready-made greeting, per-minute prices from providers with a Polish voice and a calculation of how many calls a day it takes for this to pay off.
I am not a lawyer, and this text is not legal advice. I describe the legal situation as of 24 October 2026. If health data or an unusual use case is involved, consult a lawyer or a data protection officer about the deployment.
What an AI voice assistant can and can’t do
A voice assistant is a program that picks up a call, converts speech to text, understands the question and answers in a synthetic voice. It handles these well:
- repeated questions: opening hours, prices of basic services, directions, payment methods,
- booking, rescheduling and canceling appointments, if it has access to your calendar or booking system,
- taking requests: name, phone number, car make, description of the fault,
- calls after hours and on weekends.
After the call, the appointment can land in the calendar by itself and the customer can receive a confirmation text message. I do this kind of system integration as part of process automation.
Don’t entrust the assistant with complaints, unusual quotes or conversations with an upset customer. In a medical practice it should not assess symptoms, and in an urgent case it should transfer the call to a human.
When it makes sense: a practice, a garage, a salon
The assistant pays for itself when calls come at moments when you can’t pick up:
- Hair or beauty salon. Most calls are a question about a free slot, and the assistant books the appointment right away.
- Auto repair shop. The mechanic won’t pick up in the middle of a repair. The assistant collects the car’s details and a description of the fault and books an inspection or diagnostics.
- Physiotherapy, dental or veterinary practice. Reception serves the patient at the desk, and the assistant takes over booking and canceling appointments.
When there are few calls or you pick up almost all of them, the assistant won’t pay back. An automatic text message after a missed call, with a link to online booking, is enough then. I set it up as part of the SMS API service, and my Haloskop system sends such a text message after a missed call. I describe a similar calculation for a chat on a website in the guide Is an AI chatbot on a website worth it.
AI Act: the caller must know they are talking to an AI
Since 2 August 2026, Art. 50 of the AI Act, that is, Regulation (EU) 2024/1689, has applied. According to paragraph 1, an AI system that talks directly to people must be designed so that the person knows they are talking to an AI, unless this is obvious. A natural voice on the phone is not obvious, and the European Commission stresses that this exception must be interpreted narrowly.
The information must be clear and distinct, given at the latest at the first interaction (Art. 50(5)). On the phone, that means the first sentences of the greeting, not a mention a minute into the call.
I checked whether the EU Digital Omnibus, that is, Regulation (EU) 2026/1744 published on 24 July 2026, moved the deadline. It did not. The Omnibus mainly postponed the deadlines for high-risk systems (to 2 December 2027 and 2 August 2028), and under Art. 50 it gave time until 2 December 2026 only for the technical marking of AI-generated content (paragraph 2) in systems placed on the market before 2 August 2026. That is an obligation of the creators of generators, not of a company that answers phone calls.
Formally, the obligation under paragraph 1 rests on the provider of the AI system, but the customer will blame your company, so listen to the greeting yourself. Violating Art. 50 carries fines of up to EUR 15 million or 3% of total worldwide annual turnover (the higher amount counts), and for small and medium-sized businesses the upper limit is the lower of these amounts. I write more in the guide AI chatbot and the AI Act.
GDPR: recording and transcribing calls
The assistant processes personal data in every call: phone number, voice, name, sometimes the reason for the appointment. The caller must be informed about recording or converting the call to text at the moment the data is collected, in accordance with Art. 13 GDPR. Among other things, the caller should learn:
- who the data controller is and how to contact them,
- for what purpose and on what legal basis you process the data,
- who else receives it (the assistant provider, the telecom operator, the AI model provider) and whether it goes outside the European Economic Area,
- how long you keep recordings and transcripts,
- what rights they have, including the right to lodge a complaint with the President of UODO (Urząd Ochrony Danych Osobowych, Poland’s data protection authority).
Nobody will listen to all of this over the phone. The transparency guidelines, endorsed by the European Data Protection Board, allow a layered approach. In the call you state the controller, the purpose, information about rights and whatever might come as a surprise, that is, the recording and the conversation with an AI. You pass on the rest through a link to a website or in a text message.
The basis for recording is usually the company’s legitimate interest (Art. 6(1)(f) GDPR), for example documenting what was agreed. You process the booking data itself in connection with the contract the customer asks for (point (b)). Also consider whether you need recordings at all: a note is often enough to book an appointment, and recordings deleted after a few days are a smaller risk than a year-long archive.
Easy to forget:
- A data processing agreement (Art. 28 GDPR) with the provider and the list of its subprocessors. A Polish provider may use an AI model or speech synthesis from a US company.
- Health data. The reason for a visit to a physiotherapist or doctor may be health data (Art. 9 GDPR). The assistant shouldn’t ask about symptoms, and you should discuss the deployment with a data protection officer.
- Calling with an offer. A call with a commercial offer requires the customer’s prior consent (Art. 398 of the Electronic Communications Law, Prawo komunikacji elektronicznej).
A ready-made greeting to copy
The greeting combines the AI information with the first layer of GDPR information, works for any caller regardless of gender and lasts about 25 seconds. Replace the details in brackets.
Assistant greeting (recording and transcription):
Hello, this is [company name]. You are speaking with an AI assistant, that is, a computer program, not a human. The call is recorded and saved as text so that I can book an appointment and answer your questions. The data controller is [full company name]. Information about data and the rights that callers have is available on the website [website address]/privacy, and I can also send it to you by text message. To speak to a team member, just say “team member”. How can I help?
Version without recording (only a note is kept):
Hello, this is [company name]. You are speaking with an AI assistant, not a human. I will save a note from the call that is needed to book an appointment. The data controller is [full company name], details at [website address]/privacy. How can I help?
Text message after the call (second layer of information):
[Company name]: thank you for calling. The call was handled by an AI assistant and was recorded. Who processes your data, for what purpose, for how long and what rights you have: [link]. Questions about data: [email].
Put the full information from the list above under the link. Test the greeting on three people from outside the company: if any of them doesn’t know afterward that they spoke to an AI, the greeting is not clear enough.
Per-minute prices and where recordings end up
As of 20 October 2026, net prices from the providers’ price lists. I converted dollars at the average rate of the National Bank of Poland (NBP) from that day (1 USD = PLN 3.8959).
| Provider | Price | What it covers | Where the data is |
|---|---|---|---|
| Polish providers with a minute package (examples from price lists of 20.10.2026) | approx. PLN 500–1,000/month with 500 min, each additional minute approx. PLN 0.80–1.10, setup from PLN 0 to approx. PLN 3,000 | a ready-made assistant with a Polish voice; in the pricier packages setup, support and domestic telephony | according to the providers, recordings or processing in the EU, details in the data processing agreement |
| ElevenLabs (ElevenAgents) | USD 0.08/min (approx. PLN 0.31) + AI model + telecom operator | a platform for building it yourself, supports Polish | USA by default, EU only on the Enterprise plan |
| Retell AI | USD 0.07–0.31/min (approx. PLN 0.27–1.21), depending on the model and voice, + operator | a platform for building it yourself, supports Polish | USA (according to the Retell team, May 2026) |
With the minute pool fully used, a minute in the Polish packages costs approx. PLN 1–2 net. Foreign platforms are usually cheaper per minute, but they are building blocks: someone has to build the script and connect a Polish number and the calendar, and transferring data to the USA requires a legal basis. Ask every provider where the recordings and transcripts are stored, who its subprocessors are and whether recording can be turned off.
How many calls a day it takes to pay off
I calculate how many appointments the assistant has to save to cover its cost. A saved appointment is a call that nobody would have answered, after which the customer would have gone to a competitor.
Assumptions (plug in your own): 22 working days a month, 30% of calls go unanswered because you are working with a customer, and every third missed call is a customer who won’t call back. Then each call a day yields 22 × 0.3 × 1/3 ≈ 2.2 saved appointments a month.
calls per day = monthly cost of the assistant ÷ profit per appointment ÷ 2.2
Profit is the amount left after costs, not the price of the service.
| Business | Monthly cost | Profit per appointment | Appointments to save | Break-even point |
|---|---|---|---|---|
| Hair salon | PLN 500 | PLN 60 | approx. 8 | approx. 4 calls a day |
| Physiotherapy practice | PLN 1,000 | PLN 100 | 10 | approx. 5 calls a day |
| Auto repair shop | PLN 1,240 (PLN 990 + setup spread over a year) | PLN 250 | approx. 5 | approx. 2–3 calls a day |
The result depends most strongly on the share of missed calls. If you answer 9 out of 10 calls, the multiplier falls to approx. 0.7, and the salon already needs about 12 calls a day. Then check the minute pool: 12 calls a day of 2–3 minutes each is 530–790 minutes a month, more than the 500 in the cheapest packages.
Calculate the time savings separately: 10 calls a day of 3 minutes each is approx. 11 hours a month, but that is a gain only if you spend this time on customers.
Before you buy anything, spend two weeks recording the number of calls, missed calls and people who called back. That will tell you more than the provider’s calculator.
Summary
An AI voice assistant makes sense when you often can’t pick up the phone and most callers ask about an appointment and prices. From 2 August 2026 it must say at the start of the call that it is an AI, and when recording you must give the information from Art. 13 GDPR. Before signing a contract, calculate the break-even point and check where the recordings end up.
If you want me to run the numbers for your company, write to me. As part of the AI Act Package from PLN 490 net, I will add a “you are talking to an AI” notice to the chat on your website, label AI-generated content where the law requires it, and prepare a clause in your privacy policy and instructions for your team. I reply within 24 hours, and new clients get a 20% discount on their first order.
Frequently asked questions
Yes. From 2 August 2026, Art. 50 of the AI Act requires the person to know this at the latest at the first interaction, which in practice means at the start of the greeting. The Digital Omnibus of July 2026 did not move this deadline.
Consent is not the only possible legal basis: businesses often record calls on the basis of a legitimate interest, for example to have proof of what was agreed. You must, however, always inform the caller about the recording at the start of the call and give the key information from Art. 13 GDPR, and make the rest available on a website or in a text message.
For booking, rescheduling and canceling appointments, yes; for assessing symptoms, no. A conversation in a medical practice easily touches health data, so the assistant should ask only about what is needed for the booking, and it is worth discussing the deployment with a data protection officer.
According to price lists from 20 October 2026, Polish packages with a ready-made assistant cost from PLN 499 net a month for 500 minutes, and versions with deployment and support about PLN 1,000 a month plus about PLN 3,000 upfront. Foreign platforms charge from a few to a few dozen cents per minute, but someone has to build and connect them.
A call with a commercial offer requires the customer’s prior consent to such contact, in accordance with the Electronic Communications Law (Prawo komunikacji elektronicznej). If an AI conducts the call, it must also say that it is an AI from the very first words.
Related services
Have a similar project?
Describe what you need and I’ll send a quote within 24 hours. New clients get 20% off their first project.


