Deployed in more than 40 countries. See EbixEvolution by market →

Brokers reviewing a client account together

Ebix Meridian

One file for every client.

Prospects, clients, and contacts on a single record in EbixEvolution, with the risk details, policies, claims, ledger, and documents that follow attached to it for the life of the relationship.

Request a demo

See policy management

the module, end to end

Everything about the client, in one place

The client file is the spine of EbixEvolution. Every other module writes to it and reads from it.

Prospects and clients

Every prospect starts as a record that becomes the client file the moment the first policy binds, with nothing re-entered along the way.

Contacts and relationships

Directors, finance contacts, site managers, and group structures, so the right person is on every document and every renewal conversation.

Risk details on the file

Locations, vehicles, activities, turnover, and the facts each class needs, captured once and reused across every quote and policy.

The full client view

Policies, claims, invoices, receipts, documents, diary, and notes on one screen, so anyone who picks up the phone has the whole picture.

Notes and correspondence

Calls, emails, and meetings logged against the client, the policy, or the claim they concern, and kept for the life of the relationship.

Diary and follow-ups

Renewal invitations, outstanding documents, and promised call-backs sit on the file as tasks with owners and dates.

Segments and marketing lists

Clients by class, insurer, renewal month, or producer, for renewal campaigns and cross-sell without an export.

Permissions by role

Who can see, edit, invoice, and receipt is set by role, and every change to the file is recorded.

Inside the module

The client file, the risk capture, and the diary as a broker sees them day to day.

The client file

Policies, claims, invoices, documents, and diary on one screen, with the contacts and risk details behind them a click away.

Every policy and claim on the record
Ledger balance and open items
Diary, notes, and correspondence

ebixevolution.com/clients

Risk capture

The facts each class of business needs, captured once against the client and reused on every quote, policy, and schedule that follows.

Locations, vehicles, and activities
Class-specific question sets
Reused across quotes and renewals

ebixevolution.com/clients/risk

Diary and renewals

Renewals, follow-ups, and outstanding documents as dated tasks with owners, on the file and on the team's work queue.

Renewal invitations diarised automatically
Tasks by owner and due date
Nothing falls between people

ebixevolution.com/diary

Actual product screens, shown as configured and white-labeled for RedGram Wealth Management, an investment advisory firm running on Ebix Meridian. Your firm gets the same portal under your own brand.

Illustrative screens · EbixEvolution captures to follow

Service team working from the client file

Anyone can pick up the phone.

When a client calls, whoever answers sees the same file the account executive works from: what is on cover, what is outstanding, what was promised, and what the last conversation was about. Service does not depend on one person's memory.

The whole picture

Cover, claims, balance, and documents on one screen.

The last conversation

Notes and correspondence logged where they belong.

The next step

Open tasks with owners and dates, visible to the team.

Built for the long relationship

Brokerages keep clients for years and decades. The client file is designed to carry that history without becoming unreadable: the current position first, the full record underneath.

Current position first

What is on cover and what is outstanding, before the history.

History kept, not archived away

Every past policy, claim, and invoice remains on the file.

Group structures

Parent and subsidiary entities linked, with programmes viewed at either level.

Producer and team assignment

Every client has an owner and a service team, and the work queues follow.

See your own clients
on the file

Bring a few real accounts to the demo and see how the file reads once the history is on it.