How to Replace Email Chaos with a Client Portal: A Step-by-Step Guide
Tired of hunting through email threads for the invoice a client asked about three weeks ago? Here's how to set up a branded customer portal in Flitz, step by step.
If you run a Swiss SME, chances are your "client communication system" looks like this: a tangle of email threads, a shared Google Drive folder nobody can find anything in, invoice PDFs attached to messages titled "Re: Re: FW: Invoice," and a WhatsApp group that somehow also has your accountant in it. It works, sort of — until it doesn't, usually right when a client asks "what's the status of my project?" and you have to dig through three apps to answer.
A customer portal fixes this by giving each client one place to log in, see what's relevant to them, and talk to you — without giving them access to anything that isn't theirs. Here's how to move from the manual mess to an automated setup, step by step.
Step 1: Map out who needs to see what
Before inviting anyone, list your active clients and decide what each one actually needs access to. A client paying your invoices needs to see billing. A collaborator working on a shared project board probably doesn't need financial visibility at all. This is the thinking behind per-user feature toggles — Work, Chat, Invoices, Files, and AI Assistant can each be switched on or off per person. There's no one-size-fits-all setting, so you're not forced to either lock everyone out or expose everything to everyone.
Expect this step to take longer than the actual setup — it's a planning exercise, not a technical one.
Step 2: Send the invite
Once you know who gets access to what, inviting someone in is a single email. The magic-link invite flow sends your client a link; they click it, pick a password, and they're in. No account creation forms, no "forgot password" loops before they've even started, no manual credential sharing over email (which, let's be honest, is a security habit worth breaking anyway).
What to expect: your client sees a branded portal, not a generic login screen, so it reads as an extension of working with you — not a third-party tool they have to figure out.
Step 3: Turn on Work collaboration where it matters
For clients involved in active projects, switch on the Work module. They can comment on tickets and make edits directly, which cuts down the "can you also check the email I sent" back-and-forth. You keep control over the structure: moving or deleting tickets stays reserved for your team, so the board doesn't get reorganized by someone outside your company.
What to expect: fewer status-update emails, because clients can see progress themselves instead of asking for it.
Step 3: Let invoices share themselves
If a client is a billing contact, invoices are auto-shared with them the moment you issue them — no attaching PDFs, no "did you get my last email?" follow-ups. Non-billing collaborators on the same account never see financial data, even if they're active on the same Work board. This separation matters for businesses working with multiple contacts at one client, where not everyone should see what's being invoiced.
What to expect: fewer "can you resend the invoice" messages, and a cleaner audit trail of who has access to financial documents.
Step 4: Move files out of email attachments
Every customer record supports drag-and-drop file upload — share an NDA, a signed agreement, or project files directly on that client's record. Instead of searching your inbox for "the contract from last spring," both sides go to the same portal and find the same file.
What to expect: this is the step that most visibly reduces email clutter, since file-sharing threads are usually the longest-lived ones in any inbox.
Step 5: Let the AI Assistant handle routine questions
Clients with AI Assistant access enabled can ask something like "what's the status of our project?" and get an answer immediately, without waiting for someone on your team to check and reply. The assistant is scoped per client — it answers based on that client's own data and never reaches into another client's information, even though it's the same assistant across your whole portfolio.
What to expect: a drop in the small, repetitive status-check questions that otherwise interrupt your day.
Step 6: Chat without leaving the thread you're already in
With Chat enabled, conversations happen inside the context of the client's record — attached to the same place as their files, invoices, and project boards. You're not hunting for the relevant email chain months later; the history is sitting right where the work is.
Step 7: Offer a path to grow
If a client outgrows being "just a contact" in your portal — say, they want their own instance for their own business — they can upgrade to their own Flitz tenant in one click, while still keeping the collaboration link with you. It's a natural next step rather than a disruptive migration.
What changes once this is running
None of these steps require your client to learn new software beyond logging into one link. From your side, the manual work — attaching invoices, forwarding files, answering "where's the update" messages — gets replaced by access controls you set once per client. You can read more about how the setup works on the customer portal feature page.
The result isn't a flashier client experience for its own sake. It's fewer places to check, fewer things to forward, and a clearer line between what each client can and can't see — which, for most Swiss SMEs juggling several accounts at once, is the actual time saver.