The Relationship CRM Beside Your Agency System

A CRM for insurance agents organizes the people, conversations, opportunities, and next actions around an agency. An agency-management system owns the operational insurance record. Customermates is designed for the CRM side of that boundary, not as a substitute for policy or claims software.

CRM or AMS: which does an insurance agency need?

An agency-management system typically maintains policies, carrier downloads, documents, claims activity, commissions, and accounting. A CRM focuses on prospective business, client relationships, referral sources, conversations, and sales follow-up. Some insurance suites combine both categories, but the capabilities should still be evaluated separately.

Customermates is a general CRM. It does not replace an AMS, policy-administration system, carrier portal, claims platform, rating engine, or commission ledger.

A supported insurance-sales workflow

Create a deal for a prospective relationship or renewal conversation. Connect it to the client contact, the relevant organization, and the introducer where useful. Configure stages around the commercial interaction rather than carrier processing.

1. Create the prospect context

   Add the person or business and preserve the source of the relationship without copying a complete policy or claims file into the CRM.

2. Configure the sales stages

   Use stages such as “Inquiry”, “Needs discussion”, “Quote prepared externally”, “Customer decision”, “Won” or “Closed”.

3. Add bounded reference fields

   Store a product category, carrier reference, renewal month, referral source, or external AMS identifier when the agency's data policy permits it.

4. Record the next action

   Attach a task to the relevant CRM record. The task has no due date, recurrence, or automatic renewal schedule.

5. Continue insurance operations in the AMS

   Quoting, submission, binding, endorsements, claims, documents, and commissions stay in the system that owns those records.

Renewal follow-up without a renewal engine

A renewal month or external policy reference can help a user filter CRM opportunities and prepare a relationship review. A separately operated n8n workflow can create tasks from a date field. On the cloud, a Mate routine can list opportunities with an upcoming renewal month on a schedule and prepare conversation drafts for review; it uses AI credits and is not a reminder feature. Customermates does not calculate policy terms, start reminder sequences, send bulk renewal campaigns, or prevent a policy from lapsing.

The same boundary applies to claims. A user can record that a relationship follow-up is needed, but Customermates does not accept first notice of loss, maintain the claim file, assign adjusters, calculate reserves, adjudicate coverage, or issue settlement communications.

Cross-sell context and commissions

Custom fields may hold high-level product references selected by the agency. Filtered views can help a user inspect those records. Customermates does not infer coverage gaps, recommend products, score clients, or run cross-sell campaigns.

Commission rates, statements, reconciliation, clawbacks, and revenue forecasting belong in the AMS or accounting system. A custom currency field holding a commission amount does not replace commission accounting.

Individual conversations, AI, and integrations

The managed unified inbox is available from Pro upward. It brings supported individual email and messaging conversations into the CRM, where participants can be associated with contact context. It is not a bulk campaign or sequence tool. Conversations are linked to contacts, not to policies, claims or deals. Self-hosted deployments do not include the inbox.

An authorized external AI client can use supported MCP actions on CRM records. It does not quote insurance, determine coverage, analyze claims, calculate commissions, or replace a licensed professional's review.

Customer-built connections can use the REST API and webhooks, MCP, or the separate n8n integration. The customer owns carrier and vendor contracts, field mapping, permissions, validation, retries, and duplicate handling. There is no native carrier-download, comparative-rater, policy, or claims integration.

Data and deployment boundaries

Keep policy documents, coverage details, health information, claim files, commission statements, and regulated advice in systems approved for them. 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 or GDPR compliance certification.

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.

Frequently asked questions