CRM for Insurance Agents in Israel: What It Must Hold

A CRM for an insurance agent has to hold far more than contacts: every product each client holds with each insurer, renewal dates, expected commission, powers of attorney and the advice documents behind each sale. Israel has dedicated agent systems that cover most of this. A custom CRM pays off mainly when an agency needs a process, report or integration they do not provide.

This article describes systems and documentation requirements at a technical level. It is not legal or regulatory advice.

What does an insurance agent's CRM have to hold?

In a general CRM a deal closes and drops off the screen. For an insurance agent, closing is where revenue starts: the policy renews, commission is paid for years, and family members join. The data model is different:

• Household - client, spouse and children, because products are sold to the whole family.
• Product per insurer - the insurance company, line (general, life, health, pension), policy number, start and renewal dates.
• Expected versus received commission - without both fields, an unpaid commission is invisible.
• Powers of attorney and authorizations - when given, what they cover, when they expire.
• Advice documents and records - linked to the product the advice was about.
• Service requests and claims - with status and date, so whoever covers for you on holiday sees what is open.
• Lead source - to learn which channel brings clients who stay, not only clients who sign.

I covered matching commissions between policy, payment and expected amount in detail in insurance commission reconciliation.

Which dedicated insurance-agent systems exist in Israel?

These are systems marketed explicitly to insurance agents. Each description is what the vendor states on its own site (checked October 2026); none publishes a price.

What separates them is not the feature list but depth: what the clearing-house import looks like in practice, which commission reports can be produced, and whether you can export your own data in full. Test those three in a demo on a real portfolio, not on sample data.

What regulation requires you to document - the facts

These points directly shape what the system must store:

• Advice document. Under agents-and-advisers circular 2018-10-6 ("Advice document - amendment"), a copy of every advice document given to a client, including the record of data received from the clearing house and the clearing-house file number, is kept by a pension insurance agent for at least seven years from delivery. Draft circular 2025-3, published on gov.il, keeps the same period.
• Pension clearing house. Any license holder registered in the agents-and-advisers register can open an account. An information request carries an authentication code the client generated, as proof that a power of attorney exists. Access is through a web portal or a B2B interface.
• Har HaBituach. An agent with a specific authorization from the insured can view that person's insurance products. Its terms of use state that no database of any kind may be created from information obtained through the site. If the plan includes an automated import of Har HaBituach data into a CRM, settle that question with a lawyer before building.
• Amendment 13 to the Privacy Protection Law took effect on 14 August 2025. It narrows the duty to register databases, adds a duty to notify the Authority about a database holding especially sensitive information on more than 100,000 people, and lets the Authority impose administrative fines.

When is a dedicated system enough, and when do you need a custom CRM?

A dedicated system is enough for an independent agent or a small agency whose process matches the one the system assumes. It already understands insurers, lines and the clearing house, and rebuilding all that from scratch is money you do not need to spend.

A custom CRM, or an extension around the existing system, pays off when one of these holds:

1. The agency runs its own sales process - a call center, campaign leads, rule-based lead routing - that the system does not model.
2. You need a commission or profitability report the system does not produce, and someone rebuilds it in Excel every month.
3. Another system has to be connected: accounting, WhatsApp Business, website forms or telephony.
4. The agency wants full ownership of its data and code, with no per-seat licensing.

In most cases I see, the answer is not to replace the dedicated system but to build around it: lead intake, commission matching, reports and reminders. That is what I described in automation for insurance agencies. The general build-versus-buy comparison is in custom CRM vs off-the-shelf.

How much does a custom CRM for an insurance agency cost?

A custom CRM or internal management system costs $5,000 - $28,000 and takes 3 - 8 weeks, per my pricing page. What moves the price inside that range:

• The number of integrations, and how many require work against a vendor's interface.
• Migrating data from an existing system, especially de-duplicating clients.
• Role-based permissions: agent, manager, call center, back office.
• Commission and profitability reports, which are usually the hardest part.

An extension around an existing system usually lands at the low end, because the data model already exists.

What to have ready before you choose or build

• A full export of your current data, even if it is a spreadsheet.
• The list of insurers and lines you work with.
• A real commission report from each major insurer.
• A description of your current renewal process: who calls, when, and what gets recorded.
• The list of people who need access, and what each may see.

Sources

• Har HaBituach - FAQ and terms of use (Capital Market Authority)
• Pension clearing house - Q&A for agents
• Privacy Protection Authority - Amendment 13 guide