What Is a CRM and How Do You Connect It to the PBX?

What a CRM is

The letters CRM come from the English Customer Relationship Management. Simply put, it is a system in which every customer has a card: name, phone numbers, address, what they ordered, what they asked for, what was promised to them and when they were last spoken to. Instead of the information being scattered among notes, spreadsheets and the secretary's memory — everything is in one place, and everyone on the team sees the same picture.

The word "customer" here is broad. In a nonprofit it is a donor, in a yeshiva it is a parent or an alumnus, in a service center it is a subscriber, and in a store it is someone who bought once and may come back. What they all share: the relationship with them is built over time, and a lot of it goes through the phone.

And that is exactly where the problem of most CRM systems lies: they don't know what happens on the phone. The agent talks with a customer for ten minutes, and then has to remember to open the card and write a summary. In most cases this doesn't happen, or happens in three words. Connecting the CRM to the PBX closes that gap.

How a PBX and a CRM talk to each other

The connection between telephony and a computer is called CTI in the professional world — Computer Telephony Integration. The idea is old, but it used to require special cards in the computer and a cable from the PBX. In a cloud PBX the connection goes over the internet, through two channels:

• An API — the CRM "asks" the PBX: which calls were there today? What was the route of a particular call? Where is the recording? And it also asks it to do things — dial, send an SMS.
• Webhook — the PBX "notifies" the CRM the moment something happens: a call came in, a call ended.

Through the API the CRM receives the full call record from the call log: who called and from which number, to which line, through which menu and queue the call passed, who answered, how long they waited and how long they talked, and the recording itself. That is much more than an agent would write by hand, and it is accurate — with no "I think it was on Tuesday."

How the system knows who is calling

Every call arrives with a caller ID — the number it was dialed from. The CRM takes the number and searches for it in the customer cards. Found? The card pops up on the agent's screen, sometimes even before they pick up the handset. Instead of "Hello, who am I speaking with?" the agent opens with "Hello Avraham, how is yesterday's order?"

A few things worth knowing about this search:

• A blocked number — if the caller blocked their caller ID, there is nothing to search for. The card won't pop up, and the agent will ask as usual.
• Several numbers per customer — a customer who calls once from home and once from a mobile needs both numbers on their card.
• A shared number — an office or family where several people call from the same line. Here the card shows everyone associated with the number.
• Format — 050-1234567, 0501234567 and 972501234567 are the same number. A good system normalizes them; otherwise the search fails.

AI call transcription and analysis

Here a modern CRM already does something no secretary had time for. After the call ends and the recording is ready, the system transcribes it — turns the speech into text — with speaker labels: what the agent said and what the customer said. Without such labels, a transcript is a block of words from which it's hard to tell who asked for what.

Artificial intelligence runs on the transcript, analyzes the call and returns:

• A summary — a few lines: who called, what they wanted, what was agreed.
• Topics — an order, a complaint, an account inquiry, a donation, a technical question. This way you can see at the end of the month what people actually call you about.
• Follow-up tasks — "Send a quote by Thursday," "Call him back after he checks with his wife." These tasks become follow-ups and reminders on the card, so that no promise falls between the cracks.

It's important to understand what this is not: it is not a person listening to every call, and it is not perfect. A transcript of a call with background noise, fast speech or switching between languages can miss words. So the summary is a tool for the agent — saving them most of the writing — and not a replacement for their judgment. The original recording always remains, for anyone who wants to hear exactly what was said.

The first call and the next call

The best way to understand the value is to follow one customer. Suppose someone calls an office supply store for the first time. The number is unfamiliar. The agent answers, understands that it's a school that needs a printer for the teachers' room, and promises to send a quote.

On the first call — after the call ends, the system pulls the call record and the recording from the PBX, then transcribes and analyzes. From the call it identifies who the customer is — by the name they gave — and creates a customer card automatically, with the summary, the topic ("Quote — printer") and a follow-up task. The agent didn't type anything.

On the next call — a week later, the same number calls again. This time the screen doesn't show just a number, but the customer's name, and next to it the summary of the previous call and the open task. Even if a completely different agent answers, they know right away: "Ah, the school with the printer — did we send the quote?" The customer doesn't have to explain everything from the beginning, and that is exactly what they remember from the service.

Over time the card fills up: all the calls, all the recordings, all the summaries. A manager who opens the card sees the whole history of the relationship in a minute.

Dialing and SMS from inside the card

The connection also works in the opposite direction. Click to Call: the agent clicks the number on the card, and the PBX first calls them — on their phone or app — and when they answer, it dials the customer and connects. There is no typing and no wrong digits, and the call goes out from the business's number and is logged automatically on the card.

In the same way you send an SMS from the card — a confirmation, a reminder, an address — from the business number, and the message is saved in the customer's history next to the calls.

What you gain, and what to watch out for

• The agent knows who is calling before they say hello.
• No call is forgotten — follow-up tasks become reminders.
• Continuity — any agent can pick up where the previous one left off.
• Less writing — the summary writes itself.
• A management picture — what people call about, who comes back, where things get stuck.

And what to check: privacy — recordings and transcripts are sensitive information, and it's worth limiting who sees them. Notification — it is customary to tell callers that the call is being recorded. And recording quality — a good transcript starts with a clear recording, meaning good headsets and a stable connection.

One customer, three calls: a full example from start to finish

To see all the parts working together, we'll follow one customer of an air-conditioning installation business in Bnei Brak, over three calls in one month. The names are made up; the process is real.

First call — Sunday, 10:20. A mobile number that doesn't appear on any card calls the main line. The agent's display shows only the number. They answer as usual, and the call is recorded like every call on this line. The caller introduces himself: "Hello, this is Friedman from Chazon Ish Street, I need a quote for an air conditioner for the living room, about 40 square meters." The agent asks a few questions, and promises a quote by Tuesday.

After the call ends, the system pulls the call record from the PBX (who called, to which line, who answered, how long they talked) and the recording, and transcribes it with speaker labels. An excerpt from the transcript looks roughly like this:

• Customer: This is Friedman from Chazon Ish Street, I need a quote for an air conditioner for the living room.
• Agent: About how many square meters is the living room?
• Customer: Forty. And we already have an electrical outlet from the old air conditioner.
• Agent: Excellent. I'll send you a quote by Tuesday, and if you approve it we'll schedule a measurement visit.

The AI runs on the transcript and returns: Summary — "New customer, Friedman, requests a quote for a living room air conditioner of about 40 sq m, an electrical outlet exists." Topics — quote, installation. Follow-up tasks — "Send a quote by Tuesday" and "Schedule a measurement visit after approval." Since the number was not familiar, a new customer card was created with the name the customer gave, the number he called from, the summary, the recording and the tasks. The agent didn't type a word.

Second call — Wednesday, 4:05 PM. The same number calls again. This time a different agent answers, who wasn't on the first call. Their display shows not a number but "Friedman — Chazon Ish", and below it the previous summary and the open task "Send a quote" — which was already marked as done on Monday. The agent opens: "Hello Mr. Friedman, did you receive the quote?" The customer confirms, and wants to schedule the installation. They set it for next Tuesday morning. After the call the analysis adds a second summary to the card ("Approved the quote, installation scheduled") and a new task: "Call the customer two weeks after installation to make sure everything is fine."

Third call — two weeks after the installation. This time no one calls in. In the agent's task list a reminder pops up, born from the analysis of the second call: "Call Friedman back — post-installation check." The agent clicks the number on the card, the PBX dials them, and then the customer. The customer is satisfied, but mentions a slight drip from the indoor unit. This call too is recorded, transcribed and analyzed, and the analysis produces a task for the technician. No one wrote a note, and no promise was forgotten.

Notice what the connection did here: on the first call it created the card, on the second it recognized the customer and showed the context, and on the third it took the initiative — reminding the agent to do something the customer hadn't asked for, but exactly what turns an occasional customer into a regular one.

What the agent sees on the screen

When we say "the card pops up," it's worth knowing what exactly appears. A typical CRM screen connected to a PBX has four areas, and most of them fill in on their own:

1. The call line — who is calling (the name, if identified, or just the number), which line they called (for example "Service line" rather than "Sales line"), and through which menu or queue they arrived. This is what lets you answer "Hello, service" and not "Hello?"
2. Customer details — name, additional phone numbers, address, permanent notes ("Only speaks after 5:00 PM," "Longtime customer").
3. The latest summary and open tasks — the lines the agent really reads in the three seconds before "Hello." What was agreed last time, and what is still open.
4. History — all the calls and messages, from newest to oldest, with the recording next to each call and the option to open the full transcript.

Below all this sit the buttons: dial, send an SMS, add a note, create a task manually. During the call the agent can add a word or two, but most of the writing is done afterward, automatically, from the transcript.

A tip from the field: this screen is only worth something if it's open. An agent who works with two screens — the phone on one side, the CRM on the other — or with one screen large enough, makes use of the card. An agent who has to search for the window while the phone is ringing will answer without reading.

What passes through the PBX's API

Everything described so far relies on information the CRM receives from the PBX through the API. These are the main items that pass through it, taken from the call record:

In the opposite direction, commands pass through: "Dial the agent and then the customer," "Send an SMS from the business number." On our side, the PBX's API is under construction, and the CRM we built is its first user. Anyone who wants to connect their own system — talk to us.

Privacy and consent: what's important to know

Connecting a CRM collects more information about each customer than ever: a recording, a word-for-word transcript, a summary and tasks. This is sensitive information, and there are a few general principles worth adopting regardless of the exact law that applies to you:

• Notify about the recording — a short message at the start of the call ("This call is recorded for service purposes") is the accepted practice. Someone who doesn't want to be recorded can ask not to be, and you should know in advance what you'll tell them.
• Limit who sees it — not every agent needs to hear every recording. Permissions by role: an agent sees the cards they handle, a manager sees everything.
• Don't keep everything forever — set a retention period for recordings and transcripts. Information that no longer serves a purpose is just a risk.
• Be careful with especially sensitive information — credit card details, or health or family matters mentioned on a call, now sit in searchable text. Think about whether you need them on the card.
• Let the team know — agents should know that their side of the call is transcribed too. Most will work better for it, but they need to be told, not left to find out.

Rule of thumb: the more the system stores, the more order you need. A good CRM integration comes with a written policy of a line or two — who sees what, and how long data is kept.

Existing CRM or built-in CRM — how to choose

Do you already have a system your team knows? Or are you starting from scratch? Both ways are legitimate, and here is an honest comparison:

There is also a common middle path: keep the existing system for accounts and inventory, and let the phone CRM manage the calls, summaries and tasks — with the phone number as the shared key between the two.

Checklist before connecting a CRM

A successful integration starts with simple questions, not with technology. Go through the list before you begin:

1. Where are your customers today? Excel, a notebook, an old system. You need one list with a name and phone number, in a consistent format — this is the basis for identification.
2. Which lines are recorded? Transcription and analysis only work on a call that was recorded. Decide which recording groups are included.
3. Who needs to see what? Agents, manager, bookkeeping. Set permissions before there is any data in there.
4. What happens to an unanswered call? A decision: should a "call back" task open automatically, and for whom.
5. Who closes tasks? A reminder that nobody marks as done turns into noise. Appoint someone responsible.
6. Shared numbers — an office or a family with one line. Decide how to display them.
7. Recording notice — word it, and record it in the line's greeting.
8. A trial week — turn it on for one queue or one agent, read the summaries, and only then expand.

The last item is the important one. In the first week you will find that the analysis understands "order" and "price quote" very well, but invents a topic for a ten-second call with a wrong number. Filtering out calls that are too short from the analysis is a small adjustment that saves a lot of noise.