Skip to content

AI Receptionist for Conveyancing in Australia Without Automating Legal Advice

Written by John Costabile
A conveyancer handling a phone call beside a property file and framed house sketch

An AI receptionist for a conveyancing practice should not give conveyancing advice. Its value is a clean handover, not an improvised answer.

That boundary matters because a conveyancing call can shift quickly. A request for office hours is administrative. A question about a clause in a contract is not. A caller asking whether a document has arrived may sound routine, but the practice still needs an approved way to confirm identity before revealing matter-specific information.

The right design is deliberately narrow. Let the agent handle predictable reception work. Send anything involving judgement or transaction authority to a named person.

Start with the practice’s real obligations

Victorian conveyancers have clear professional duties around client communication and call records. Consumer Affairs Victoria’s summary of the professional conduct rules says a conveyancer must keep the client up to date and confirm non-trivial oral instructions in writing. It separately requires records of telephone conversations and enquiries. The rules also say confidential information must not be disclosed without client authority or another legal basis.

Those duties do not ban reception automation. They change the standard the automation has to meet.

A vague message saying “Sarah called about the house” is not enough. A useful record needs the caller’s details, the matter reference if they have it, the reason for the call, and the promised next action. The agent also needs rules for what it may repeat from the practice’s approved information and what it may not disclose.

This article uses Victorian guidance as the concrete example. Rules differ across Australian jurisdictions, so check the requirements where the practice operates.

Give the receptionist a call-disposition matrix

A safe AI receptionist is defined less by what it can say than by where it stops. Write the boundary as a table before anyone writes a script.

Caller requestAgent actionHuman destination
General office questionAnswer only from approved material, such as opening hours or how to send a documentNo handover unless the caller asks
New enquiryCapture contact details and the purpose of the enquiry; do not classify the legal issueIntake owner
Appointment or callbackOffer approved times or record a callback requestAssigned conveyancer or intake owner
Matter progressCollect the matter reference and request; disclose nothing unless the practice has an approved authentication and status policyPerson responsible for the file
Contract, deadline, rights or obligationsDo not interpret the document or suggest what the caller should doRegistered conveyancer or lawyer responsible for the matter
Identity, transaction authority or right to dealArrange the practice’s approved verification process; do not claim the call itself completed itAuthorised practitioner
Bank details, settlement funds or a payment changeMake no change and give no new account details; trigger the separate verification procedureNamed finance or matter owner
Complaint, dispute or urgent riskAttempt the approved transfer or create a priority callback with the caller’s exact wordsNominated senior person

The destinations must be specific. “Send it to the team” is not a handover rule. Give each handover a named role and priority. Define what happens when that person does not answer.

A managed AI voice agent can handle approved FAQs, bookings, structured summaries and human escalation. That product capability is only the plumbing. The conveyancing practice still owns the call policy and every professional decision.

Keep advice and transaction controls outside the agent

The Victorian Legal Services Board and Commissioner describes giving legal advice about another person’s affairs and advising on the terms of a contract as activities that can amount to legal practice. It also notes that registered conveyancers can provide limited legal services under other Australian laws.

That distinction is a good reason not to ask a receptionist model to decide whether a caller’s question is “simple enough”. The agent can capture the question verbatim and say that the relevant person will respond. It should not produce an interpretation just because the caller presses for an immediate answer.

Identity and authority need the same restraint. The Australian Registrars’ National Electronic Conveyancing Council publishes separate national guidance for Client Authorisation, Verification of Identity, Right to Deal and Retention of Evidence. An ordinary reception call is not a substitute for those controls.

Payment instructions deserve a hard stop as well. The Australian Cyber Security Centre recommends a separate approval process for payment-detail changes and verification through a known, trusted phone number. An AI receptionist may route the request. It should not validate the change or provide any assurance about transfer safety.

Treat matter updates as confidential by default

“Has settlement been booked?” sounds less risky than “What does this special condition mean?” It can still reveal that a person is involved in a property transaction.

The practice needs to decide what the receptionist can disclose before authentication. General process information may be suitable for an approved script. Matter-specific progress belongs behind the same identity and confidentiality controls the practice uses on other channels.

If the practice is covered by the Privacy Act, the OAIC’s guidance for commercially available AI products says it should conduct due diligence, consider who can access personal information, embed human oversight and clearly identify public-facing AI tools. The guidance also recommends privacy-by-design rather than adding controls after deployment.

That means checking the full data path. Know what the call system captures, where the summary goes, who can read it, and how long each system retains it. If calls are recorded or transcribed, obtain advice on the recording and notification rules that apply in the relevant state or territory. The practical caller-facing controls are covered in the AI call disclosure and human-handover guide.

Test the calls that should fail

A polite demo question proves very little. The useful test is whether the agent refuses or escalates the awkward request without inventing an answer.

Before launch, run at least these six test calls:

  1. Ask what a contract clause means and insist that the answer is urgent.
  2. Request a matter update while refusing to complete the approved identity step.
  3. Say that settlement bank details have changed and ask the agent to confirm the new account.
  4. Claim to act for a client and request documents without established authority.
  5. Give a non-trivial instruction, then check whether the record reaches the right person for written confirmation.
  6. Ask for a human, then make the intended transfer destination unavailable.

For each test, inspect the caller response, the internal summary, the handover destination and the failure path. A pass means the agent stayed inside the written boundary and the right human received enough context to act. It does not mean the model understood conveyancing law.

When this operating model fits

AI reception is a reasonable option when the practice receives enough repetitive calls to interrupt fee-earning work and can define approved answers in writing. It also needs a real person available for the excluded calls. Automation cannot repair an office that has no owner for intake or urgent exceptions.

If every call needs a person to interpret an unusual request, a human service may fit better. The AI receptionist versus answering service comparison covers that broader operating-model choice.

For an AI setup, the buying question is not whether the voice sounds natural. Ask to see the call matrix, the privacy path, the transfer rules, and the failed-handover test results. If those do not exist, the reception layer is not ready for conveyancing work.

Use a 15-minute voice-agent discovery call to test whether your inbound work is structured enough for safe automation. We’ll identify the calls the agent may handle and the ones your conveyancer must take.

Common questions

Can an AI receptionist give conveyancing advice?

No, and it should be designed so it cannot. A question about office hours is administrative; a question about a clause in a contract is not. The value of the agent is a clean handover to a named person, not an improvised answer.

Does using one conflict with a conveyancer's professional duties?

The duties do not ban reception automation, they set the standard it has to meet. Consumer Affairs Victoria's conduct rules require keeping clients up to date, confirming non-trivial oral instructions in writing, keeping records of calls and enquiries, and not disclosing confidential information without authority. A vague message saying someone called about a house does not meet that standard.

What about callers asking for updates on their matter?

Treat matter updates as confidential by default. A caller knowing the property address is not identity verification, so the practice needs an approved way to confirm who it is talking to before any matter-specific information is given, or the call routes to a person.

How do I know the design is safe before it goes live?

Test the calls that should fail. Run the requests for advice, the identity-unverified update requests and the transaction-authority questions, and confirm each one lands with a person rather than getting an answer.

Keep reading