A client portal connected to your files

A client portal is useless if the client has to learn how to use it. Ours takes both doors: their online client area, or a simple email they just reply to.

Published on 28 August 2026

One file, one thread, the whole history

Every client has their own file, with their contacts, their documents and the full conversation. Whatever the client writes arrives attached to the right file, whether it comes through their client area or by email.

Linking by email relies on a short reference placed in the subject line. The client replies as they would to anyone, with nothing to install and nothing to remember. An address the file doesn't know is ignored and logged: nobody invites themselves into a client file.

Internal notes stay internal

An internal note is not the same thing as an on-screen message, and it is never passed on to the client. The filter is applied on the server side, not in the display: it is not a matter of discipline, it is a matter of how the thing is built.

An open request stays visible, a handled request gets closed

When a client writes in, the file moves to "request to handle", with how long it has been waiting shown. If the message contains an urgency signal, a formal notice or a tax inspection, it jumps to the top with its reason.

A request is only closed by an explicit action: ticking that this reply handles the request, or marking it as handled when everything was sorted out over the phone. Replying is not enough, because "I'm on it" is not a resolution. The client is told the request is closed and can reopen it simply by replying.

A suggested reply, never sent on its own

As soon as a client message comes in, the assistant drafts a suggested reply from the client file summary, past exchanges and the knowledge base. It waits in the text box, with the points to check flagged.

You send it with one click, or you edit it, or you ignore it. Nothing goes out without a human. The file summary itself regenerates when you open the file, if messages have come in since last time.

Who sees what

A client file is visible to its leads and to management. The portfolio is built when your clients are imported, lead column included, then corrected by hand as needed. A file with no exchange for twelve months archives itself, and the first message wakes it up.

What it isn't

This is not a document management system and it does not replace your archiving. We add the context: a document cited in a thread can point back to the original that lives on your side. Your vault stays your vault.

Going further