951,000 members.
Every one of them
a different Tuesday.
A layer that sits over the systems you already run, joins what a member's record knows across all of them, and prepares the next thing they need to hear — in the app, in a letter, or from the person who picks up the phone. It never sends. It never decides a claim.
Your own numbers: more than 951,000 members as at 30 June 2025, and 94c of every dollar received in premiums paid out in claims in the year to that date. A not-for-profit returning 94c in the dollar has more to lose from a badly handled moment than almost anyone.
The member's record already knows. It has just never been read as one thing.
Policy, claims, prior approvals, the app, the contact centre, the provider network. Each knows part of a member. None holds the whole picture — and the member experiences all of it as one relationship with you.
Nothing gets replaced. Nothing gets migrated. No claim is ever assessed, approved or declined by this layer.
One screen, each morning
Today's member moments, what is prepared, what is waiting on a person, and what has been deliberately held back.
Specialist agents, each with written limits
Single-job agents that read across the systems and prepare the next thing a member needs. None sends. None assesses a claim.
Everything you already run
Read-only, and only the fields a given job needs. Health information is never read in order to write a message.
Joining is a transaction. A diagnosis is not.
A member journey that treats all five of these the same is the reason insurance feels administrative at the exact moment it should not. Choose a moment and watch the journey assemble — the stages change, what it reads changes, and so does who approves.
It reads the record, not the health information. Whether a claim is open, whether an approval is pending, whether someone has called three times — that is enough to prepare a message. The diagnosis is not needed and is not read.
It reaches the member where they already are. The app is the fastest way to tell someone something before an envelope does.
It knows when to say nothing. Every journey here contains at least one step that is deliberately held.
Most remediation goes wrong before a word is written.
Your own role description asks for remediation communications delivered with accuracy, empathy and integrity, driving fair, ethical and compliant outcomes under CoFI. That is not a writing brief. It is a research brief with a letter at the end of it.
Here is the whole campaign, in the order it should actually happen. Click through it.
Tell them before the envelope does.
You already describe the app as a pocket-sized healthcare partner where members check benefit balances, request prior approval and make instant claims. That makes it the single best place to say something difficult first — because it arrives when the member opens it, not on the day the post decides.
A remediation notice in the app, a day ahead of the letter, does three things a letter alone cannot: it removes the shock of an unexplained envelope, it answers the first question immediately, and it gives them a way to ask the second one.
Illustrative screen. Not a Southern Cross design, and no app data was accessed. Only registered policyholders can make claims or request prior approvals.
Kia ora
MemberThe checks that matter most are the ones that stop a letter being written at all.
Remediation is where a well-meaning template does the most damage. These run on every draft in the batch, and the ones that block are the point of the whole thing.
Press run to see what it catches — and what it refuses to produce at all.
The batch, before anything goes out.
Illustrative cohorts — not Southern Cross data. Cohort sizes are deliberately blank: this concept has no member data and does not estimate how many people anything affects.
| Cohort | Members | Prepared | Waiting on | Status |
|---|
Every row is a draft waiting for a named person. The layer does not send, approve, assess, or calculate redress.
Every letter carries its own working.
Not a log somebody has to go and find. The provenance travels with the piece of work — which fields it read, which rules it held, who must approve it, and what it refused to do.
On a remediation, that record is the difference between explaining your process to a regulator and reconstructing it.
- Artefact
- —
- Read
- —
- Not read
- Diagnosis, clinical notes, provider correspondence, or any health information
- Rules held
- Conduct of Financial Institutions regime · Fair Trading Act 1986 · Privacy Act 2020 · Health Information Privacy Code 2020
- Refused
- No redress amount calculated or stated. No letter drafted for a deceased or flagged-vulnerable member.
- Approver
- A named person. Unsent until then.
- Prepared
- —
- Reference
- —
What this will never do
It does not send. It drafts, and a named person sends. It never assesses, approves or declines a claim. It never calculates or states a redress amount. It never reads a diagnosis, clinical note or any health information in order to write a message. It does not write back to your systems. It does not pretend to be a person — every message says it was prepared by a machine and approved by a human.
No production access is requested by this concept.
Scope
One remediation cohort, research through to a batch ready to send. Six weeks. Not the whole programme, not the contact centre, not the underlying assessment.
Access
The remediation scope note, your letter templates, your contact-centre call drivers, and the names of the fields that mark a deceased or vulnerable member. No member records. No health information. No claims data.
Scorecard
Drafts accepted without rewrite. Held cases a person agreed should have been held. Contact-centre calls the letter would have caused. Complaints. One remediation lead's honest answer to “would you put your name on this?”
Fail any line of the scorecard and we change the design or stop.
Pick a verb.
Not “book a demo”. Any of these is a real next step, and the third one is a perfectly good answer.
What is the one constraint we have got wrong?
Every concept is built from the outside. There is always something about how Southern Cross actually runs that we could not see. One line is enough.
Opens your mail app to assembl@assembl.co.nz. Nothing is collected by this page.