What your client sees in a white-label AI portal

A white-label client portal is the branded page your client lands on after they sign. It shows them where their AI build stands, holds what they have handed over, and tells them what happens next, all under your agency's name instead of a vendor login. In Lumina Sales it is one of four pieces of the platform, and it exists for one reason: the weeks between "yes" and "live" are where deals go cold.

This post covers what the portal is, what your client sees, what you see, and where it stops. If you are weighing whether a portal matters for a $49 a month stack, read the limits section before anything else.

What is a client portal for an AI agency?

Think of it as the client-facing half of fulfillment. The demo site is what a prospect opens before they buy. The portal is what a client opens after. Per our site, it is "a branded home for each client after they say yes": status, assets, and next steps, carrying your logo, your colors and your name.

A general definition from Teamwork, which sells project software, is a "secure, shared space where your team and your client act on the same work." That fits. The difference in an AI agency is that the work is a custom build, usually a voice agent or chat agent plus a website piece, and the client has very little idea what building one involves. The portal is where that gets explained by showing progress instead of by email.

What does your client actually see?

Four things, in the order they matter.

First, your branding. Your logo sits at the top and your colors run through the page. Your name is on it. The client never sees Lumina. They do not need to install anything or create an account to get through intake, which matters because small business owners abandon anything that looks like homework.

Second, the intake. This is the structured ask for what the build needs: opening hours and holiday cover, services with a price band for each, logo, brand colors and photos, the calendar, the phone number, and who receives the leads. It is the same list we walk through in what you need from a client before the build starts. You can change whatever the form asks by default, so a roofer is not asked about treatment rooms.

Third, status. The client can see where the job sits instead of emailing you to ask. Teamwork makes the same point about its own product: a status window is meant to cut the "any update?" pings. It also warns that a status window "still only shows what already happened," which is true here too. The portal tells a client the build is in progress. It does not give them a delivery date you have not committed to.

Fourth, next steps. After intake comes testing, then go-live. We cover the sequence in what happens after your client signs an AI buildout. The portal is where the client sees which step they are on and whether the next one is waiting on them or on you.

What do you see on your side?

You work from your agency workspace at your own subdomain. Each client has a buildout record that tracks the demo, the portal invite, the fulfillment job and onboarding as separate states, so you can tell at a glance whether a deal is stuck on intake or on the build.

The same record holds the money. You see your retail price, your wholesale cost and the margin between them. That last part is the reason the portal sits inside the same stack as ordering: you set the client's price, we charge you the wholesale setup and monthly agreed on the pricing call, and the gap is yours. The numbers behind that are in what you actually keep on a white-label AI client.

Why does the portal matter after the sale?

Because the most common failure in this business is losing momentum after a signature, not losing the demo.

A client who signs on Tuesday and hears nothing until the following Monday starts to wonder what they paid for. A client who has to dig up a logo, find their login for the booking calendar and answer six questions over three emails will do it slowly, and every slow day is a day your churn risk goes up. The portal collapses that into one link.

There is also a margin argument. Worklenz, another portal vendor, puts agencies at "between five and ten hours per client per month" on manual updates. It cites no source for that figure, so treat it as a vendor's estimate, not a benchmark. But the direction is believable. If you are the one chasing assets and answering status emails by hand, the time comes out of the markup you charged for.

What are the limits?

The portal is not a project management tool. It is not a replacement for Slack, a shared drive or your own CRM, and we do not claim it is. It is a branded status and intake surface for one kind of deliverable. If your clients expect proofing workflows, time tracking, invoicing inside the portal or single sign-on, that is a different product, and the portal-software vendors above sell those.

Second, it only helps if you use it as the default path. Teamwork says as much: if email still handles requests, the portal stays optional, and a client who has been told to "just send it over" will keep emailing. You have to send the portal link on day one and decline to take assets any other way.

Third, it does not do the build for you. Fulfillment is a separate step, ordered through the platform, and the portal reflects it. A well-branded status page on top of a slow job is still a slow job.

Fourth, I am working from what our site states today, not a feature-by-feature spec. Open the workspace before you promise a client a specific portal feature in writing.

This is also not for agencies that sell one-off websites and disappear. A portal earns its keep when you have a recurring relationship and a monthly fee to protect.

How should you introduce the portal to a client?

Do it on the call where they say yes, not afterward. Tell them they will get one link, that it has your logo on it, and that everything you need from them goes in there. Then send it before you hang up.

Keep the ask small the first time. Hours, services, logo and calendar will get a receptionist live. Photos and secondary services can follow. A client who finishes the first intake in ten minutes is a client who opens the second one.

If you are still pricing the build, do that first. The 30-minute pricing call comes before the portal invite, because the invite should arrive with a price already agreed.

FAQ

Do my clients see Lumina anywhere in the portal?

No. The portal carries your logo, your colors and your name. On published demo pages, the one thing always visible is the sandbox disclosure saying the AI is a demo and bookings in it are simulated. See the FAQ on the site for the full answer on branding.

Does the client need to create an account?

Intake does not require one. They open your branded link and fill it in, and nothing needs to be installed. What access looks like beyond intake is worth checking in your workspace, since we do not spell it out here.

Is the portal included in the $49 a month?

Yes. Client portal access is part of the plan, along with the demo site, fulfillment platform access and onboarding help for closed deals. The pricing section lists the usage limits. Client builds are separate: a wholesale setup fee and monthly, agreed on a 30-minute call.

Can I change what the intake form asks for?

Yes. Whatever the form asks by default, you can change. Cut the questions that do not apply to the trade you sell into, and keep the list short enough that a business owner finishes it in one sitting.

What happens to client portals if I cancel?

Our site says nothing is deleted when you cancel your plan, and published demos unpublish. It does not spell out the client-facing portal behavior, so read what happens if you cancel and confirm with us before you sell anyone a long contract.

Next step

Open a workspace at app.luminasales.io/signup, start a buildout record for a real prospect, and click through the client view yourself before you sell it. If you would have to apologize for anything on that page, fix it before it reaches a client.