Referral Partner Updates for Mortgage Brokers, Drafted With AI

Draft a short update at each case milestone, share only what the client has agreed in writing, and let AI write the wording from your case-stage notes while you read each message before it goes. Add one weekly digest per agent. Cover status and next step; leave out figures, income and advice.

Estate agents ring brokers for one reason: they want to know whether a sale will complete and what is holding it up. Answer that before they ask and the calls stop. The same workflow also shows partners that you are organised, which is the sensible reason to do it, rather than any inducement. Keep the updates about the transaction itself.

Follow me on Instagram@sagnikteaches

What an agent actually needs to know

An agent selling a property wants dates, blockers and the next action. They do not need the buyer's income, credit history, deposit source or the lender's reasoning. Sorting information into three bands before drafting keeps you on the right side of confidentiality.

Connect on LinkedInSagnik Bhattacharya

When the blocker is itself personal ("the applicant's payslips are missing"), translate it: "We are waiting on some paperwork from the buyer." The agent needs to know the delay exists, not the reason.

Subscribe on YouTube@sagnikteaches

Consent: the part to settle before any template

The borrower is your client, not the agent's. Ask for permission in the first meeting, in writing, naming the agent, the milestones and the channel. Illustrative wording for your fact find or engagement paperwork:

Sharing progress with your estate agent
With your agreement, we will tell [agent name] at [agency] when
your mortgage application reaches these stages: application
submitted, valuation booked, valuation done, offer issued, and
any delay that affects the completion date. We will not share
your income, credit information, or reasons. You can withdraw this
at any time by telling us. Please tick one:
[ ] I agree   [ ] I do not agree

Record the answer in your case system. A "no" means no updates, and a missing answer means no updates too. Check your data-protection rules for any further requirement, and ask your compliance adviser if you are unsure. If your CRM lets you add a consent field, make updating the agent impossible when it is empty. HubSpot for mortgage brokers shows how stage and referrer fields fit together.

Step 1: map your case stages to a short list of updates

If your case system has eight to ten internal stages, agents probably care about five or six of them. Map yours (illustrative; use your own names).

Note the careful phrasing of "agreement in principle". It is not an approval and does not guarantee a mortgage; do not let AI call it "approved". The same caution runs through what mortgage brokers can automate with AI, and what stays advice.

Step 2: build templates with AI, then fix them by hand

Write one template per update, in your voice, once. Ask the AI to draft, then edit. A prompt that works (no client data needed):

Write a 70-word email from a mortgage broker to an estate agent
saying that the mortgage application for their sale has been
submitted to the lender today. Friendly and brief. Use the
placeholders [agent first name], [property address], [date],
[your name]. Say what happens next (the lender books a valuation)
without promising a date. Do not mention the buyer's finances.
Never say "approved".

An illustrative output:

Subject: [property address]: application submitted

Hi [agent first name],

A quick update: the mortgage application for [property address]
went to the lender today, [date]. Next, the lender will arrange a
valuation. I'll let you know the date as soon as it's booked so
you can help with access.

Thanks,
[your name]

What you would fix: the template is fine, but add your direct number, and check "as soon as it's booked" matches what you do. If you only update weekly, say that instead. A promise to tell the agent "as soon as" a milestone happens is one you will break on a busy Friday.

The full set: six templates to build

1. Introduction after the first call

A short note confirming you are working with the buyer and how best to reach you. It carries no financial information. Good opening: "I'm [name], the mortgage broker helping [buyer first name] with the purchase of [address]." Include the agent's preferred contact route if they have said.

2. Agreement in principle

One line on whether the buyer is ready to make an offer. Avoid the word "approved" or any figure. The buyer's affordability is not the agent's business, and it is your job to say only what has been agreed with the client.

3. Application submitted

The example above. Add the next step but never a date you do not control.

4. Valuation

Two variants: booked, with the date and access request; and complete, with the neutral line "The valuation is done; we are waiting for the lender's next step." If the valuation is lower than expected, do not describe the number. Say "the valuation has raised a question that we're working through" and call the agent, because a revised price affects negotiation and you should speak to the client first.

5. Delay notice

Subject: [property address]: small delay

Hi [agent first name],

The lender has asked for some extra paperwork from the buyer, so
the offer will take a little longer. I'm chasing it today and will
update you on [day]. If your seller has a deadline, please let me
know so I can flag it to the lender.

Notice what it does not say: no reason, no blame, no promise of speed. It gives the agent a next date and an invitation to raise a deadline.

6. Offer and completion readiness

"The mortgage offer has been issued to the buyer and their solicitor. Funds are expected to be ready for the completion date, subject to the legal work finishing." Hold the phrase "subject to" in every completion message: you do not control the legal side.

Tone: warm, brief, free of reassurance you cannot back

A good partner update is short and factual, ends with what happens next, and does not sell. Avoid "everything is on track" unless it demonstrably is. Say "on schedule" only against a date you hold. A before and after:

Before: Great news! Everything is going brilliantly and we should
        have this wrapped up very soon. Don't worry about a thing!
After:  The application is with the lender. The next step is a
        valuation, which they book. I'll update you when it's
        scheduled.

The "before" is friendly and unhelpful, and it contains two promises ("very soon", "don't worry") that you cannot keep. The "after" is the same warmth with nothing to retract.

Step 3: the weekly digest

For an agent with several cases, a single weekly email beats a stream of one-liners. Build it from your CRM or case sheet: one row per case, with only band-one and band-two information. Paste an anonymised list (property reference, stage, next step, expected date) into the AI and ask for a digest.

Below is a list of cases for one estate agent. Write a short weekly
email: one line per property giving the stage, the next step and
the date if one exists, sorted by completion date. Use only the data
given. Do not add reasons for delays or any information about the
buyers. Start with one sentence saying how many cases are moving
normally and how many are waiting on something.

[property ref | stage | next step | date]
Case 14 | Application submitted | Valuation to be booked | -
Case 9 | Offer issued | Legal work | 28 Nov
...

An illustrative result:

Hi [name], here is this week's summary of your cases with us.
Three are moving normally and one is waiting on a lender query.
Case 9: offer issued; legal work under way; target 28 Nov.
Case 14: application submitted; valuation to be booked.
...
Call me on [number] if anything here affects your timetable.

Check each row against your CRM before sending. If the AI adds a reason or a promise that you did not provide, remove it; the instruction not to is there because models love to fill gaps with plausible detail.

Three agents, eleven live cases: the time sums

Picture a broker (illustrative) with eleven live cases from three agents, sending updates by hand: about 15 messages a week at roughly 6 minutes each, so around 90 minutes. With templates and a Friday digest, the broker sends two or three milestone messages a day at about 2 minutes each after editing, plus three digests at about 8 minutes including the CRM check. That is nearly the same total in the first month because checking takes time, but agent phone calls to the broker fall as digests answer their question first. The honest benefit is fewer interruptions, not hours saved.

Count calls for four weeks before and after. If agent calls do not fall, the digest is not telling them what they need. Ask two agents what they would have asked and add it, if it is shareable.

What to put into the AI tool, and what to leave out

The updates mention a property and a buyer, so decide in advance what the drafting tool may see. The simplest rule: the AI gets the template instructions and an anonymised reference, and you add names and addresses in your own email or CRM afterwards.

• Safe to paste: the stage name, the next step, a date, a property reference such as "case 14" and the prompt text.
• Keep out: buyer names, income, employer, credit details, lender decisions, account numbers and anything from the fact find.
• Tool settings: use a business account, switch off training on your inputs where the vendor offers it, and keep chat history short. Check the vendor's current terms rather than relying on this sentence.
• Built-in options: if your CRM or case system has its own drafting assistant, read its data terms the same way before you let it see case notes.

With placeholders, the draft can be pasted into your email program and filled in there, which keeps personal data out of the AI tool entirely.

One case from enquiry to completion, with the messages filled in

Here is an illustrative case (a first-time buyer, a flat, an independent agent) with the real wording at each point, so you can see how short the updates are. The property reference is "case 14".

Seven short messages over a month, none longer than three sentences. Nothing in them would embarrass the buyer if they read over the agent's shoulder, and that is the best test of what is safe to share. Day 20 shows the discipline: the delay is reported, the reason is not, and the next update has a date.

Fitting the tone to the kind of agent

One template does not suit every agent. Adjust the length and channel and leave the content rules alone.

A pre-send check that takes forty seconds

Whoever or whatever drafted the message, read it once with these questions.

1. Is this the right agent, and the right property? (Look at the reference, not just the address.)
2. Does the client's consent record say yes for this agent and this stage?
3. Is every fact in the message in the case record today?
4. Does it contain any financial or personal detail, or a reason for a delay?
5. Does it say "approved", "guaranteed" or "definitely"? Remove those.
6. Does it give a date I control, or only one the lender or solicitor controls?

The classic failure is a stale or mismatched message: an update for case 14 sent to the agent for case 9, or the same digest sent after a case has fallen through. The first check, matching the reference to the agent, catches most of it.

Using AI to read case notes and suggest the update

If your case notes are in a system that has its own AI drafting, you can have it propose the milestone message from the latest note. Keep this to systems whose data terms you have read. The prompt pattern is the same: give it the stage and the allowed statements, and forbid anything outside them.

Allowed statements for agent updates:
- application submitted (date)
- valuation booked or done (date)
- offer issued (date)
- delay with next update date
Latest note (internal, do not quote): "Lender asked for two more
payslips, chased broker's client, valuation done Tuesday."
Task: Write the agent update. Use only the allowed statements.

The illustrative reply should say that the valuation is done and that the lender has a small query, with an update date. If it mentions payslips, the instruction was not strong enough: tighten the forbidden list and send nothing until the output passes the check above.

Five partner-update mistakes and the symptom of each

• The over-eager digest. A weekly email that lists every internal stage floods the agent. Symptom: agents stop reading it. Fix: show only milestones and next steps.
• Promising speed. "We'll have the offer by Friday." Symptom: the agent chases you on Friday afternoon. Fix: give the lender's stated service levels as an expectation, or no date.
• Leaking a reason. The AI adds "because the buyer changed jobs". Symptom: it appears in a draft you never asked for. Fix: forbid reasons in the prompt and delete them on review.
• Ignoring a "no". A client declines sharing but the CRM sequence still runs. Symptom: an agent mentions something you never told them. Fix: make the consent field gate the sequence.
• Using one voice for every message. A cheerful tone on a delay reads as flippant. Fix: keep a separate calm template for delays.

How to tell whether the updates are earning their keep

Track three numbers for a month: calls and messages from agents asking for status, the time you spend on updates, and the number of cases where an agent was surprised by a delay. Success looks like fewer status calls, roughly flat or lower time after the first fortnight, and no surprises. If surprises persist, a stage is missing from your list. If status calls do not fall, the digest is not telling them what they need, so ask two agents what they would have asked.

Keep a log of corrections too. A line such as "removed a reason for a delay from the day-20 message" each time it happens shows you which instruction needs tightening. After a month the same corrections stop appearing, which is the sign the templates are ready for any further automation.

Edge cases that need a person

• The client withdraws consent. Stop at once, note the date and do not send the next digest row for that case.
• A lender declines. Tell the client first. Then tell the agent only what the client agrees: "The buyer is reviewing their options." Never explain the decline.
• The agent asks about the buyer's affordability. Answer "I can't discuss the buyer's finances; I can tell you where the application stands."
• A chain problem. If another party's sale is delaying completion, say so in neutral terms and leave solicitors to coordinate the chain.
• A rate or product change. It is client business. Do not mention it.

Keeping partner updates clean of inducements

Updates are service on a transaction, but a broker who produces special reports, gifts or free marketing for agents who send the most cases may be in a different area of law. Rules on referral payments and things of value exist in many markets; the RESPA Section 8 checklist for loan officers shows how one such rule looks at AI-made content, and your compliance adviser decides what applies to you. Keep the update stream identical for every agent, whatever they send you.

Setting up and checking it works

1. Write the consent wording and add a consent field to your case record.
2. Draft the six templates with AI and edit each by hand.
3. Send every update for a month as a draft that you read before it goes.
4. Keep a short log of anything you had to correct, and add it to the prompt.
5. After a month, ask two agents whether the updates help and whether anything is missing.
6. Only then consider automating a single milestone, such as "application submitted", with a person able to stop it.

If your CRM already sends stage-based emails, check what it says against the bands above. For the client's side of the same journey, see can AI keep mortgage clients updated during an application, and for the stages before the first update, from enquiry to fact find. If you would rather set the templates up alongside your case system, that is what my AI implementation consultation covers. Start with the consent line, though; nothing else works until that is in place.

Questions about keeping referral partners updated

Do I need the client's permission to update the agent?

Yes, as a safe default. Get the client's agreement, ideally in writing at the start, to share named milestones with the named agent. Without it, the information belongs to the client and the broker's duty of confidentiality applies. Check your data-protection obligations and keep a record of the consent.

Should AI send the updates automatically?

Not at first. Let AI draft, and have a person read and send each message until your templates have run cleanly for a month. Automating a message that goes to a third party about a client's finances needs consent, accuracy checks and a way to stop it.

How often should I update an agent?

Update at milestones, not on a timer, plus one weekly digest covering all of their cases. Agents need to know when something changes what they should do; a stream of reassurance with no news is noise.

Can I thank agents with gifts or content?

Be careful. In some markets rules on referral payments and inducements restrict what a broker may give a referral source, including services at special rates. Keep updates about the transaction and check any perk with your compliance adviser first.

Further reads

• ChatGPT for Mortgage Brokers: Emails and Case Summaries, Not Advice — Emails and case summaries without drifting into advice.
• Mortgage Broker Social Media With AI: A Month of Compliant Posts — A month of social posts with an advertising check.
• Best AI Tools for Mortgage Brokers at Each Stage of a Case — Tools for each stage of a case.
• Choosing a Mortgage CRM With AI Built In: What Actually Matters — Pick a CRM that can gate updates on consent.
• Can Claude Read Payslips and Bank Statements for a Mortgage Case? — Handling payslips and statements safely.
• Alarm Installation Business Marketing: Contracts and Referrals With AI — A handover offer for maintenance contracts, partner sheets for property agents and brokers, and a claims check that keeps every message honest.
• How to Get More Home Inspections: Realtor Referral Emails Written With AI — Three emails for agents (introduction, thank-you, quarterly check-in) with AI prompts and drafts, consent points to check and a sheet that tracks every booking.
• AI Tools for Loan Officers: CRM, Follow-Up and Compliance Checks — A CRM-first method for loan officers: compliance fields, guard-railed follow-up prompts, a pre-check step and a log, with no rate quotes from AI.
• How Can AI Help Physiotherapy Clinics Write Referrer Updates? — Turn a clinician's own bullet points into a clear referrer update, with templates for first, progress and discharge letters and a review step.
• Private Duty Home Care Referral Sources: Follow-Ups Drafted by AI — A warm-touch schedule, privacy-safe templates and a one-sheet tracker let AI draft follow-ups for discharge planners, care managers and solicitors.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: your own CRM and case-management stage names; your data-protection and advertising rules, which you must check directly; general professional practice.