How to run a white-label research community for a client

What a white-label research community is

A white-label research community is one that members meet entirely under your client's brand: the client's name, logo and colours at the community's own web address, on the sign-in pages and in every email, while your agency runs the research behind it. The platform supplier stays in the background, and the client sees as much of the work as you choose.

Most platforms still show their own name in a few places. Ask the supplier for a written list, so you can tell your client before the members notice. This guide covers how to set a client's community up, what members and the client see, and how to hand over at the end.

One community for each client

Run a separate community for each client, even when two clients ask similar questions. Separation keeps each client's members, settings, emails and look apart, and it keeps one client from ever seeing another's data.

In Survizo, each community has its own web address, members, settings and look, and you reach all of them from one console sign-in, with a switcher at the top of the sidebar. If the same person joins two of your clients' communities, that is two separate accounts, each with its own password. An AI report reads one community's data and no other's. See many communities, one account.

Setting up a client's community

In Survizo, a guided set-up takes you through six steps:

1. Essentials. Name the community. A web address is suggested from the name, and you can write your own.
2. Features. Choose what members get: content, surveys, discussions, the social feed, private messages and community chat. Set the joining rules here too.
3. Voice and branding. Upload the client's logo, choose a colour, and write a tagline and a welcome message.
4. Web address. Claim the address members sign in at, in the form clientname.survizo.com. HTTPS is set up for you. The address stays the community's from then on, so agree it with the client first.
5. Project timeline. Add start and end dates if the project has them.
6. Review. One last look, then launch.

You can ask the first question the same day.

What the client's members see

Members should meet the client's brand from the first email to the last survey. In Survizo:

• The address. The community's own address, which opens on its sign-in page.
• The look. The client's logo and colours in the portal, on the sign-in and sign-up pages, on the loading screen and in the browser tab. When a member adds the community to their phone's home screen, it installs under the client's logo.
• Designed pages. You design the sign-in page, the sign-up page and the members' home page from eight template packs and twenty-four blocks.
• Email. Eighteen kinds of email, from the invitation to fifteen notifications, all in the client's colours with the client's logo. Email invitations can come from the client's own address once it is confirmed.
• WhatsApp. Invitations can also go out from the community's own WhatsApp Business number, to people who have opted in, carrying the community's name and its join link.
• Their words. Rename items in the member menu, so Surveys can be Tastings or Studies, and set the portal's default language from twelve.
• A study with its own look. A single survey can carry its own logo and colours, so a study for one brand looks like that brand without changing the community.

The look is set in the Designer. See branding and white-label.

Where the Survizo name appears

Members see the client's brand everywhere except five set places. Tell the client about them before launch:

• The platform's privacy notice and terms, which members can open at the join step and from their privacy settings. They name us because they are our notice to members.
• The verification code email, which carries the client's branding and is sent from our address under the name Survizo. A plain fallback version, used only if the branded one fails to build, names Survizo in the message too.
• Invitation and sign-up reminder emails, until you confirm an address of your own. Until then they come from Survizo Invitations. WhatsApp invitations come from the community's own number from the first message.
• The default invitation footer, which reads "Sent by Survizo on behalf of" the community. You can rewrite it.
• The web address, which ends in survizo.com.

What the client sees

Some clients want only the debrief. Others want to log in and watch results arrive. Decide this with the client at the start, and give them only what they need.

In Survizo, you add a client by email on the Client access screen, for one community. They get their own client portal, and you can open up to ten sections of your console to them. Most can be view only or full access. A few sections always stay with your own team, among them other administrators, API keys, integrations, the Designer and the audit log.

A worked example, with illustrative names: your account holds three communities, and you add a coffee brand's insight lead to its community only.

With the data workspace, the client can cut results by age, gender, city and social grade. Everything the client does is recorded under their own name in your activity trail. Revoke them and their access ends at their next session refresh, usually within an hour.

Running the study

• Invite from the client's list. Upload a CSV or Excel file with the details the client already holds. Invite people by email in the client's design, or from the community's own WhatsApp Business number to people who have opted in.
• Record consent. Each member agrees to the community's terms before taking part, and the record keeps a fingerprint of the exact wording they saw.
• Ask in the way the question needs. A poll for a quick count, a survey with quotas for the measured answer, a discussion for the reasons, and a recorded interview for the detail.

Handover: what the client gets

Agree the handover when you agree the brief. A checklist:

• The debrief files. In Survizo, a slide deck opens with the community's logo and name, and a workbook names the community on its first sheet. The SPSS file arrives with labels set, and an AI report saves as a Word document with a record of what it read.
• One set of numbers. Every file uses the same question codes, so a figure on a slide matches the workbook and the data file. See analysis and exports.
• The community's future. Decide whether it keeps running for the client's next question, or closes. If you set an end date, members who open it after that date see a notice, and you keep full access.
• Client access. Keep the client's sign-in for the next project, or revoke it. You can reactivate them later.
• Members' rights. Members can still download their data or ask for it to be erased, and the community's administrator handles those requests. Agree with the client who that is after the project.
• Recordings and files. Only the community's owner, or a moderator you allow, can play a recording. Deleting a community deletes the files uploaded inside it, including recordings, so export what you need first.

To see how a client's community would look for one of your own clients, book a fit call. The Survizo for agencies page has the short version.

Frequently asked questions

Can each client have their own web address?

Yes. Each community has its own address in the form clientname.survizo.com, with HTTPS set up for you. Agree it with the client before launch, because it stays the community's address from then on.

Will members see the Survizo name?

Yes, in five set places, and you can tell your client which ones in advance: the platform's privacy notice and terms at the join step, the verification code email, email invitations until you confirm your own sending address, the default invitation footer (which you can rewrite) and the web address, which ends in survizo.com. Everywhere else, members see the client's brand.

Can a client log in and see results?

Yes, if you allow it. You add the client on the Client access screen for one community, and open up to ten console sections, most at view only or full access. Everything they do is recorded under their own name.

Can a client see members' email addresses?

Not in the data workspace. A client with data access can cut results by age, gender, city and social grade, and never sees a member's email address or national ID number.

Can I run several client communities from one login?

Yes. One console sign-in reaches every community you own, with a switcher at the top of the sidebar. Each community stands alone, with its own members, settings and look.