Real Estate Agent Automation in Australia: What You Can Automate and What Must Stay Manual

Rex's API is far larger than its integration marketing suggests: 278 services carrying 2,620 methods, all POST, with 43 of those services carrying full OpenAPI documentation. That catalogue is readable without authentication, which makes it one of the few Australian CRM surfaces you can scope accurately before signing anything. The write actions most agencies assume are missing are present. `Appraisals::create` exists, alongside `read`, `update`, `search` and `getDynamicCommissionEstimate`. `Reminders::create`, `read`, `update` and `search` exist, as does `MailMerge::createAndSend`, described in Rex's own documentation as creating a mail merge and sending it instantly. Email template management sits under `AdminMergeTemplates` and `AdminHtmlTemplates`, including `getMergeTagsForRecordType`. Rex also ships its own automation primitives. `AdminAutomationRules`, `AdminWorkflows` and `AdminTracks` are first-party services, and Tracks are Rex's built-in multi-step follow-up sequences. Before you build a workflow outside Rex, check whether the same thing already exists inside it. Recurring contact is a native record field rather than an add-on. The Reminders model carries `recur_frequency`, `recur_unit`, `recur_stop_after_date`, plus `scheduled_send` and `scheduled_send_time`. A quarterly touch on a past client is a reminder record with `recur_frequency: 3` and `recur_unit: month`, not a separate scheduling system you have to build and maintain.

The real limit most agencies hit is not the Rex API, it is Zapier. Rex's native Zapier app publishes 20 triggers, 11 write actions and 4 search actions, and that write list cannot create or update a Contact, Listing, Property or Appraisal. Zapier can create a Lead, a Note, a Reminder, a Match Profile and a Track, add and remove tags, and send email or SMS. Those are enough to run a stay-in-touch system and a lead-routing chain with no code. Anything that writes to a core record requires the full API and a real Rex user account. That asymmetry decides project scope more often than budget does. If the requirement is "tag the attendee, remind the agent, log a note", Zapier is sufficient and the build is small. If the requirement is "create the appraisal record when the enquiry lands", Zapier cannot do it and the project becomes an API integration with authentication, error handling and a rate-limit strategy attached. Getting API access has its own friction. Authentication is a real Rex user's email and password rather than an OAuth app registration, and Rex's own documentation notes that the integration user counts against the agency's paid user slots unless you complete its Verified Integrator process, which takes 5 to 10 business days and requires a live integration already running in a client account.

`contact.last_contacted_date` is directly searchable in Rex, which is the single most useful technical fact for anyone trying to work the neglected part of a database. Contacts expose 437 searchable fields including the entire nested `owned_properties.property.*` tree, so one call returns every contact who owns a property in a given suburb and has not been contacted since a date you choose. That query is the whole re-engagement product. Without it you are exporting a spreadsheet, sorting by hand and hoping the export stays current. With it, the list of neglected owners is a saved search that updates itself, and the automation's job is simply to draft against it and route the drafts to a human. Appraisals carry 132 searchable fields, including `archive_lost_agency_id` and `listing_id`. A null `listing_id` means the appraisal never converted, and `archive_lost_agency_id` records which agency won it instead. Together those two fields let an agency compute its own real appraisal-to-listing conversion rate from its own data rather than arguing about industry averages. Kate Smith, Director and Principal at Kate Smith Property, described the gap this closes in a Realtair blog post on 24 March 2026: "I have so many clients, and I know I should be talking to them. But if you have that automation happening for you, it's just something you know is constantly working in the background. Nothing beats a phone call, but Realtair is an amazing, amazing product." She is speaking on a vendor's blog about that vendor's product, so read the endorsement accordingly. The observation underneath it stands on its own.

Rex's rate limit is 3,600 requests per hour per agency account, which is one request per second sustained. Rex describes the limit as soft today and states plainly that it will be strictly enforced in future, so design against it now rather than after the enforcement lands. One request per second rules out the obvious design. You cannot loop over a five thousand contact database making a call per contact and finish inside an hour. What works instead is batching: search once with a high limit, hold the result, and write back only the records that changed. Rex's documented pattern for this is e-tag sync. A search with `result_format: etags` returns record identifier and e-tag pairs at limits up to 50,000 rows, so you compare against local state and fetch only what moved. Rex's own guidance recommends syncing into a local database periodically over making live per-request API calls. Webhooks cover the other direction, with support for more than 50 events across all subscription tiers. They fail closed and they fail permanently: a webhook showing a 99% failure rate over 24 hours is disabled, and events that occurred while it was unhealthy are never replayed. Any response slower than 10 seconds counts as a failure. Rex's own recommendation is to run a nightly e-tag sync alongside webhooks, which in practice makes the nightly sync mandatory rather than optional.

Here is the working day mapped against what the tooling and the law actually permit. The blocking constraint is listed separately from the verdict, because in this industry the two are usually different things. | Task area | Verdict | What actually blocks it | |---|---|---| | Lead acknowledgement and routing | Automate fully | Nothing. Lead Created trigger plus Assign Lead and Create Reminder all exist in Zapier | | Appraisal booking and reminders | Automate fully | Nothing. Appraisal Created is a published trigger | | Creating an appraisal record from outside the CRM | API only | Zapier cannot write it. `Appraisals::create` in the full API can | | Creating or updating a contact from outside the CRM | API only | Same asymmetry. Zapier's 11 write actions exclude core records | | Populating and sending a merge email | Automate fully | `MailMerge::createAndSend` and `AdminMergeTemplates` both exist | | Any message containing a price estimate | Human approval required | Estate Agents Act 1980 (Vic) and Australian Consumer Law s 30 | | Choosing recipients from licensed property data | Prohibited | Domain and Pricefinder API terms, clause 7.6(k), and every state licence | | Past-client stay-in-touch | Automate the trigger, approve the copy | Consent and unsubscribe obligations under the Spam Act 2003 (Cth) | | Listing status admin and settlement checklists | Automate fully | Nothing. Contract Status Changed carries most of it | | Real-time per-contact API loops | Not viable | 3,600 requests per hour per agency | Read the middle column as a design instruction. Anything marked "human approval required" needs a queue and an audit trail built before the workflow, not after it.

Any automated message carrying a price estimate engages the Estate Agents Act 1980 (Vic) and the Statement of Information regime administered by Consumer Affairs Victoria. Consumer Affairs Victoria states a penalty of more than $48,842 for non-compliance, with the further consequence that an agent who sets an unreasonable estimated selling price, or advertises below it, can forfeit their commission on the sale. Enforcement is active rather than theoretical. The Victorian Government's underquoting taskforce has monitored over 700 auctions and issued more than $1.1 million in fines to estate agencies, and Consumer Affairs Victoria has laid criminal charges, including against a Melbourne agency over the estimated selling price on an Ivanhoe townhouse. The Statement of Information itself is a good automation target right up to the number. It must carry an indicative selling price as a single figure or a range no wider than 10%, the three most comparable sold properties with address, date and price, and the suburb median no older than six months. It must appear at every open for inspection, in online advertising, and reach a prospective buyer within two business days of a request. Track the deadline, assemble the document, prompt the agent, then stop. From 10 December 2026, APP 1.7 adds a transparency obligation. Where a computer program uses personal information to make, or directly support, a decision that could reasonably be expected to significantly affect a person's rights or interests, the privacy policy must disclose the kinds of information used and the kinds of decisions made. An automated price estimate sent to a consumer sits squarely inside that frame. The liability stays with the licensed agent, not the vendor, which is the whole argument for human approval before an automated send.

From 1 July 2026, obligations under the Anti-Money Laundering and Counter-Terrorism Financing Act 2006 apply to real estate professionals, and the OAIC states that all reporting entities must comply with the Privacy Act when handling personal information for or in connection with those obligations. The OAIC says this expressly includes small businesses with annual turnover under $3 million. In practical terms the small business exemption is gone for real estate agencies. Turnover no longer shelters a small agency from the Australian Privacy Principles, and because this commenced four weeks ago, most principals have not adjusted anything yet. One question is genuinely open and a lawyer should settle it rather than a blog. Whether the obligation reaches a marketing database, or only records held for anti-money-laundering purposes, is not settled on the public guidance available. The commercial reality is that very few agencies can run two privacy regimes side by side across one CRM, so the practical planning assumption is broader coverage even though the strict legal scope is unresolved. Two further changes are already live. The statutory tort of serious invasions of privacy has been in effect since 10 June 2025, which creates a private right of action that does not depend on the regulator acting. And from January 2026 the OAIC has been running its first privacy compliance sweep, targeting the privacy policies of businesses that collect personal information in person, with real estate agents named as an example. If an agency's privacy policy has not been touched since somebody copied it off another agency's site, that is the exposure. Privacy Act and consumer law for Australian software covers the wider obligations.

Licensed property data may populate the content of a message to someone who already consented, and may never be used to build, enrich or select the recipient list. That single distinction kills most of the obvious product ideas in this space, and it is a licence term rather than a technical limit. This is structural rather than one vendor's contract term. Every state's underlying property sales data licence prohibits direct marketing use, and those restrictions flow through resellers into whatever product you end up buying. | State | The prohibition in its own terms | |---|---| | VIC | No use to prepare mailing lists or to assist in direct marketing | | NSW | Must not use the sales information for direct marketing, or with the intention of encroaching on an individual's privacy | | QLD | No Mail Merge Functionality, and no direct marketing | | SA | Must not be used for the purposes of compiling contact lists, whether personalised or not | | WA | No direct marketing, defined broadly | The API terms sit on top of that. The Domain terms and conditions, which also govern Pricefinder API data, prohibit using the API data for any direct marketing purposes at clause 7.6(k), and Pricefinder's pricing page states the same thing directly. Three red lines are consistent across every source: attaching owner names to properties, bulk redistribution or dataset recreation, and any use for direct marketing or contact-list building. The cleanest way to hold the boundary is the address, price and date triple. Those three together are defensible as non-personal information, which is why Victorian law can compel their publication in a Statement of Information. The moment an owner's name or contact details attach, it becomes personal information and the full Australian Privacy Principles regime applies. That is exactly where every state licence draws its line too. Pricefinder makes it concrete: ownership data is available only in Western Australia, New South Wales, Victoria and Queensland, and owner name search is not available in Victoria at all. So the architecture that survives review has a hard separation. The recipient list comes from independently obtained consent you can evidence. The property figures inside the message come from the licensed source. Nothing crosses that line, including the tempting version where you filter your own consented list using licensed data to decide who is worth emailing. More on the data layer in Rex, Pricefinder and CMA automation.

The Spam Act 2003 (Cth) covers every commercial electronic message an agency sends, SMS included, and ACMA enforces it. Three obligations apply: express or inferred consent before sending, clear identification of the sender with accurate contact details, and a functional unsubscribe honoured within five business days. Inferred consent is the one agencies get wrong. It requires a provable, ongoing relationship, with the marketing directly related to that relationship. An enquiry from six years ago that never became a transaction is a thin basis for a send today, and consent never transfers with a purchased list. ACMA penalties are large and recent. The Commonwealth Bank paid $7,500,000 in October 2024 over more than 170 million emails sent without a functional unsubscribe and 34.8 million sent without consent. Tabcorp's TAB paid $4,003,270 in June 2025, and Pizza Hut Australia paid $2,502,500 in May 2024 over more than 10 million messages. In July 2024 ACMA noted businesses had paid more than $15 million in spam and telemarketing penalties over the preceding 18 months. Rex's own API terms reinforce the position rather than conflicting with it. Contact information obtained through the Rex API cannot be used for external outreach without the contact's express permission, cached data must be refreshed at least every 24 hours, and API access may not be sold, sublicensed or syndicated. That last clause rules out any product holding a long-lived mirror of a client's Rex database.

A demo showing AI writing an appraisal email is showing you the easy half. The questions that decide whether a product is useful are narrower: which write actions does it expose, can a human approve outbound in batches before anything leaves, and does it record who approved what and when. That approval log is what you produce if Consumer Affairs Victoria asks an agent to justify how an estimate was determined. It costs almost nothing to build at the start and is effectively impossible to reconstruct afterwards. The strategic argument for doing this well is not efficiency, it is positioning. Shane Slater, Co-Founder of Realtair, put it this way in March 2026: "As agents, we need to stop asking our future potential clients if they are looking to sell... We should be the agents that provide them with great relevant sales information, so when they become a seller, they call us for an appraisal." He sells software that does exactly that, which is worth knowing when weighing the claim. The practical test before any build: name the trigger, name the write action, name the approver, and name the field the automation reads to decide who is in scope. If any of the four is missing, the project is not scoped yet. What not to automate with AI covers the wider version of that test.

Can Rex create an appraisal record through the API? Yes. `Appraisals::create` is a documented method, alongside `read`, `update` and `search`. What cannot create an appraisal is Rex's Zapier app, whose 11 write actions exclude Contacts, Listings, Properties and Appraisals. If a build needs to write a core record, it needs the full API and a real Rex user account rather than a Zap. Can I automate a property appraisal from start to finish in Australia? No. You can automate the booking, the data gathering, the document assembly and every reminder around it. The estimated selling price is a representation a licensed agent makes and stands behind. In Victoria it also has to meet the Statement of Information rules, where non-compliance carries a penalty above $48,842 and possible forfeiture of commission. How do I find every past client I have neglected? Search Rex on `contact.last_contacted_date`. It is one of 437 searchable Contact fields and can be combined with the nested `owned_properties.property.*` tree, so a single call returns every contact who owns a property in a chosen area and has not been contacted since a chosen date. That query is the foundation of any re-engagement work. Can I use Pricefinder data to decide who to email? No. The Domain API terms governing Pricefinder data prohibit using the data for direct marketing at clause 7.6(k), and every state property sales licence prohibits using sales data to build contact or mailing lists. Licensed data may populate the content of a message to someone who already consented. It may never select the recipients. How many hours a week do Australian agents spend on admin? Nobody has published a measurement. We searched REIA, the state institutes, both major portals and the CRM vendors and found no Australian survey of agent time allocation. Several specific weekly figures circulate on AI-services blogs and trace to no source at all. The honest available finding is qualitative: Rex's AI Advisory Board reported in April 2026 that agents work roughly the top 5% of their leads. Does the Privacy Act apply to a small agency under $3 million turnover? As of 1 July 2026, yes, at least in part. AML/CTF Act obligations now apply to real estate professionals, and the OAIC states that all reporting entities must comply with the Privacy Act when handling personal information for or in connection with those obligations, expressly including small businesses under $3 million turnover. Whether that reaches a marketing database or only anti-money-laundering records is an open question for a lawyer.