TL;DR
- The accepted principle in Israel: a party to a conversation may generally record it. Recording a conversation you are not part of is an entirely different story, never to be approached.
- In a business setting, the accepted and safe practice is notification: announcing at the call's start that it is recorded for service and quality purposes.
- Recordings are personal data: security, access permissions and a retention policy are a management obligation, not a recommendation.
- AI analysis does not change the base rules: it works on the same recordings under the same permissions. The right questions are where the data lives and who accesses it.
Before diving in: we are a technology company, not a law firm, and this page is an orientation map, not legal advice. Exact rules depend on your industry, regulator and circumstances, and specific questions belong with your legal counsel. What we can give: the general map, accepted practices, and the checklist worth bringing to the meeting with counsel.
The basic principle: a party to the call
The accepted starting point in Israel is simple: listening to other people's conversations without their knowledge is a serious offense, but someone who is themselves a party to a conversation may generally record it. A floor recording its own calls with its customers operates, as a rule, in permitted territory. Everything else builds on that base.
Notification: why everyone says "this call is recorded"
Even where recording itself is permitted, the familiar announcement at the start is the standard practice, for three reasons: transparency with customers in a privacy-sensitive era, specific requirements in regulated industries, and the simple fact that an announced recording is worth more, because it can be used with a clear conscience before a customer, a regulator or a court. There is almost no scenario where skipping notification pays.
The recordings themselves: personal data in every sense
- Security: recordings contain personal, sometimes financial and medical details. Encryption and controlled access are the baseline.
- Permissions: not every employee needs every recording. Define who hears what: direct manager, QA, leadership.
- Retention policy: how long to keep and when to delete. Regulated industries have defined requirements; either way, a written policy beats an accidental system default.
- Customer rights: a customer may ask what is stored about them. An orderly response process saves headaches.
What changes when AI analysis is added? Less than it seems
A conversation intelligence layer works on recordings that already exist, under the same permissions and rules. It records nothing new; it makes what is already recorded usable. The right vendor questions are infrastructure questions: where is data stored, is it used to train models beyond your own service, how are permissions enforced, and what happens to recordings when the engagement ends. At Saleso these are questions we expect in every implementation conversation, with the answers documented in the agreement.
Again, deliberately
This page gives a general map and is not legal advice. Regulation changes, industries differ, and your specific circumstances decide. Take the checklist below to your legal counsel, and leave the meeting with a written policy.
The checklist for the meeting with legal counsel
- Is our call-opening notification wording sufficient for our industry?
- What retention policy is required: how long, and what must be kept for audits?
- Who is authorized to access recordings and transcripts, and how is that documented?
- Are there special requirements for sensitive calls (health, finance, minors)?
- What do we answer a customer requesting their own recordings or deletion?
- Does the processing agreement with the analysis vendor cover storage, use and permissions?
Frequently asked questions
May we record a sales call without informing the customer?
The accepted principle in Israel is that a party to a call may generally record it, but in practice notification at the start is the right approach: it is required in some regulated industries, builds trust, and makes the recording safely usable. The exact wording for your industry is set with legal counsel.
How long should call recordings be kept?
There is no single answer: regulated industries have defined retention requirements, and a general business sets policy by operational and legal needs. The important principle: a written, uniform policy rather than an accidental system default.
Does using AI on recordings require additional customer consent?
The analysis works on recordings lawfully collected for the same service and quality purposes, so in most cases it is the same framework. What matters: verify the processing agreement covers storage, permissions and use, and that your notification wording is broad enough. A good question for counsel at the annual review.