Client uploads and messaging in one place
An example of a client view that shows the checklist, still-needed items, and conversation without scattering files across WhatsApp.
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.
Uploads and messages on one pack
Client and staff talk next to the checklist, not in a side chat.
Alex Harper
Attached payroll summary. Is the directors loan schedule still needed for SA?
Questions and uploads stay on the same pack, so staff are not hunting WhatsApp for which job a PDF belongs to.
The problem
Clients send files wherever is easiest
Photos of invoices, half-named PDFs, and questions arrive in personal WhatsApp and random email, while the pack list lives somewhere else.
Uploads without context
A PDF arrives with no job reference, so staff spend time guessing which pack it belongs to.
Questions split from documents
The client asks in one channel and uploads in another. History is hard to reconstruct.
No shared progress
Clients do not know what is still missing, so they either over-send or go quiet.
Staff and client flow
How this example runs
Clients work inside a portal shaped for the pack. Messages and uploads stay attached to that work.
Sign in to their pack view
They see required documents, still-needed items, and what is already accepted.
Upload or reply in context
Files and messages sit against the same job, so staff are not hunting threads later.
Respond from the practice side
Notes and replies stay with the pack. Chase and review use the same status.
Keep progress visible
Both sides see movement on the checklist without a status meeting.
In the week
What changes in the week
Fewer “did you get my WhatsApp?” loops. Clearer ownership of what is still missing.
Clients upload against a checklist instead of scattering files across channels
Staff answer questions next to the documents that matter for that pack
Progress is visible without rebuilding status from email search
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.
Explore
More example workflows
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.