Trumis For organisations
The buyer's view · recorded intake, executive register

Every complaint on the record. Every risk on the register.

Trumis records each complaint exactly as the person confirmed it — verbatim narrative, ticked claims, evidence annexed, reference-stamped, lodged under your own complaint-handling policy — and tiers every open matter on an executive register by modelled exposure and response clock. Nothing is summarised or softened between your customer and your accountable executive. People still just talk — any language, voice or text; the structure is Trumis's job.

Verbatim
The record your executive reads is the one the person confirmed
3 tiers
Critical · Elevated · Watch, with modelled AFCA exposure
30 days
RG 271 window, spent responding — not reconstructing
One-line embedNo scripts in your page
<script src="https://embed.trumis.com.au/v1.js" data-partner="acme-energy"></script>
No scripts run in your page context, and no access to your DOM.
Complaints arrive pre-addressed to your inbox, framed under your policy.
Or take the structured object directly over the partner-mode API.
Sandboxed iframe · verified branding resolves server-side
The document

What your team receives

Complete and unedited, from the live engine · fictional complainant, fictional retailer
Formal complaint — service experience
Claims confirmed Evidence annexed Ref TRM-9C41F
FORMAL COMPLAINT — SERVICE EXPERIENCE Lodged with the organisation under its complaint-handling policy PART 1 — PARTIES AND CONTEXT This complaint is made to Acme Energy about the service I received, and is lodged under its complaint-handling policy. The conduct complained of is principally that of a person acting for the organisation, described in my account as: “the branch manager”. The organisation is responsible for the conduct of those acting on its behalf. The facts set out below are within my own knowledge, and I reviewed and confirmed each stated circumstance before lodging this complaint. PART 2 — WHAT HAPPENED In my own words, this is what happened: This complaint concerns the matter recorded in my correspondence with Acme Energy, involving $380. The full correspondence record is annexed; times are as captured. What I told them at the time: — [26 Jun 1] “You said the $380 overcharge would be refunded within 5 business days. Can you confirm?” — [6 Jul 09] “It has been 7 business days and no refund has arrived.” The captured record ends with my message unanswered. In my own words: I was in the Acme Energy office on Collins Street on 3 July around 2pm about my bill. The staff member at the counter, who said he was the branch manager, told me my hardship application was ‘not his problem’ and that if I kept asking they would just close my account and send it to debt collectors. I had been promised on the phone on 26 June that the $380 overcharge would be refunded within 5 business days. It never came. I felt humiliated in front of other customers. That’s everything. I just want this dealt with. Before lodging this complaint I reviewed and confirmed each of the following circumstances: — The way I was treated was aggressive, demeaning or harassing. — I was threatened with the suspension, closure or restriction of my account or service to make me comply. PART 3 — CONDUCT COMPLAINED OF 1 — THREATENED DETRIMENT A person acting for the organisation threatened to suspend, close or restrict my account or service in order to compel me to abandon a legitimate request. Whether the person held actual authority to carry out the threat does not lessen its coercive effect, and I ask that this conduct be specifically investigated. 2 — CONDUCT TOWARDS ME The behaviour towards me was intimidating, demeaning or harassing, and fell short of the standard the organisation’s own service commitments describe. OUTCOMES SOUGHT 1. Written acknowledgement of this complaint within the timeframe set by your complaint-handling policy 2. A written assurance that my account or service will not be suspended, restricted or otherwise adversely affected in connection with this complaint, together with an explanation of the threat that was made 3. A written response addressing each confirmed circumstance above, including what your investigation found and what will change 4. Escalation details for your internal review and for the relevant ombudsman, should I be dissatisfied with the response This document was prepared with the assistance of FairClaim, an automated legal information service. It does not constitute legal advice. If your matter is complex or the amounts at risk are significant, you should seek advice from a qualified legal practitioner or financial counsellor before proceeding. ANNEX — CORRESPONDENCE RECORD Reconstructed from screenshots provided by the complainant of their correspondence with the Acme Energy support chat; reviewed by the complainant; quotes verbatim as captured. [26 Jun 1] Complainant: You said the $380 overcharge would be refunded within 5 business days. Can you confirm? [26 Jun 1] Acme Energy Support: Yes — the refund of $380 has been approved and will reach your account within 5 business days. [6 Jul 09] Complainant: It has been 7 business days and no refund has arrived. — Prepared with Trumis, the complaint companion — trumis.com.au
Every claim in this document was ticked by the person before it was written. Scroll for the full record, including the verbatim correspondence annex.
How it works

Intake on your page

01

People talk, in their language

English, 中文, Tiếng Việt, العربية, Ελληνικά — voice or text, no form fields, at most one gentle question per turn.

02

Evidence is read on their device

Screenshots of chats and letters are OCR’d in the browser; images never leave the person’s device. They approve the reconstructed record before it is used.

03

Claims are ticked, not assumed

The AI never decides merit — a deterministic rules engine does — and nothing is written unless the person explicitly confirmed it. Your team can rely on what it reads.

04

You receive it, not us

The person sends from their own email (embed), or your systems capture the structured object (API). Your inbox is the record of receipt, and the register holds category codes only — never names, contact details or anyone's words.

01

People talk, in their language

English, 中文, Tiếng Việt, العربية, Ελληνικά — voice or text, no form fields, at most one gentle question per turn.

02

Evidence is read on their device

Screenshots are OCR’d in the browser; raw images stay on-device. The approved extracted text is retained with the intake.

03

Claims are ticked, not assumed

The AI never decides merit — a deterministic rules engine does — and nothing is written unless the person explicitly confirmed it. Your team can rely on what it reads.

04

Controlled complete record

Trumis retains an encrypted complete intake for up to 24 months. Client access stays tenant-isolated; named platform-administrator reads are audited.

Compliance

Record-keeping, RG 271 and ombudsman schemes

General information about how Trumis output fits common obligations — not compliance advice. Your compliance team owns the mapping for your organisation.
Complete complaints on first contact

RG 271 expects financial firms to address the issues a complaint raises within the response window — 30 calendar days for most. Structured intake means the clock starts on a complaint your team can actually action; reconstruction time is the single biggest driver of blown IDR timeframes.

Complete intake records

The email in your inbox or API object remains your operational record. Trumis also retains the encrypted conversation, facts, extracted evidence text, generated document and routing for controlled support and assurance access.

The register

Licensed intake includes a risk-tiered view of what arrived: critical / elevated / watch, urgency, evidence strength, amount bands — each row matched to the complaint in your inbox by the Reference: TRM-… line printed on it. Category codes only; it structurally cannot hold anyone’s words.

Identity, particulars and preservation

Documents carry the complainant’s identity as they typed it, the location, date and people involved, and a records-preservation request — the details AFCA, the TIO and state ombudsmen ask for, captured before escalation ever happens.

Escalation-aware

Consumer-side documents name the correct external scheme with response clocks. Complaints that reach an ombudsman as “the organisation never understood my complaint” are the expensive ones; intake that listens is how they stop.

Auditable merit decisions

Every generated complaint maps to named arguments in a maintained legal knowledge base (grounds.passed_arguments in the API) — you can see why the engine considered grounds to exist.

Security & privacy

Posture, stated plainly

Including what we don't yet hold
Architecture

No accounts, and no conversation state held between turns. What is stored, in Australia: content-free category codes for the register and statistics, and an encrypted, access-audited intake service record. The full model is published at trumis.com.au/security.

Data residency

Hosted on Vercel, served from Australia, API compute pinned to Sydney. The one overseas flow — AI provider processing of conversation text, typically US — is disclosed in the Privacy Policy. APP 8 relevant.

The embed

A sandboxed iframe: no scripts in your page context, no access to your DOM, and verified partner branding resolves server-side so it cannot be impersonated.

Certification — not yet held

We are open about not yet holding SOC 2, ISO 27001 or IRAP. The architecture deliberately minimises what such an audit would need to protect.

Assurance

We answer security questionnaires and support your pen-testing of a pilot.

Disclosure

Vulnerability reports via security.txt at trumis.com.au/.well-known/security.txt.

Architecture

Complete server-processed intakes are encrypted in a controlled archive for up to 24 months, with tenant isolation and audited named-administrator access. The full model is published at trumis.com.au/security.

Data residency

Hosted on Vercel, served from Australia, API compute pinned to Sydney. The one overseas flow — AI provider processing of conversation text, typically US — is disclosed in the Privacy Policy. APP 8 relevant.

The embed

A sandboxed iframe: no scripts in your page context, no access to your DOM, and verified partner branding resolves server-side so it cannot be impersonated.

Certification — not yet held

We are open about not yet holding SOC 2, ISO 27001 or IRAP. The architecture deliberately minimises what such an audit would need to protect.

Assurance

We answer security questionnaires and support your pen-testing of a pilot.

Disclosure

Vulnerability reports via security.txt at trumis.com.au/.well-known/security.txt.

Onboarding

From pilot to licence

Week 0 Free

Pilot, self-serve

Paste the one-line embed on a test or live complaints page. Watermarked, complaints pre-addressed to your inbox. No contract, no call required.

Weeks 1–4 Free

Evaluate

Your team reads real intake output and forms its own view. We are available at info@trumis.com.au throughout.

When ready Annual

Licence

A written agreement covers verified branding, watermark removal, registered page origins, API keys with raised limits, support commitments and data-processing terms.

Alternative $349/mo

Starter licence

Smaller organisation? The self-serve Starter covers the same verified, unbranded embed at a public price — pay by card, live within one business day of verification.

Trumis
Paste the embed on a test page today. No contract, no call required.
One address for everything: info@trumis.com.au · acknowledged within two business days.