Contact us
Live demo

AI-powered support for PEXA

We built an AI support agent trained on the PEXA Help Centre. Ask it about workspaces, financial settlements, digital certificates, or any of the state-specific procedures your practitioners handle every day. It cites its source article on every answer, refuses to quote duty amounts, and hands off cleanly when a question falls outside its scope.

Try the PEXA AI agent

click any prompt to copy it

Every answer comes from the live PEXA Help Centre. The agent will say when a question isn't covered rather than guess.

Built for PEXA

Grounded in the PEXA Help Centre and shaped around the questions practitioners actually ask mid-workspace.

Workspace management

Creating and joining workspaces, workspace roles, invitations, workspace statuses, and the Ready check.

Financial settlements

Financial settlement schedules, trust account verification and authorised signatories, invoicing, and workspace fees.

Documents and dealings

Mortgages, caveats, transfers, Form 25 for foreign transferees, lodgement verification, and residual documents.

State-specific procedures

NSW, VIC, QLD, WA, SA, ACT, TAS, and NT. The agent asks for jurisdiction before answering when a question crosses state boundaries.

Digital certificates

Mobile Signing setup, Gatekeeper-accredited certificate transitions, refunds on unused USB hard tokens, MFA and Okta Verify.

Refuses to guess

Never quotes duty amounts, never recommends concessions, never echoes BSB or account numbers in chat. Hands off when the answer isn't in the Help Centre.

How we built this

Real content, real rules, real testing. No mock data, no invented answers.

1

Scraped the Help Centre

Every article across Workspace Basics, Financial Settlements, Digital Certificates, Settling on Time, and the four PEXA products, indexed and searchable.

2

Wrote the rules that matter

Never quote duty amounts. Never handle bank details in chat. Ask for jurisdiction on state-specific questions. Cite the source article on every answer.

3

Simulated the tough questions

Practitioners asking for a specific duty figure. Pasting a BSB and account into chat. Asking for a human straight away. All handled correctly.

4

Went live

Chat widget you can embed on pexa.com.au tomorrow. Every subsequent Help Centre update flows through without a redeploy.

What's next

A view of what a full deployment looks like when you're ready.

1

Train on your real data

Full Help Centre coverage plus any internal SOPs, macros, or QA guidance you currently rely on for practitioner support.

2

Phase 1 read-only

Deflect the procedural volume from your voice and email channels. Chat opens on the Help Centre and pexa.com.au. No writes to workspaces yet.

3

Phase 2 write-back

Extend into Salesforce for cases, PEXA Exchange for read-only workspace lookups, and Genesys for warm handovers to your team.

4

Scale across channels

The same agent handles voice on your practitioner support line, email intake, and chat. One knowledge base, one set of rules, three channels.

What this means for your team

The concrete outcomes practitioners and the contact centre both feel.

Cost per contact drops

Procedural volume that currently arrives by phone can be answered in chat, at chat's cost profile. Voice reserved for the complex cases that need it.

Always on

Settlement questions at 6:57 pm on a Thursday get answered, not queued. No rota, no wait time, no callback.

Consistent across jurisdictions

Every NSW answer matches every other NSW answer. No agent-by-agent variance on stamp duty entry, lodgement verification, or trust account rules.

Cites its sources

Every response names the Help Centre article it drew from. Practitioners can open the original for full detail without leaving the flow.

Compliant by construction

Refuses to quote duty amounts, refuses to give legal advice, refuses to handle bank details in chat. The compliance line is coded in, not left to agent training.

Keeps up with the Help Centre

Every Help Centre article your content team publishes propagates through the agent without a redeploy.

Ready to see what this looks like for PEXA?

Happy to walk through the sim results, share the KB gap analysis, or scope a full deployment.

Talk to the team