Private contact on a joint mortgage file: check every send route

After the responsible owner approves a joint applicant's revised contact instruction, give the support team a way to check every route that could send a message. Updating the person's CRM record is one action. It does not demonstrate that a queued reminder, an old email conversation or a separate portal notification will use the same instruction.

This guide is for Australian brokerage owners defining that implementation task for assistants and covering staff. It starts with an approved instruction. It does not decide what may be withheld from another applicant, assess financial abuse or establish a safe-contact plan for an individual. Those questions need the brokerage's designated owner and appropriate specialist process.

Keep the contact decision with the responsible owner

The MFAA's October 2026 resource announcement describes guidance on recognising vulnerability, responding appropriately, maintaining professional boundaries and finding specialist support. Make that wider response part of team preparation; a message-routing worksheet cannot replace it.

The Australian Banking Association's September 2026 financial-abuse guideline discusses separate communications for joint parties, updating contact information across databases and checking preferences as circumstances change. It is voluntary bank guidance, not a universal brokerage rule or permission for an assistant to change a channel. Its relevance here is the operational question: where else could an old contact instruction still be used?

Before assigning the task, name the person who approves contact arrangements, the system owners who can implement them and an available backup. The procedure should specify which affected messages support may hold while seeking urgent owner review. It should also identify time-sensitive communications that must be escalated rather than silently cancelled. Immediate safety concerns follow the established emergency or specialist procedure, ahead of this administrative exercise.

Turn the approved instruction into a send check

Use a controlled instruction reference, not a fresh copy of the customer's disclosure. Record the person affected, the permitted method and timing, any explicit restrictions, the approving owner, and when the instruction needs review. Keep actual contact details in the approved system.

Then list the routes that exist in your brokerage. A small practice might use three; another may have several systems and an external provider. Do not assume that the example below describes your software. Ask its owner to identify the field or instruction each message actually uses.

Example starting inventory for an instruction-to-send check

Route to inspect	Question for the owner	Useful completion evidence
Individual CRM contact	Which person's record is being changed, and could a household default override it?	Authorised change confirmed against the relevant person and instruction reference.
Queued appointment reminder	Does this already-created item use the current contact field or a stored recipient?	Queue item checked; permitted hold or correction recorded before release.
Document-request email	Would replying reuse an old recipient list, quoted message or attachment?	Fresh draft checked for approved recipients and content, without forwarding the disclosure.
Portal notice or SMS	Does the portal maintain its own contact record or automatic notification?	System owner confirms the applicable setting and any unresolved limitation.
Lender or other external sender	Who must request and confirm the corresponding arrangement?	Separate handoff reference and actual confirmation, or a clearly open dependency.
Covering colleague	Can they find the current practical instruction before sending?	Colleague demonstrates the permitted next action using a fictional record.

Add an owner and next review point to every unresolved row. “CRM updated” should not close a row about a different system. Equally, an assistant sending an internal request does not demonstrate that an external organisation has changed its records.

The joint-applicant document worksheet remains useful for deciding which requested item belongs to which person. This check addresses a different dependency: whether the next message will follow the instruction already approved for that person.

Rehearse the old-recipient problem

Fictional exercise: mock applicant A has an owner-approved instruction to use their nominated individual email during a specified contact window. The instruction excludes phone calls, voicemail and SMS. It concerns A's contact arrangements; it does not authorise changing applicant B's record or deciding B's access to information.

The trainee receives an invented system map, a dummy queue and the approved instruction. They find that A's CRM person record has been corrected. An appointment reminder created earlier still contains the household address. A draft document chase is a reply to an old conversation involving both applicants. The correct response is to identify those particular items and apply only the holds or preparation steps allowed by the procedure, with the remaining decision returned to the named owner.

The system owner then supplies a synthetic preview showing the reminder's corrected recipient. The trainee prepares a new document-request draft with the approved recipient and only the necessary content. Neither result is tested by sending a live message to a customer.

Now reveal a second notification setting: the fictional portal still plans to send an SMS when the document task is reopened. The exercise remains incomplete. The worker records the unresolved portal route, its owner and the instruction governing the pending task. They should not improvise a different customer channel simply to make the queue look clear.

Copy a route completion record

Use one record per actual send route. These fields capture implementation evidence, not the customer's underlying disclosure:

• Route and recipient source: [system, queued item or conversation reference; owner-confirmed source of the recipient].
• Instruction and check: [restricted instruction reference and version; checked time].
• Permitted action: [approved hold, preparation or change; implementing owner].
• Returned evidence: [what was actually checked or confirmed; controlled result reference].
• Still unresolved: [remaining route or external confirmation; owner and next review point].

Keep the record in the approved restricted location. Add routes identified by your system owners; completing these example fields does not establish that every route in your brokerage has been found.

Give cover staff the instruction they need

For the final part of the exercise, hand the file to a covering colleague. Provide the approved operational instruction through the designated restricted record. Do not put the disclosure narrative, a relationship allegation or copied personal correspondence in the general handover board.

Ask the colleague which message they could prepare next, which route remains unresolved and who must decide. If the colleague sees only a generic “contact updated” note, improve the handover. A useful result names the instruction version and the outstanding route without spreading the underlying story.

Use the file-note method to distinguish the customer's request, the owner's decision, the action actually completed and the remaining exception. Do not overwrite the history to imply every route changed at the same time.

Close the implementation task precisely

Return a short reconciliation: routes checked, changes confirmed, messages still held under instruction, and external confirmations still awaited. The owner decides the next contact action. Avoid a global “safe” or “confidentiality guaranteed” status; the record establishes only the checks actually performed.

Include a review point for the current instruction and a way to route any new preference to its owner. The support worker should not use a prohibited callback or message simply to check whether the restriction still applies.

When hiring, assess whether an assistant can follow the approved instruction, inspect a recipient source and leave an unresolved dependency visible. Describe the systems, change permissions and manager coverage in your brief. You can discuss a clearly scoped client-contact support role with Mortgage Talent; specialist safety, privacy and legal decisions remain separately assigned.