Your clients approve in your portal, not on WhatsApp.

No. Each agency has its own instance, so there is no automatic sign-up. We start with a guided demo and, if it's a fit, we set it up for you.

No. Internal conversations on a task are not shown in the client portal; the client only sees what concerns them.

It can happen, especially at the start. Then you or the account manager approve it from the piece itself, and it's recorded with your name and the date, not theirs. Paste their message into the piece's comments and it's clear where that OK came from. Reminders stop as soon as the piece is approved. The next piece reaches them by email again, on your domain, with the two buttons: tapping is less work than typing. What your client will see, and the message to let them know

You invite each of them with their own access to that client's space; they all see the same pieces. Every approval and every change request is recorded with the name of whoever made it and the date, so you can see whether the OK came from marketing or from the boss, and their notes stay on the same piece instead of in three chats. What the portal doesn't do is require two approvals: if one person decides at your client, invite only them, or agree in writing who approves and who gives their opinion beforehand. How to put it in writing: who approves and how many rounds are included

It happens, and the portal doesn't stop it: what it does is make it visible. The approval of that version stays in the history with their name, the date and the version, and it doesn't go away because they ask for something else later. If you decide to make the change, your team sends the piece back with corrections from the piece itself, the new delivery is another version and the round is numbered after the previous ones: you can see it was approved and how many rounds it has taken since. What the portal doesn't decide is whether that round is included in what you agreed or billed separately: it doesn't invoice, and that's settled beforehand. The guide has the rule to put in writing: a typo, yes; the concept or the message, a new piece. What can change after approval, in writing and before the first piece

That's exactly what the portal puts in writing. Each piece records when it was sent for approval and with what deadline, when the client approved or requested changes and who did it, and how long it has spent in each status. The reminders that went out to them are in the email log, with whether they were delivered and opened. And you don't find out at the end: the approvals queue is ordered by due date, the calendar flags the ones past their deadline and, once the three reminders run out, the portal alerts the account manager and you. In the report you see how long each client takes to approve, on average, and every number opens its pieces. What the portal doesn't do is postpone the publication on its own or decide whose delay it was: postponing is a button for the team, and what happens to the date is agreed with the client beforehand. The guide has that rule and what to do when they don't reply. What to do when they don't reply: reminders, escalation and what was agreed

What changes for your team is where they deliver: the piece the client has to approve is created in the portal and the version is uploaded there, instead of being sent by chat or email. That alone gets the client their email and records the approval. The step-by-step workflow and the “My turn” filter are switched on client by client, whenever you want; the overdue notices, only if you turn them on. Each person sees their Drive folders from the Library if they connect their Google account. What there isn't: a sync with another board, or an API. Whatever you keep elsewhere stays there. What your team will see, and the questions they'll ask you

It goes in the same workshop. Tasks that aren't pieces for approval live in the same list or kanban as the rest, with the same statuses from draft to completed and grouped by person, under their own “Other tasks” tab, kept apart from content. Each one hangs from a project of that client, whether retainer, one-off or internal, and the client doesn't see it: their portal only shows the pieces that reach them for approval, their calendar and their files, never the team's tasks, costs or internal conversations. If a campaign includes pieces the client does approve, such as the ads, they follow their workflow just like a reel: there's a suggested workflow template for Ads alongside the one for Content. And for your freelancers, the cost is born with the task whether or not it goes through the client, and becomes payable on completion. What it doesn't do: measure campaign results. It doesn't connect to Meta, Google Ads or Analytics, and its reports are operational: approval times, pipeline and overdue work. What your team sees when they log in: list, kanban and “Other tasks”

Not today. PortaliaFlow focuses on approvals, production, freelancers and the client relationship. It does connect to Google Drive and Google Calendar, per user.

In the European Union (Frankfurt), on an instance dedicated to your agency, encrypted and backed up daily. If you need a data processing agreement, we'll go through it on the call.

English and Spanish. Each user picks their language and receives emails in it.

No. The calendar marks a piece as published when you say so, but it doesn't post to any network. Reports are viewed in the portal and exported to CSV; there is no PDF.

It doesn't invoice your clients, has no native app (it's a mobile-friendly web app), doesn't publish to social media, doesn't connect to Meta or Google Ads, and today has no two-factor or Google sign-in. What it does do, it does at a real agency every day. The full list of what it doesn't do