AI Email for NDIS Providers

All email processing happens in Australian data centres with AES-256 encryption, and we connect via OAuth 2.0 — we never see your email password. Your correspondence is never used to train models for other customers. On top of the platform security, you can define restricted categories: emails mentioning health information, guardianship matters, incidents, or specific participants can be locked to view-and-flag handling only, so the AI never drafts or sends anything in those categories without a named staff member approving it. Every processing action is logged, which supports your obligations under the Privacy Act 1988 and the Australian Privacy Principles when handling participant information.

Yes — this is one of the most useful things it does for NDIS providers. The AI classifies each email by sender and content: NDIA and myplace or PACE portal notifications, plan management companies chasing invoices or remittances, support coordinators requesting quotes or service agreements, and participants or family members asking about supports and rosters. Each stream gets its own queue, priority rules, and reply templates, so a payment query never buries a message from a participant's family. You can route plan manager and NDIA correspondence straight to your finance or admin team while participant emails go to the relevant service.

With extreme caution, by design. Emails whose content suggests an incident, injury, safeguarding concern, or complaint are flagged as critical and escalated immediately to the staff members you nominate — the AI never auto-replies to incident-related correspondence. The email, its timestamps, and every processing step are logged so you have a clear record of when the message arrived and when it was escalated. This supplements, but does not replace, your incident management system and your obligations under the NDIS (Incident Management and Reportable Incidents) Rules 2018. Your registered incident process stays exactly as it is; AI Email just makes sure nothing sits unread in a shared inbox over a weekend.

Yes. Every email the AI touches gets a complete processing log: when it arrived, how it was categorised, what was drafted, who approved it, and when the reply was sent. Logs are searchable by participant, sender, service, and date range, and can be exported for your quality and audit preparation. That kind of consistent, timestamped correspondence trail supports the documentation expectations that come with the NDIS Practice Standards and provider quality audits — instead of reconstructing email history from individual staff inboxes, you have one organised record of how participant and stakeholder communication was handled.

Yes — you can set different voice profiles for different audiences. Replies to participants and families can be drafted in warm, plain English: short sentences, no NDIS jargon, no acronyms without explanation, and a reading level you choose. Replies to plan managers, support coordinators, and the NDIA can use a more formal, detail-complete style with the reference numbers and line items they expect. The AI learns your organisation's existing tone from your sent email, so drafts sound like your team wrote them. Staff review drafts before they go out, and you decide which routine categories, if any, are ever sent automatically.

Absolutely. A provider running SIL homes, community participation, support coordination, and allied health under one roof can give each service its own rule set — separate triage priorities, reply templates, escalation contacts, and approval workflows. Roster-change requests for a SIL house can go straight to that house's coordinator, while therapy enquiries route to your allied health intake. Multi-site providers can do the same per region or office, with organisation-wide reporting across all of them. The Professional plan covers 5 mailboxes at $399 per month, so shared service inboxes and site inboxes can all run under one account.