Do you need a CRM to use an AI assistant?

Plenty of agencies run without a CRM. A principal with one or two sales agents, a small rent roll, an office in a regional town: the contacts live in phones, the appraisals in a calendar, and the listings on realestate.com.au. When an agency like that looks at AI assistants, a common worry is that it will need to buy, set up and fill a CRM before anything else works.

It doesn't. An assistant needs a place to look up who is calling and a place to write down what happened. A CRM is one such place, and for many agencies a good one. It is not the only one.

What does a CRM actually do for an agency?

A CRM (customer relationship management system) is the agency's shared memory: a database of people, properties and the history between them. In a real estate office it usually holds:

• contacts, such as vendors, landlords, buyers and tenants, and how each relates to a property;
• property records, including past sales and properties that aren't listed;
• activity: calls, emails, appraisals, notes and follow-ups;
• prospecting lists, so agents know who to call this month and why;
• database marketing, such as newsletters and just-listed or just-sold campaigns;
• reporting on where listings and leads came from.

Trust accounting is usually not on that list. Rent receipting, payments to owners and the trust ledger normally sit in a separate trust accounting product or module, which has its own obligations: in Queensland, an agent's trust accounts must be audited for each audit period under section 34 of the Agents Financial Administration Act 2014, and agents with trust accounts must appoint an auditor (Queensland Government). A CRM may sit beside that software. It doesn't replace it, and buying one won't change your trust accounting.

What does an AI front office need from a CRM?

It needs to know who is calling, which properties are current, and what happened last time. Then it needs somewhere to write the result of the call.

• Contacts, so a known vendor or landlord isn't greeted like a stranger, and so a new caller's details are kept.
• Listings, so the assistant knows what is for sale or lease. For anything a caller actually hears, the safer source is the public listing on realestate.com.au, not private notes.
• Call history, so the agent can see what was said, and the next conversation starts where the last one ended.

Any system that holds these can do the job. A CRM holds them well. So can the assistant's own records, if they are built to.

How does AgentFront work with a CRM?

If your CRM is one AgentFront connects to, AgentFront works inside it. It reads contacts, properties, listings and activity from the CRM. After a call, it writes back a defined set of changes: it can create or update the contact, add a call note, and create a property record. There is no unrestricted two-way sync, and the integrations page sets out exactly what is read and written.

Even with a CRM connected, callers only hear what is publicly listed on realestate.com.au. Private notes in the CRM are never read to a caller.

How does it work with no CRM?

Since 29 September 2026, an agency with no CRM can use AgentFront, and AgentFront keeps the contacts and every call's record itself. The AgentFront 1.1 release brought that in.

The day-to-day work doesn't change. Each call is recorded with a timestamped transcript and a summary. When a seller agrees an appraisal time, the confirmed event goes into the agent's calendar after the call and the appraisal is recorded in AgentFront. Anything the assistant couldn't do becomes a task for the team, and the agent gets a text when an appraisal is booked or an investor calls.

The difference is where the history lives. Without a CRM, your team opens AgentFront to see who called, what they wanted and what was agreed, instead of a contact record in a CRM.

What does AgentFront need either way?

The same three things, with or without a CRM:

• Your listings on realestate.com.au. Listing answers to callers and enquirers come from the public listing, read-only.
• Your calendar, Google or Outlook, for appraisal times. The assistant offers only times that fit the agent's working hours, appointment length and buffers.
• A Gmail or Outlook inbox for rental enquiries, a person's own, or a group address such as rentals@ that delivers into it. Outlook joined in October, as covered in AgentFront for Microsoft 365 and Outlook.

Calls reach the assistant through forwarding set on each agent's own phone, usually on no answer, busy or unreachable, which also covers after hours. That is a phone setting, not a CRM one.

When should a small agency still get a CRM?

When the work you want to do is about the database rather than the phone. An assistant answers calls and records what happened. A CRM is how an agency works its database over months and years, and no assistant replaces that.

Signs a CRM is worth it:

• You want to market to your database regularly and need consent and opt-outs kept in one place.
• Several agents share vendors and buyers, and you need one view of who spoke to whom.
• Your appraisal follow-ups run to more names than one person can carry.
• You want reports on where listings came from, to decide where to spend.

Signs it can wait:

• One or two agents, with most new business arriving by phone.
• Listings on realestate.com.au, appraisals in a calendar, and a database small enough to know by heart.
• No regular database marketing yet.

For the second kind of agency, an assistant that keeps its own records covers what a CRM would have done on the phones. The CRM decision can then be made on its own merits, when the database work justifies it, rather than as a step you had to take before answering your calls better.