Joined-up support after a life event

The problem and opportunity

Northern Ireland's draft AI strategy names linked citizen services after a bereavement as a public-service application: notifying the relevant services so that someone has less to do at a hard time.

It does not say who authorises each notification, what gets shared, or how a mistake is put right.

nidirect publishes the list of contacts a bereaved person makes. Most of them are separate approaches the person makes themselves. That fragmentation is what the list shows, and it is the problem the strategy's example points at.

Published sources

• Who to tell about a death — nidirect
• Registrar General Quarterly Report — Northern Ireland Statistics and Research Agency

The problem statement above derives from the life-event-services playbook, published by Hypership as part of lab-notes.ai. The research is theirs; the prototype is ours.

What we built

• A web chat that opens straight into a conversation, with no app to install and no account to create.
• The agent establishes which of the published contacts apply to someone's circumstances, then brings them one group at a time rather than as a list.
• For each contact it drafts what that contact needs: a letter, an email, a text, or notes for a phone call.
• Inbound safety checks run before any conversation logic, on their own path, ahead of everything else a message might trigger.

What it does not do

• It never contacts an organisation. It drafts; the person sends. Notifying an organisation on someone's behalf needs authority that no published source establishes.
• It states no duration, waiting time, drop-off rate or saving. Nothing published measures any of them.
• It is not an official service and carries no government endorsement.