What Is Call Recording on a PBX?

What it is, and how it differs from recording on a mobile

Call recording on a PBX is recording that happens on the PBX itself, and not on a device. Every call that passes through a path set up for recording is saved as an audio file, without the representative having to press anything and without an app on the phone.

This is a big difference compared with a recording app on a mobile. There, the recording depends on a particular employee's device, is kept with them, and leaves with them when they go. On the PBX, the recordings belong to the organization, are organized by call, and are accessible to those who were given permission — even a year after the employee changed roles.

And on a cloud PBX there is another advantage: it doesn't matter which device answered. An IP phone on the desk, software on a computer or a SIM extension on a kosher mobile — the call passes through the PBX, so it is recorded in the same way.

Why organizations record

• Quality control — the service center manager listens to a few calls a week and checks that representatives answer properly.
• Training — a new representative learns from real calls: how to handle an angry customer, how to close a sale.
• Documentation — an order given over the phone, a pledge of a donation, agreement to terms.
• Resolving a dispute — "You told me the shipping was free." You listen and you know.
• Protecting the team — when a caller behaves abusively, the recording backs up the representative.
• Analysis — modern systems transcribe the recording and produce a summary and tasks from it. More on this in CRM integration.

How it works behind the scenes

1. You set rules: what gets recorded — for example certain extensions, a service center queue, or calls of a particular number.
2. The call passes through the PBX: the audio of both sides passes through it anyway, so it can keep a copy.
3. The call ends: the PBX closes the file, processes it and attaches it to a record in the call log.
4. Retention: The file is kept for the period you set, and then it is deleted automatically.
5. Access: Anyone with permission can listen to or download the recording from the log.

Note the third step: the recording does not always appear the moment you hang up. In many systems, processing takes time, so the recording is available only after a short wait.

How long to keep recordings

The retention period is a business decision, not just a technical one. Longer means more documentation, but also more sensitive information stored with you and more responsibility for it. A few ways to think about it:

• Service center — A few weeks to a few months is usually enough to check complaints and coach staff.
• Sales and commitments — Keep them at least until the deal is closed and there is no dispute about it.
• Especially important calls — Download the file and save it separately, in an organized folder.

Practical tip: don't set one retention period for the whole organization. Service center calls, management calls and the gemach line shouldn't be kept for the same length of time. That is why good systems let you set up several recording groups, each with its own period.

The law, notifying the caller, and privacy

The accepted practice, and in many cases also the requirement, is to let callers know the call is being recorded. The simple way: a short sentence in the opening greeting — "To improve our service, calls to the service center are recorded." It takes three seconds and avoids awkward situations.

In Israel, as a rule, a party to a call may record it, and it is forbidden to record other people's calls without consent. But the exact rules depend on the type of organization, the field of activity and what is done with the recording — so it is worth checking with a legal advisor what applies to you. This page is a general explanation and not legal advice.

What about privacy? A recording is personal information. Give access only to those who need it, don't send recordings in WhatsApp groups, and set a reasonable retention period. When an employee leaves, cancel their access to the control panel.

Common mistakes

• Recording everything and listening to nothing. A recording is worth something only if someone uses it. Set a routine: a few calls a week, by topic.
• Not recording what matters. You set up recording for the main queue and forget that some calls go directly to the sales manager's extension.
• Looking for a recording a minute after the call and not finding it — because it is still being processed.
• A retention period that is too short, and you find out when a complaint arrives about a call from two months ago.
• No notice to the caller, and then a customer hears that he was recorded and feels wronged.

Recording, monitoring and transcription — what's the difference

The three tools complement each other. In practice, a good service center uses monitoring during an agent's first weeks, recordings to check a sample, and transcription to quickly find the call in which "someone promised something."

Worksheet: retention period for each type of call

Instead of guessing one number, go through the types of calls in your organization and decide for each one separately. This table is a starting point — the numbers are examples, not legal recommendations:

After you fill in the table, each row becomes its own recording group with its own period, and you assign the matching extensions or queues to it. A row marked "not recorded" is just as important: if you don't need a recording, it is better not to have one — less sensitive information to protect.

A helpful question for each row: "If a customer comes in X months from now and claims something about the call, will we need it?" If the answer is yes, X is the minimum.

Who may listen

A recording is sensitive information, so the question "who gets to listen" is as important as "what do we record." The rule: access by role, not by seniority or curiosity. In the users and permissions screen of the control panel, you give each user only the screens they need — someone who doesn't need to hear recordings doesn't see them.

• Service center manager — Hears the calls of their own queue. Not management calls.
• Agent — Usually doesn't listen to recordings alone. If you want them to learn from their calls, the manager sits with them and plays them.
• Accounting — Only collections calls, and only to look into an issue.
• The manager — Everything, but even they shouldn't log in with this user from just any computer.

Three small procedures that save trouble: a recording does not leave the control panel unless there is a documented reason; when an employee leaves, their user is canceled the same day; and once a quarter, go over the list of users and ask about each one — why do they have access?

Wording for a recording notice

The notice should be short, clear, and played before the call begins. Here are a few wordings by type of organization, to insert into the opening greeting:

• General: "Hello, you have reached [business name]. Calls are recorded to improve our service."
• Service center: "Please note that this call is recorded for quality control and handling of inquiries."
• Sales: "So that we can keep to what we agreed with you, this call is recorded."
• Donations line: "This call is recorded to make sure the donation details were taken down correctly."
• Parents' line at an institution: "Calls to this line are recorded. For a personal matter, you may ask to continue without recording." — and then the agent knows to transfer to an extension that is not recorded.

Tip: record the sentence in the voice of the same announcer who recorded the rest of the menu, so it doesn't sound like an add-on. For outgoing calls, the agent says the sentence themselves at the start of the call, because there is no menu before it.

Two examples: a sales review and settling a dispute

Weekly sales review. A furniture store with three salespeople on the phone. Every Thursday the sales manager opens the call log, filters the week's sales queue calls that lasted more than five minutes, and picks two for each agent. She listens with a sheet of four questions: Did the agent introduce themselves? Did they ask what the customer needs before making an offer? Did they state a clear price? Did they sum up the next step? Twenty minutes a week, and after two months all the agents end their calls with "So I'll send you a quote by tomorrow noon." Recordings of especially good calls are saved in a folder for training new employees.

Settling a dispute. A customer of a renovation company claims that a total price was agreed with him, and the company says the price did not include materials. The call was seven weeks ago. The owner searches the log by the customer's number, finds three calls, and listens to the second — ten minutes. In the sixth minute the agent says explicitly, "Without materials, those you buy separately." She downloads the file, saves it in the customer's folder, and invites the customer to listen. The argument ends in one conversation instead of a letter from a lawyer.

What the two examples have in common: a recording that was set up correctly in advance, and someone who knows where to find it. And the opposite: in the second example, a retention period of one month would have left the company with nothing.

How much space it takes

A phone call recording is a small file. Phone audio is limited to call quality, not music quality, so one minute usually weighs between a few dozen kilobytes and half a megabyte, depending on the format. Orders of magnitude:

• A 3-minute call — About the size of one photo from a phone.
• A small service center, 200 calls a day — A few hundred megabytes a month, at most.
• A full year of the same service center — A few gigabytes. Less than one high-quality movie.

The conclusion: space is almost never the reason to shorten the retention period. The reason is privacy and responsibility for information — and that is decided by need, not by the disk.