Skip to main content

The Pulse Engine

Six stages turn incoming correspondence into work your team can review and send. Every one is built for parliamentary offices — grounded in retrieved sources where available, checked before staff decide, with primary application data hosted in Australia.

See the platform

Stage 01 · Gather

Gather and normalise every channel

Every email, social message, logged call, and letter flows into a unified stream. Pulse normalises format, reconstructs threads across forwarded chains, and extracts attachments with OCR — downstream stages see a single, consistent document format.

1.1Gmail and Outlook via full OAuth sync, plus IMAP
1.2Messenger, WhatsApp, and Instagram DM on the same spine
1.3Thread reconstruction across forwarded chains
1.4Attachment extraction with OCR for scanned documents

Stage 02 · Classify

Understand what each message is about

Pulse reads every message the way an experienced staffer would — what it's about, how urgent it is, how the constituent feels, and which policy area it touches. It recognises people, legislation references, and places, so the queue arrives triaged.

2.1Category, topics, priority, and sentiment on every message
2.2Named entity recognition for people, legislation, and places
2.3An AI summary on arrival, before anyone opens it
2.4Spam and unsubscribe handling built in

Stage 03 · Retrieve

Find the answer in your own records

For knowledge-grounded replies, Pulse searches the records your office already knows — Hansard contributions, past correspondence, policy documents, and constituent records — and surfaces relevant passages even when the wording is completely different. Every retrieved passage carries its source, so staff can see where the context came from.

3.1Hybrid retrieval — semantic search and keyword search together
3.2AI reranking of candidate passages for relevance
3.3Source provenance on every retrieved passage
3.4Manual mode — hand-pick the documents that inform a reply

Stage 04 · Generate

Draft with citations, not guesswork

Pulse brings retrieved office context and, when enabled, approved web results into the drafting process. Source-backed claims carry citations, while Pulse Voice keeps the tone and structure of the address the reply will send from.

4.1Knowledge Library and optional approved web grounding
4.2Inline citations on source-backed claims
4.3Pulse Voice — learned from each address's own sent mail
4.4Citations preserved through every edit and approval

Stage 05 · Guard

Check claims before sign-off

For source-backed drafts, a groundedness check can compare the result with its sources and flag unsupported statements. Citations stay attached through review, and shared office replies require an authorised approver before send.

5.1Groundedness check against the retrieved sources
5.2Unsupported claims flagged before review
5.3Citations attached for the approver, stripped only on send
5.4Authorised sign-off for shared office sends

Stage 06 · Secure

Protect it like government data

Public Pulse stores primary application data in Australia. Approved subprocessors may process data overseas under the safeguards and disclosures in our Privacy Policy. Pulse is CASA Tier 2 assessed, compliant with the Privacy Act 1988 (Cth), and designed to meet the security requirements of parliamentary offices.

6.1CASA Tier 2 assessed
6.2Primary application data hosted in Australia
6.3Privacy Act 1988 (Cth) compliant
6.4Row-level security with full tenant isolation

Pulse connects to your entire office

Connect your existing tools in minutes. No migration required.

Set up in under an hour
Integrates into your current channels
Follows your existing approval workflows
Routes work to the right team member
Pulse

See the whole pipeline run on your own correspondence