AI for mortgage brokers. The chase, handled.

It does the chasing and the remembering. The documents after an appointment, the client who has gone quiet, the fixed rate coming to an end, and the past client nobody has spoken to in two years.

AI for mortgage brokers is the chasing and the remembering, and it stops well short of anything a client would call advice.

Two different things get called AI, and only one of them matters here. The first is automation, which means a job that starts on its own: an appointment finishes, so the document list goes out. The second reads what a client wrote back and answers it in your words, which is what turns a reminder into something people actually reply to.

What it takes off you first

• The documents after every appointment.

  The list goes out the same day, and the reminders keep going until the last payslip is in.

• The client who has gone quiet.

  An application stalls waiting on one thing, and the follow up happens whether or not anybody noticed it stall.

• The fixed rate coming off.

  Every client with a rate expiring hears from you in advance, without anybody building a list first.

• The past clients nobody has rung.

  An annual check in goes to a book that would otherwise only hear from you when they go looking for somebody else.

All of that is work a broker already knows should happen. It happens in the month it should, instead of in the month somebody finally gets to it.

They leak in the gaps. A deal stalls waiting on one document, a fixed rate rolls off without a call, and a past client goes to whoever contacted them first. All three are failures of remembering rather than of advice.

Watch what happens to a document request after an appointment. It goes out on Tuesday. Some clients send everything, some send half, and some send nothing. Working out which is which, and writing to each of them separately, is the job that never quite happens in a busy week.

The cost of that is not an hour. It is a settlement that lands a month later, or a client who refinances with somebody who rang them first. Neither shows up as a missed task anywhere, which is exactly why it keeps happening.

What that costs you

• Settlements that arrive late.

  A file waiting on one document for three weeks is commission sitting still, and the same work spread over a longer month.

• Clients who refinance elsewhere.

  A fixed rate rolling off is the moment your client is most likely to talk to somebody else. Whoever rings first usually keeps them.

• A back book that goes cold.

  Past clients are the cheapest source of new business you have, and they stop being that the moment they stop hearing from you.

The Australian Securities and Investments Commission's guidance on using a mortgage broker tells consumers to expect a broker to stay across their loan, and the brokers who do that consistently are the ones who did not leave it to memory.

Nothing here asks you to change systems. The work happens in the CRM and the tools your business already pays for, and the value is in the handoffs between them rather than inside any one of them.

Your CRM holds the deals, your lodgement platform holds the applications, and your document store holds the files. What none of them does is chase a client on your behalf, which is why a person is still doing that by hand.

Where the handoffs are

• Between the appointment and the file.

  A document comes back by email and somebody saves it into the right folder under the right client.

• Between the CRM and the client.

  The deal sits at a stage waiting on one thing, and nothing tells the client that until a person notices.

• Between settlement and the back book.

  The file closes, and the client hears nothing again until they go looking.

• Between the rate and the calendar.

  The fixed rate expiry is in the system, and nobody is watching it until the month it happens.

Individually each of those takes a couple of minutes. Across a full pipeline they are the difference between a month that settles and one that slips. The audit maps them in your own stack and puts a number beside each one before anything is built.

It gives no advice. It makes no recommendation, it forms no view about what suits a client, and it decides nothing about a loan. Every record it drafts is reviewed and signed by you.

This matters more here than in most industries, because the advice goes out under your name and your credit licence. The automation handles the layer around it and stops at the edge of anything requiring your judgement.

Where it stops, deliberately

• Anything that is advice.

  It will not compare products, suggest a lender or explain what suits somebody. That is yours and it stays yours.

• Your compliance records.

  It can draft from what is already on the file, so nothing is typed twice. What goes on the record and whether it is right stays your decision and your signature.

• Client data going where it should not.

  Payslips, statements and identity documents are not handed to a public AI tool. The builds run on your own accounts with the handling agreed in writing.

Where the work is genuinely repetitive and written down, it runs. Where it is not, it stops and waits for you, and every run is logged so you can read what it did.

The follow ups that only happen when somebody remembers go on a list, and the one costing the most settlements comes off it first. The wording gets approved before anything is built, and it runs watched before it runs alone.

The first one is the document chase, because it is the one holding up the money. The next starts once that one is running.

1. The chasing gets written down properly

Half a morning. What goes out after an appointment, when, and what happens when a client sends half of it. Most brokers have never had this written down anywhere.

2. The job costing you the most goes first

A rough number goes beside each one. The document chase usually wins, because everything downstream of it is waiting.

3. You approve the wording before anybody builds anything

Every message goes out in your name, so it gets written the way you would write it and signed off before it exists as anything but words on a page.

4. It connects to the CRM you already run

Most broking CRMs can already tell another system when a deal changes stage. Nothing gets replaced and nothing gets migrated.

5. It runs watched before it runs alone

For a fortnight, with a person approving each message before it sends. That fortnight finds the client situations nobody predicted, before a client meets one.

6. The next one starts once the first is boring

A job is finished when nobody in the business is thinking about it any more. That is the signal to start the next one, rather than a date on a plan.

Writing down how the chase actually happens takes longer than building it. The first job runs watched inside a fortnight, and each one after it is shorter because the connections already exist.

The order it happens in

• The writing down comes first.

  How a request actually goes out today, including the parts nobody has put on paper. This is the slow half.

• Then it gets built and watched.

  It runs with a person approving each message, long enough to meet the situations nobody predicted.

• Then it runs on its own.

  You hear about it monthly: what ran, what it replied to, and anything that failed and stopped.

The first thing a broker notices is that the chasing stops being anybody's job. What follows that is a month where files stop sitting still, because the reminders went out whether or not anyone had time to send them.

Ask where it runs, whose accounts it uses, what happens to client documents, and what you keep if you stop paying. Those four answers separate a build you own from a subscription you rent.

These are worth asking of anybody, including this one, so the answers given here sit under each question.

• Where does it actually run?

  On your own accounts and a server you can point at, rather than inside a platform you rent. The first one is yours and the second one is not.

• What happens to client documents?

  Payslips, statements and identity documents stay inside systems you control, and are not handed to a public AI tool. Agree the handling in writing first.

• Does anything it sends count as advice?

  Nothing it sends should, and that line is drawn before anything is built. Ask exactly where the automation stops and you start.

• What do I keep if I stop paying?

  A build keeps running afterwards. A subscription stops on the day the paying stops, and you start again from nothing.

• Am I locked into a contract?

  Not here, it runs month to month. Any arrangement you cannot leave at the end of a month is worth a second look.

All of this can also be built in house, and plenty of brokers do it well. The six steps above are the same either way.