Skip to main content
Example workflow

Document chase with multi-channel reminders

An example of how staff chase missing papers from Today's packs instead of rebuilding lists from email and WhatsApp before every deadline.

Example flow from custom practice builds. Not a packaged product feature.

See it in motion

How this feels in the working day

A short simulated run of the practice UI. No live AI on this page. Open the portal demo when you want to click through the real queues.

Chase from the outstanding list

One command logs the reminder against the pack. No new email thread to lose.

Today's packsHarper & Associates

Needs you

1

Missing

2

Ready for Xero

3

Harper & Co Design

Missing: Payroll summary, Directors loan

Chase every short pack from one queue. Reminders go out, Missing clears, and you stop rebuilding lists from the inbox.

The problem

Chase lists live in three inboxes

Partners feel it when VAT week or Self Assessment season starts and nobody can see who was chased last, on which channel, or what is still outstanding.

01

Same clients, same missing bits

Purchase invoices, P60s, and bank PDFs get chased again in a new thread because the last chase is buried.

02

Channel hopping with no log

Email one day, WhatsApp the next, portal forgotten. Managers cannot tell what already went out.

03

Fire drill before filing

The outstanding list is rebuilt under deadline pressure instead of staying current through the month.

Staff and client flow

How this example runs

Staff own the Missing from client queue. Batch chase due soon, or chase one pack. Clients get a clear ask. Every chase is logged.

01Staff

Open the outstanding queue

See which clients are short on documents for the current job, sorted by deadline risk.

02Staff

Send a chase from one command

Chase due soon, chase everyone short, or remind one client via portal, email, or WhatsApp when those channels are connected.

03Client

Receive a specific request

They see what is missing on their still-needed list, instead of a vague “please send everything”.

04System

Update the pack status

When something arrives or a chase goes out, the queue reflects it so the next person does not repeat the work.

In the week

What changes in the week

Quiet gains you notice before the next filing peak, not vanity dashboards.

01

Managers see who is still short early enough to chase on the channel that gets a reply

02

Staff stop rebuilding chase lists from email search before VAT or SA week

03

Partners are pulled in for exceptions, not for “who have we chased?”

Custom each time

An example, not a product SKU

This is an example from builds like the Harper Associates portal demo. Every system is scoped to your process, branding, and channels after a discovery call.

FAQ

Common questions

Straight answers on fit, scope, and what custom means here.

Want this shaped for your firm?

Book a free discovery call. We will map your process and put a clear project price in writing if there is a fit. Try the portal demo if you want to click through an example first.