White-label WordPress management: check more than the logo
A report can carry your logo while the next email still shows the platform’s name. Neither result is surprising once you look at how many separate surfaces a client encounters.
Before selling white-label management as part of a care plan, walk through that journey as a client. Do not begin and end with the branding settings screen.
Map the surfaces your client will see
Start with the invitation email. Open its link, inspect the portal and submit a harmless test request. Preview a report and its delivery email. If the client has WordPress administrator access, inspect the connector’s plugin listing and settings too.
Write down which identity appears at each step. Distinguish the visible sender name from the actual sending address and Reply-To address. A branded display name does not establish that mail is sent from your domain.
Some identities should remain explicit. Billing records, legal notices and technical diagnostics should not misrepresent who operates the software. White-label presentation is not a promise that a person inspecting source code or network requests cannot identify the underlying platform.
What the current IrmaWP work covers
Agency’s white-label controls now include an agency profile for client surfaces and connector presentation, with a branded connector download. Applying it to connected sites depends on a compatible connector and successful synchronization. Older installations may need an update before the branding action is available.
Custom portal and sender domains have verification workflows. They also require provider configuration, DNS ownership checks and successful activation. Do not announce a client domain merely because you typed it into a form. Confirm the portal opens with valid HTTPS and that a test message actually arrives from the expected identity.
The latest domain workflows require deployment acceptance; availability should be confirmed with the IrmaWP team. A local test with a simulated mail provider is not proof of live email delivery.
Keep access separate from appearance
Starter and Pro can use a client portal; Agency adds white-label controls. Branding should never expand the set of sites a client can see. Test with two clients and confirm that each sees only the intended scope.
Also test the unglamorous cases: a failed invitation, an expired link and a teammate who has less access than the owner. Keep a record of what you actually checked before describing the service to a client.
Use the white-label feature page as the scope reference. Promise the surfaces you have verified, and keep any pending domain or email setup out of the completed-work column.
Have a correction or a workflow we should cover? Tell the IrmaWP team.