Client experience management in mortgage broking is the work of deciding what a borrower receives, understands and has to chase from first enquiry to the reviews after settlement. The brokerage then checks that it delivers those things. You manage it by naming who owns each handover, promising only the contact your team can keep and moving every settled client into an agreed review schedule.
A client can settle on a well-chosen loan and still remember your brokerage for the three calls nobody returned. The loan result and the service around it are measured separately, so each needs its own owner and its own check.
What Client Experience Management Changes
Managing the client experience shifts your review of each file from the loan result to the client’s side of the process. Instead of asking whether the loan settled, you ask what the client received, what they understood at each stage and what they had to chase. A client who has to ask twice for an update has found a gap in the process, even when the loan outcome is good.
Loan Outcome and Client Experience Compared
| What you check | Loan outcome | Client experience |
|---|---|---|
| The result | A suitable loan that settles | A client who knew where the file stood at every stage |
| What the client receives | The loan, the rate and the repayment | Updates, explanations and callbacks at the times you promised |
| What the client understands | The product they chose | The current stage, what they still need to supply and when you will contact them next |
| What the client chases | Nothing, if the loan settles | Every update they had to request and every callback that came late |
| Who owns it | The broker who gives the credit assistance | A named person at each handover |
Treat the two columns as separate results. Incorrect: “The loan settled, so the client was well served.” Correct: “The loan settled, and the client always knew which stage it had reached.” Predictable communication and reliable follow-through are what the client experiences while the loan outcome is still unknown.
Map the Journey From Enquiry to Settlement
Map the journey by writing down the question a client asks at each stage, then give that stage a named owner, a contact trigger and an escalation route. The map below uses hypothetical roles for a brokerage with one broker and one client-service officer. Your deal-stage controls in mortgage pipeline management supply the stage changes that trigger each contact.
Hypothetical Client Journey Map
| Stage | The client’s question | Owner | Contact trigger | Escalation route |
|---|---|---|---|---|
| Enquiry | Can you help me, and what happens next? | Client-service officer | A new enquiry by phone, email or web form | Broker calls if the enquiry needs credit advice before the first meeting |
| Discovery | Which loans suit me, and what will you need? | Broker | The discovery meeting ends | Broker books a second meeting if goals or finances are unclear |
| Evidence collection | What’s still missing? | Client-service officer | A document arrives, or a requested document is overdue | Broker calls when a missing document holds up submission |
| Submission | Has the application gone in? | Broker | The application is lodged with the lender | Client-service officer confirms lodgement if the broker is unavailable |
| Lender assessment | Why haven’t I heard anything? | Broker | The lender requests information, issues a decision or misses its usual turnaround | Broker contacts the lender’s business development manager (BDM) and tells the client what was asked |
| Settlement | When do I get the keys, and what do I sign? | Client-service officer | Loan documents issue, or a settlement date is booked | Broker contacts the lender’s settlement team if documents or funds are late |
Lender delays need their own route because the broker cannot control them. When an assessment runs past the lender’s usual turnaround, the owner chases the lender, then tells the client what was asked and when the next contact will be. The client learns about the delay from you rather than finding it by chasing.
Every handover in the map needs a backup owner. When the client-service officer is on leave, write the name of the person covering each open file into the customer relationship management (CRM) system. A handover without a named backup leaves no one responsible for the client’s next update.
Set Service Commitments the Team Can Meet
Turn the journey map into three commitments the client can hold you to: an acknowledgement, a progress update and a promised callback. Set each one at a level your team can meet in a heavy month, because the client judges you on the commitments you keep. The hypothetical standards below suit a two-person team.
- Acknowledge every enquiry, document and message by the end of the next business day, naming who will deal with it.
- Update the client whenever the file changes stage, and at least weekly while it sits with the lender.
- Call back by the time you promised, or contact the client before that time to give a new one.
Adjust the commitments for case complexity. A self-employed borrower, a construction loan or one of your vulnerable customers can need more frequent contact and a single named contact person. Record any agreed change in the CRM so whoever covers the file knows what the client expects.
Separate your chosen service standard from conduct the law requires. Your update rhythm is a brokerage decision, while complaint handling has rules of its own. The Australian Securities and Investments Commission’s Regulatory Guide 271 Internal dispute resolution (RG 271) expects a complaint to be acknowledged within 24 hours, or one business day. It requires an internal dispute resolution (IDR) response to a standard complaint within 30 calendar days.
A useful update states the present stage, the outstanding action and the next contact. It makes no promise about the lender’s decision. This hypothetical message meets that standard:
Hi Sam, your application is with the lender’s credit assessor. They’ve asked for your last two payslips, so please upload them through the portal today. Once they’re in, I’ll send them to the assessor. I’ll update you by 2pm tomorrow, or sooner if the assessor replies.
Keep Settled Clients in the Review Process
At settlement, agree the ongoing contact with the client and record it in the CRM. Note the consent they gave, the channel and how often they want to hear from you, and the broker responsible for their reviews. Book the first home loan review before the file closes, so the relationship has a next step.
Check the consent rules for each channel. Under the Spam Act 2003, a marketing email or SMS needs the person’s consent and a working unsubscribe option. The Australian Communications and Media Authority’s unsubscribe fact sheet says an unsubscribe request must be actioned within 5 working days. Australian Privacy Principle 7 on direct marketing also requires that the client knows how to opt out, as the Office of the Australian Information Commissioner’s direct marketing guidance explains.
Track My Trail’s Refinance Finder shows which settled loans to review first. It builds a review queue of active loans settled more than two years ago, ordered by settlement age and balance, with an estimated LVR (loan-to-value ratio) for each. A settlement-month filter supports recurring review cycles, and a reviewed mark returns the loan to the queue after 90 days.
The broker still runs each review. Check the client’s current situation and goals, then contact them through the channel they agreed to, using the client review template. Record the contact and any advice in the CRM. If the review leads to a refinance recommendation, your best interests duty applies to that credit assistance.
Keeping a settled client in a review rhythm also protects the trail on their loan, which is the income client lifetime value measures over the life of the relationship.
Recover a Missed Update and Improve the Process
When a client complains about a missed update, treat it as a complaint, fix the handover that failed and record what you changed. RG 271 defines a complaint as an expression of dissatisfaction where a response or resolution is explicitly or implicitly expected. A client doesn’t have to use the word “complaint” for one to exist.
Hypothetical Missed Handover
In this hypothetical, the lender’s valuation comes back lower than expected while the client-service officer is on leave. No backup owner is recorded, so the client hears nothing for six business days. The client then emails the broker to say they feel ignored and want to know whether the purchase can go ahead.
- Acknowledge the complaint the same day. The broker replies, apologises for the silence and promises a call by 11am the next morning.
- Record it in the complaints register with its date received, the issue and the person responsible. RG 271 requires firms to record all complaints and track the progress of each one.
- Assign the action. The broker asks the lender’s BDM about the valuation and works out the options, such as a larger contribution or a review of the valuation.
- Complete the callback by the promised time. The broker explains the valuation, the options and the next step, and agrees when the client will hear next.
- Confirm in writing what was done and what happens next, and ask whether the client is satisfied. Under RG 271, a complaint resolved to the client’s satisfaction by the end of the fifth business day needs no written IDR response. The client can still ask for one, and a hardship complaint always needs one.
Then fix the cause. The update went missing because no one covered the file during leave. The brokerage adds a rule that every open file has a named backup owner before anyone goes on leave.
Hypothetical Service Review Across Three Periods
Compare the same measures over successive review periods to find the changes worth keeping. RG 271 expects firms to analyse complaint data regularly to find where service delivery needs to improve. The figures below are hypothetical.
| Measure | Period 1 | Period 2 | Period 3 |
|---|---|---|---|
| Files settled | 24 | 22 | 26 |
| Clients who chased an update more than once | 7 | 3 | 2 |
| Callbacks made after the promised time | 9 | 4 | 4 |
| Most common feedback theme | No contact during valuation | Slow document requests | Slow document requests |
In this example, the backup-owner rule started after period 1. Repeat chasers fell from 7 to 3 and stayed low, so the rule is worth keeping. Late callbacks fell but then held at 4, and feedback moved to slow document requests. The next change belongs at the evidence collection stage, such as one combined document list sent after the discovery meeting.
Run this review at the end of every period and keep only the changes the measures support. Your next step is to pick the handover that produced the most repeat chasers last period and give it a named backup owner.
