CRM features mortgage advisers actually use

Sales pages describe capability. Adoption logs describe reality. If you sat behind an adviser for a fortnight, you would see the same small handful of screens over and over, and a great deal of the platform never touched at all.

This is a rough ranking of what earns its place, and a list of what tends to gather dust, based on how mortgage advice work is actually shaped rather than on how systems are marketed.

The five things used every day

The client record. Not the fancy version — the top of the screen. Name, number, current lender, current rate, expiry date, property address, last contact. An adviser about to pick up the phone wants those seven things in one glance, and how well a system presents them determines how the whole product feels.

The note field. Advisers live in notes. Every call, every lender conversation, every reason a decision was made. A system that makes note-taking fast gets a full history; a system that makes it a three-click journey gets a sparse one, and sparse case histories are how complaints become expensive.

The task list for today. Not the project view, not the board, just what needs doing before six o'clock. If this list is trustworthy it becomes the adviser's working day. If it fills up with automated tasks nobody clears, it is abandoned within a month and never recovers.

Document status per case. Which items are outstanding, which arrived, which were rejected. This is checked constantly, usually just before phoning a client.

Search that tolerates human input. Half a surname, a misremembered postcode, a phone number with spaces. Advisers search far more than they filter, and a fussy search box is a daily irritation.

The three things used weekly

Rate expiry lists. Pulling next quarter's expiring clients is the single most commercially valuable routine in a brokerage, and it happens weekly or monthly rather than daily.

Pipeline by stage, mainly for the Monday conversation about what is stuck.

Templates for client emails and document requests. Used often but edited most times they are used, which is why rigid templates fail. Advisers want a starting point, not a script.

What principals use that advisers do not

Conversion reporting, adviser performance, income against procuration fees due, and file-review sampling. All legitimately important, all invisible to the person writing the case.

This asymmetry matters when you buy. A principal evaluating a system will be impressed by dashboards that no adviser will ever open, and the firm ends up paying for a reporting layer while the daily screens remain awkward. Weight the evaluation towards the people who will be in it eight hours a day.

What tends to go unused

Elaborate workflow automation. Firms configure ambitious rule chains during implementation, then find that real cases deviate constantly and the automation creates tasks that have to be dismissed. A small number of reliable automations beats a large number of clever ones.

Internal chat. Most firms already have a messaging tool and will not move for a CRM.

Marketing campaign modules. Broker platforms usually include something here and it is usually thinner than a dedicated email tool. Firms serious about client communication tend to export and use something else.

Custom fields, past the first dozen. Every implementation adds fields that seemed essential and are now permanently empty. Empty fields are not neutral; they make the record harder to read and they train people to ignore what they see.

Mobile apps, more often than vendors would like. Advisers do use phones for calls and calendars, but keying a fact find on a handset is rare. Check whether the mobile experience matters to your team before paying for it.

Features that quietly matter more than they sound

Permissions granularity. Whether an administrator can see everything, whether an adviser can see another adviser's clients, and whether a departing employee's access can be cut in one action.

Bulk actions. Reassigning forty cases when someone leaves, or updating a status across a set of records, is either a two-minute job or a two-day one.

Undo and audit. Someone will delete something. What happens next is a real differentiator and is never on the feature grid.

Duplicate handling. Joint applicants, clients who come back after three years, and enquiries submitted twice all create duplicates, and the ease of merging them determines whether your data stays trustworthy.

How to find out for your own firm

After six months on any system, ask each user to list the five screens they open most and the five features they have never used. It takes ten minutes each and it produces an unusually honest picture.

Use the answers two ways. Turn off or hide what nobody uses, because visual clutter has a real cost. And check whether anything on the never-used list was a reason you bought the product, because that is a renewal conversation worth having.

Capability across UK broker platforms differs and changes; confirm anything specific with the supplier rather than relying on a general article.