# White Label

## What it does

Marketing agencies use white label to give **their own clients** a branded place to manage **reviews**, **ratings**, and **feedback**—without our branding showing through. You control how the portal looks and who may enter it; your clients focus on day-to-day **reputation** work inside the businesses you set up for them.

{% tabs %}
{% tab title="Agency customer" %}
You paid for an agency-style subscription and will spend most of your admin time under **Agency** in the console header after you upgrade.
{% endtab %}

{% tab title="Direct customer" %}
You run your own business inside a single account and never need this page—stay in your project menus for customers, review requests, and reviews.
{% endtab %}
{% endtabs %}

***

## How to use it

1. Move to an **agency plan** when you are ready to support several client businesses from one login.
2. Click **Agency** at the top of the console to open your agency workspace.
3. Before sending invites, add **Projects**—each row is usually one client business you operate for someone else.
4. Use **Clients** to email invitations so outside contacts may sign in only on **your** portal and only into the projects you picked.
5. Use **Team** for **your internal coworkers** who should see every client; keep paying portal users under **Clients** instead.
6. Choose **Settings**, **Appearance**, then **Domain** so your name, colors, footer text, and web addresses line up. Finish **Domain** early so links and invites stop pointing people at the default host.
7. When needed, open **Email** to edit notification wording, **External links** for extra sidebar shortcuts, or **Code editor** if you want finer layout tweaks—each screen matches the labels you already see.
8. If your plan shows extra automation choices under **Agency**, review what each screen offers. Turn off or renew anything you no longer recognize.

***

## What to expect

* Finished branding and domains mean invitation mail and the sign-in experience carry **your** company identity.
* Every portal user stays tied to the **projects** you assigned; they do not browse unrelated businesses.
* **Team** seats behave like staff backstage; **Clients** behave like customers in the house—keep those roles separate.
* Email and text **review requests** share **one account-wide allowance**. Lower busy outlets by opening each project’s **strategy** limits and setting daily or monthly caps so quieter clients still get airtime.

{% hint style="warning" %}
If **Domain** is unfinished, people may still pass through the default platform address. Finish domain setup in the Agencies part of this guide before polished onboarding.
{% endhint %}

***

## Tips & common questions

{% hint style="success" %}
Pair **one paying customer** with **one primary project** most of the time. Add more projects only when that relationship truly spans multiple locations or brands you bill separately.
{% endhint %}

{% hint style="info" %}
Invitations lapse after roughly **one week**, yet you can **resend** them anytime from **Clients** or **Projects**. Your customer always chooses their own password—you never receive it.
{% endhint %}

{% hint style="warning" %}
You **invoice clients yourself**. Pick whichever bookkeeping or card processor you already trust and set service prices on your own.
{% endhint %}

{% hint style="danger" %}
Removing or pausing the wrong **project** can halt live outreach for that business. Read the confirmation text slowly before you agree.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.moregoodreviews.com/agencies/white-label.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.