No time for a live demo?  ·  Questions? Call (312) 715-8977

For claim managers

A claims CRM for claim managers who need to see which files have stalled

A claim manager does not work one file. You answer for all of them: which ones nobody has touched, who is carrying too many, and whether a claim moved forward because the work was done or because someone clicked a stage. CRM For Claims puts those answers on the claims list, the Tasks page and each claim’s own history.

Get Pricing

The short version

What a claim manager needs from a claims CRM

A claim manager needs three things from a claims CRM: a list that shows which files have gone quiet without opening each one, a way to see and move one person’s workload, and a history on every claim that says who did what and when. Everything below is a screen that already exists in CRM For Claims, not a report someone has to build.

The question Where the answer is
Which claims has nobody looked at lately? The claims list turns a row red once you have not opened that claim for a number of days you choose. One filter, "Show only those who require attention", hides everything else.
What is on my own desk today? The claims list filter "Projects with active tasks for ME", and the company Tasks page filtered to due today, overdue or high priority.
What is one rep carrying? The claims list filter "Show user's projects" for their files, and the Tasks page filtered by person for their open work.
Who moved this claim, and when? The claim's Records screen: every stage entry and exit, task, file and change, stamped to the minute with a name, filterable by person.
What reached a stage this month? The Projects Categories Report: pick a stage and two dates, get every claim that entered it in the range.
How many contracts did the team sign? Sales Dpt. Performance: signed contracts for the period, split by Primary Representative, lead source and type of loss.

Stalled claims

How the claims list shows which files need attention

Every time you open a claim, the CRM records that you opened it. When the number of days set on your user record passes without you opening it again, the row turns red on your claims list. The number is set per person, from 1 to 29 days or Never, and it is 7 for a new user. A manager who reviews files weekly and a rep who should touch theirs every two days can have different clocks.

  • Red is personal. If your access lets you see every claim in the company, a row only turns red for you when you sit on that claim’s project team or have an open task on it. Without that rule a manager’s whole list would be red on the first day.
  • Closed work stays quiet. A claim in a closing stage such as Completed / Closed or Cancelled never turns red.
  • Open tasks can count too. A per-user permission makes a claim red whenever that person has an active task on it, even if they opened it yesterday.
  • One filter, one pile. “Show only those who require attention” set to Yes hides every claim that is not red, so Monday morning starts with a list rather than a scroll.

The same list filters by any of your stages, by Active, by Favorites, by one user’s projects and by a date range, and the filtered result prints with Print Selected Filter. The stages are the ones your office writes, as described in how the claims pipeline is set up.

Workload

Seeing each person’s workload and handing claims over

The company Tasks page shows the work across every claim, filtered by due today, high priority, overdue or with notes, by person and by period. That is how you see one rep’s pile without opening their claims one at a time.

Changing the Primary Representative

When you change who represents a claim, the CRM lists the outgoing person’s unfinished tasks on that claim, with due dates and anything overdue marked, and offers to move them to the new representative. Every task is ticked; untick one and it stays with its current owner. Completed tasks are never moved. If more than one person takes the role, you pick who receives the tasks.

Tasks that follow a role

Tasks created by a stage can be assigned to a role instead of a named person, so the next one lands on whoever holds that role today. When someone leaves, you change the role, not every stage. How that works is on automations and tasks.

The wider question of what happens to a file when someone leaves mid-job is covered in reassigning a claim when someone leaves, and the question of who owns a claim once the contract is signed in who owns the claim after signing.

Control

Stopping a claim from moving before the work is done

A stage on a board only tells you where somebody put the claim. Three settings on each stage make it tell you where the claim really is, and they are checked on the server rather than hidden in the interface.

  • Task gating. A stage can refuse a claim that still has incomplete tasks, with a message naming the reason.
  • Exclusivity. A stage can be marked exclusive, or given a list of stages it must never sit beside, so a claim cannot be Cancelled and Scheduled at the same time.
  • Who may move it there. Each stage is open to an access level, or to a ticked list of named users. A stage only a manager should approve is one setting.

Access to screens and reports is set the same way, person by person. The detail is on roles and permissions.

History

Finding out who changed a claim, and when

When a homeowner says nobody called, or a carrier says a document never arrived, the answer is on the claim’s Records screen. It is one timeline in eight categories, among them Stages, Tasks, Files, Project Changes and Finance. Each row carries the date and time to the minute and the name of the person responsible, or System when the action was automatic. A stage writes a row when the claim enters it and another when it leaves, and a file row names the folder it went into.

Filter the timeline to one person and you see everything that person did on the claim. That is the review a manager actually needs after a complaint, and it takes one filter rather than an afternoon of asking around.

Numbers

The reports a claim manager brings to the weekly meeting

The KPI page reads the same claims, invoices and expenses the team enters, so there is no separate spreadsheet to reconcile. Three reports do most of a manager’s work:

  • Projects Categories Report lists every claim whose latest entry into a stage you choose falls between two dates. It answers “what reached final invoicing this month”.
  • Master Report shows the period for the whole company: projects created, contracts signed, approvals, deposits, overhead, completed and cancelled. Each line says which date it counts by, and Previous and Next step the whole report back or forward by one period.
  • Sales Dpt. Performance splits signed contracts by Primary Representative, lead source and type of loss, and prints to PDF.

Each report is granted to people one by one, so a claim manager can have the pipeline reports without the balance sheets. The full list is on reporting and KPIs.

Honest limits

What this does not do for a claim manager

  • Red means “you have not opened it”, not “nothing happened”. A rep can work a claim every day and it still turns red on your list if you have not opened it in your set number of days.
  • No spreadsheet export. The claims list prints; it does not export to Excel or CSV.
  • Reports are not emailed on a schedule. A report runs when somebody opens it.
  • An automatic task is due in seven days. A different deadline means editing the task after it appears.
  • Stage automation is on the Professional plan. Essentials includes claim pipelines, tasks and team permissions. Both are on the pricing page.

For the rest of the product, see the features overview.

FAQ

Frequently asked questions

Straight answers about who we serve, what we automate, and how to get started.

Bring your Monday morning list

Book a demo and we will set a red-row clock, filter a claims list down to the files that need you, and change a Primary Representative so you can see exactly which tasks follow.

Contact us
Call (312) 715-8977