Skip to main content

Casework that never falls through

Tasks and cases are created where the work starts — inside the thread — linked to the constituent, owned by a staffer, and tracked to done. And when the case needs a minister, a formal representation runs through its own gated workflow.

See the platform
Site visit — Bell St crossingFriJP
Draft minister rep — freight routeMonSW
Call Mrs Okafor re NDIS outcomeTodayET
1

Commitments become tasks, not memories

"We’ll chase the department and come back to you" is a task the moment it’s written. Pulse keeps the promise attached to the thread that made it, so follow-ups happen because the system remembers, not because someone does.

Correspondence timeline

Sarah Nguyen — Pedestrian crossing on Bell Street

9:14 am

David Chen · internal comment

@Josh can you pull the school-zone traffic counts before we reply?

9:26 am

Phone call logged — Sarah confirmed the near-miss dates

11:05 am

Emily Torres approved the reply

2:31 pm

Reply sent — 2 watchers notified

2:31 pm
2

Case files that carry their history

A case gathers its correspondence, notes, and actions in one place. When the constituent calls back in three months, anyone in the office can pick it up with full context.

In progressBell St crossing — Road Safety Program assessment
Email — Sarah Nguyen raised the crossing14 Aug
Rep sent — Dept of Transport15 Aug
Reply — assessment date confirmed22 Aug
JPJosh Patterson · due FridayOpen case →
3

Ministerial representations, done properly

The letter an MP writes to a minister on a constituent’s behalf is a first-class object, not a Word document in an email chain. Constituent authority is recorded before approval can even be requested; sign-off is always required; the letter renders on the office’s real letterhead; and a register tracks every rep against your response SLA — so the department’s clock runs visibly.

Representation — Minister for Transport

On behalf of Sarah Nguyen · office letterhead

DraftIn reviewApprovedSentReply
Constituent authority recorded — signed consent on file before approval could be requested
Sent 4 Aug · 21 days elapsedApproaching SLA
4

The same governance as the inbox

Case updates sent from shared office accounts run through the approval chain like any shared reply. Casework speed never comes at the cost of a staffer bypassing office authority.

Approval requestedjust now
ETAwaiting Emily Torres · Chief of Staff
Approve & send
Shared account sends require sign-off — every approval is logged.

Why offices choose Pulse

Sources you can inspect

Source-backed drafts include inline citations that staff can verify before review or send.

Shared sends require sign-off

AI can draft and route, but it cannot send. Replies from shared office accounts require an authorised approver; personal accounts remain owner-controlled.

Primary data stored in Australia

Primary application data is stored in Australia. Approved subprocessors and any overseas processing are disclosed in our Privacy Policy.

Keep every commitment your office makes

See the platform