Receipted AI for Property Management: What TCIT Needs to See

The Tenancy Compliance and Investigations Team conducts 400 to 500 audits of New Zealand property management companies each year. When they arrive at your office — or send a formal request for records — they are not asking general questions about your policies. They are asking about specific interactions: maintenance requests that were logged or not logged, tenant contacts that were actioned or not actioned, response windows that were met or missed.

If your AI agent has been handling tenant contacts, those interactions are part of your compliance record. When TCIT asks what happened with a particular maintenance call, “the AI handled it” is not an answer. But a receipt showing the call timestamp, the maintenance request created in Re-Leased, the urgency classification applied, and the property manager notification sent — that is an answer. That is what TCIT needs to see.

The RTA Obligation Starts at First Tenant Contact

This is the point that most property management firms have not fully worked through when they deploy AI: the Residential Tenancies Act 1986 creates obligations that begin at the moment of tenant contact, not at the moment a human staff member responds. If a tenant calls your property management company about an urgent maintenance issue and your AI handles that call, the RTA clock has started. The question of whether the contact was received, acknowledged, and actioned is now a question your records must be able to answer.

For routine maintenance requests, TCIT expects to see evidence that requests were received and addressed within a reasonable timeframe. For urgent or emergency maintenance — dangerous conditions, no heating in winter, water damage — the timeframes are tighter and the consequences of non-compliance are more severe. An AI agent that routes calls without receipting its actions creates a documentation gap that sits squarely in the middle of your RTA compliance record.

A Receipted AI agent changes this entirely. When a tenant calls at 11pm about a water leak, Alice logs the call, captures the details, applies your urgency rules, creates the maintenance request in Re-Leased, and notifies the duty property manager. Every one of those steps produces a timestamped receipt. The record is not a call recording sitting in a folder somewhere — it is a structured document showing what action was taken at each step, and when.

What a Property Management Receipt Contains

An AliceHQ receipt for a property management interaction contains the elements TCIT and your own internal auditing requires. The channel through which the contact arrived — phone, SMS, or web chat. The timestamp of first contact. The tenant intent identified. The urgency classification applied, with reference to your configured rules. The Re-Leased job ID created. The notification sent to the property manager, with timestamp. The confirmation sent to the tenant, if applicable. And a link to the full conversation transcript.

This is not a log buried in a system. It is a receipt formatted for human review and export. When TCIT asks what happened, you open the receipt. When a tenant disputes the response to their maintenance call, you open the receipt. When you are reviewing your own processes to identify response time improvements, you review receipts in aggregate.

Re-Leased Integration: The Receipt Proves the Write

AliceHQ integrates directly with Re-Leased, the property management software used by a significant proportion of NZ property management firms. The integration means that when Alice handles a maintenance request, the job is written directly to Re-Leased — not queued for a staff member to manually enter later. The receipt captures the Re-Leased job ID returned at the moment of creation, so there is no ambiguity about whether the record was made.

This is important for TCIT purposes because it closes the loop between the AI action and your system of record. A call recording can be disputed — a tenant can claim the AI said something different, or that the call was not actioned. A Re-Leased job ID in the receipt cannot be disputed: the job either exists in Re-Leased at that timestamp or it does not.

What This Means for Your Next TCIT Audit

Most property management companies approach TCIT audits reactively. They gather records after the request arrives, search through systems for the relevant interactions, and hope the documentation is complete enough to satisfy the audit. When AI has been handling contacts, this process gets harder because the records may be scattered across call logs, transcripts, CRM entries, and system writes that were not connected to each other at the time.

With Receipted AI, the approach changes. Every AI-handled interaction has a receipt that connects the call, the action taken, and the Re-Leased record, in a single retrievable document. When TCIT asks what happened with Tenant X on 15 February, you pull the receipt for that contact. It takes thirty seconds, and the answer is complete: timestamp, action, system write, confirmation sent. The audit becomes a documentation review rather than a records archaeology project.

This is what “when TCIT asks what happened, you have the answer” means in practice. Not a promise of compliance. An actual record that proves the right thing happened, when it was supposed to happen, in the right system.