Workflow Orchestration Console
Real Estate — Branch Demo
Ready
Oracle Cloud · AI Database 26ai · Governed

Scenario

Incoming trigger

0:00
Elapsed (live)
0 min
Manual effort replaced
0
Automated actions
0
Human checkpoints

Workflow pipeline

Agentec Agent — activity stream governed session · NZ region
# Agentec orchestration agent ready.
# Connected: CRM · REINZ · LINZ · Trade Me · Trust ledger · Email
# All actions are policy-checked and written to the audit trail.

What Agentec is

A workflow layer that sits across the systems a branch already uses. It watches for triggers — a signed agreement, a tenancy application, a maintenance report — then runs the routine steps the same way, every time, in every system that needs updating.

What it isn't

Not a new CRM, not a chatbot, and not a replacement for your people. Nothing gets ripped out. Decisions, judgement and client relationships stay with salespeople and property managers — Agentec does the re-keying, chasing and assembling around them.

When it's unsure, it asks

Every piece of data the AI reads carries a confidence score. Anything below threshold, ambiguous or unusual is flagged to a person — never guessed. You'll see this happen live in the demo, alongside the approval gates it can't pass without you.

Where Agentec sits

ORACLE CLOUD INFRASTRUCTURE — SYDNEY REGION Security, governance and audit boundary · Oracle AI Database 26ai · encrypted at rest and in flight YOUR PEOPLE Approve & decide Handle flagged exceptions Stay client-facing Agentec asks, people decide — approvals and exceptions always go to a person AGENTEC ORCHESTRATION LAYER Watches for triggers · runs the workflow end to end · enforces policy · logs everything Read & extract Check policy Update systems Draft comms Reconcile Audit log Secure two-way API connections to the systems you already run — nothing replaced SYSTEMS YOU ALREADY USE CRM REINZ LINZ & Council Listing portals Trust ledger Email & calendar

From demo to live — the pilot path

1DiscoveryMap one real workflow at one branch, with the people who run it today. The messier the better.1–2 weeks
2Connect & configureRead-only API connections first. Approval gates, spend limits and confidence thresholds are set with you, not for you.2–3 weeks
3PilotOne workflow, one branch, measured against the manual baseline. People approve everything while trust is earned.~4 weeks
4ScaleExpand workflow by workflow, branch by branch, once the numbers prove out — on the same governed platform.Ongoing

Questions teams usually ask

Does this replace our people?No — it removes the re-keying, chasing and assembling between systems. Salespeople and property managers keep every decision and every client relationship. It gives them capacity back.
What if it gets something wrong?Low-confidence data is flagged to a person, never guessed. Nothing external — emails, listings, money — moves without human sign-off, and every action sits on the audit trail and can be corrected in the source system.
Where does our data go?It stays in-region on Oracle Cloud (Sydney), encrypted at rest and in flight. Client data is never used to train third-party AI models.
Do we have to change our systems?No. Agentec connects to the CRM, REINZ, portals and ledgers you already run, through their existing interfaces. If a system changes later, the workflow layer adapts — that's the point of it.
Can we turn it off?Any workflow can be paused instantly — per branch or entirely. The manual process underneath is unchanged, so nothing breaks when you do.
How do staff work with it?Mostly through the tools they already use: approvals arrive by email or in the console, tasks land in the CRM. There's no new system to learn before the benefit shows up.

Audit trail — grouped by workflow run

No events yet. Run a workflow and every action — AI and human — will appear here with a sealed timestamp, grouped under the run it belongs to.

In production the audit trail is immutable — the clear button here is a demo control so you can walk into a meeting fresh.

Document vault — this session

No documents yet. Files processed during a run are encrypted into the governed vault and linked to their records — watch them appear here as workflows execute.

Originals are encrypted in Oracle Cloud (Sydney) and linked into the CRM and compliance records. Staff open them from the CRM as they always have — nothing lives on laptops, inboxes or shared drives, and retention follows your compliance policy.

Security & governance layer

⬢
Oracle Cloud Infrastructure — Sydney regionClient data is stored and processed in-region. Nothing leaves the governed environment to train third-party models.
◈
Oracle AI Database 26aiOne governed data layer for workflow state, documents and AI context — vector, JSON and relational data under the same access controls.
🔒
Encryption everywhereEncrypted at rest and in transit, including quantum-resistant encryption for data in flight.
⛬
Role-based access, branch isolationAgents see their own listings; branch managers see their branch; head office sees governed aggregates.
🗂
Governed document vaultSource documents are encrypted into OCI Object Storage (Sydney) with their metadata in AI Database 26ai, then linked to CRM and compliance records — never stored on local machines.
✎
Immutable audit historyEvery AI action, human approval and data access is logged and exportable for REA / AML-CFT compliance reviews.

Human-in-the-loop policy gates

AML/CFT & compliance: the AI prepares and checks — a person always signs off before a file proceeds.
Anything public-facing: listings, marketing copy and client emails are staged for approval, never auto-published.
Money: trust account entries are matched and reconciled by the AI, but never initiated by it.
~3.5 hrs
Admin time replaced per workflow run — hours of branch work handled in minutes.
0
Re-keying between systems. Data is captured once and flows to CRM, REINZ records and marketing.
100%
Of compliance steps logged with a timestamped, exportable audit trail.
<5 min
From signed agreement to a complete, compliant file the salesperson can act on.

Quick numbers — try theirs live

—
Hours back per month
—
Value per month
—
Value per year

Adjust live in the meeting with their numbers. Time value only — excludes error reduction, faster response times and compliance risk.

What this looks like across a branch

A branch settling 25–35 listings a month carries hundreds of hours of repeated admin: re-keying agreements into the CRM, chasing compliance documents, assembling appraisal data, drafting the same emails. Agentec sits across the systems the branch already uses — the CRM, REINZ, LINZ, the portals, the trust ledger — and runs those workflows end to end, pausing wherever a person needs to decide. Salespeople stay in front of vendors and buyers; the file builds itself behind them, and every step is governed and auditable on Oracle Cloud. The same engine runs the property management side of the business — applications, bond lodgement, maintenance coordination, arrears follow-up and owner statements — where the admin load per property is constant rather than per-transaction.

Figures shown are illustrative for demonstration. We'd calibrate them to your agency's actual branch workflows during discovery.