A CRM for Insurance Distribution Relationships

A CRM for insurance companies can support distribution, broker, agency, and commercial partner relationships. It should not be confused with the core systems that administer policies, underwrite risk, handle claims, bill customers, or satisfy regulatory recordkeeping. Customermates serves the relationship layer only.

Where CRM fits inside an insurance company

Insurance carriers and MGAs depend on policy-administration, claims, underwriting, billing, actuarial, document, and regulatory systems. A CRM has a narrower role: managing the people and organizations around distribution, partnerships, and commercial relationships.

Customermates can give a partnership team a structured view of agencies, brokers, service partners, their contacts, and a relationship opportunity. It is not a lighter replacement for a core insurance platform, and it should not hold sensitive insurance operations merely because its fields are configurable.

A practical broker-relationship workflow

Create an organization for a brokerage or agency and connect the relevant business contacts. A deal can represent a commercial relationship such as partner evaluation, onboarding, or a joint distribution opportunity. The deal should not represent a policy, claim, underwriting submission, or commission statement.

1. Create the partner organization

   Add the agency, brokerage, service provider, or other distribution partner and keep its business context in one place.

2. Associate the people involved

   Connect relationship owners, decision-makers, and operational contacts without importing policyholder or claims records.

3. Configure the commercial stages

   Use stages such as “Identified”, “Contacted”, “Due diligence handled externally”, “Commercial review”, “Active relationship” or “Closed”.

4. Add bounded partner fields

   Store non-authoritative values such as partner type, territory, internal owner, relationship status, or an external-system reference.

5. Hand formal controls to the core system

   Appointments, eligibility, contracts, production data, commissions, and regulatory evidence continue in their authoritative platforms.

What belongs outside the CRM

Customermates does not administer policies, accept first notice of loss, assign claims, calculate reserves, adjudicate coverage, perform underwriting, price risk, calculate commissions, collect premiums, issue documents, or maintain actuarial models.

Written premium, loss ratios, risk classifications, policyholder health or financial information, claims evidence, and formal appointment status should not be copied into generic CRM fields unless the insurer has separately designed and approved that data flow. Permissions apply per resource and action, not per field; read access can be limited to records a user is assigned to. Customermates carries no insurance compliance certification.

For partner-performance analysis, keep the authoritative measures in the insurance data platform. A bounded reference or a manually reviewed summary can support a conversation, but a CRM view is not the regulatory or financial report.

Messaging, AI, and system connections

The managed unified inbox is available from Pro upward for supported individual conversations. Participants can be associated with contact context. The inbox is not a policyholder campaign engine, and conversations are linked to contacts, not to policies, claims, underwriting files or deals. Self-hosted deployments do not include messaging.

An authorized external AI client can use supported MCP actions on general CRM records. It does not become an underwriting, claims, actuarial, or regulatory agent. Sensitive insurance data should not enter an external client or model path without independent approval of the complete data flow.

A customer-built connection can use the REST API and webhooks, MCP, or the separate n8n integration. The insurer owns source authority, field mapping, permissions, validation, retries, duplicate handling, and operational controls. There is no native policy-administration, claims, underwriting, carrier, or actuarial integration.

Deployment and commercial fit

In the managed cloud, the application database runs in the AWS Frankfurt region; hosting and other subprocessors, including US providers, are listed on the subprocessors page, and a DPA is available. This is not a GDPR or insurance certification, and Customermates holds none. Self-hosting the open-source core lets the operator choose application and database infrastructure, but connected services and the surrounding control environment remain separate.

Starter includes the core CRM. Pro adds the managed unified inbox and one connected account per user. Self-hosted deployments have the Starter feature set and do not include the unified inbox. See the pricing page for current plan details.

Choose Customermates when a distribution or partnership team needs a configurable relationship CRM beside established insurance systems. Choose a specialist platform when the product itself must run policy, claims, underwriting, rating, billing, commission, or regulatory operations.

Frequently asked questions