FlowsBook a callSign inCreate free accountSign up
AI employees and automation

White label AI employees: what carries your brand, and what does not

What you can brand when you resell AI employees: logo and colour, emails from your own domain, the app on your own web address. And the parts that stay xMap's.

Part of the guide AI employees

By the xMap team · · 4 min read

With white label ai employees in xMap Flows, a reseller or agency can put its own logo and colour on the app, on shared pages, emails and PDF reports, send the AI employees' emails from its own domain, and open the app on its own web address. What it cannot remove is a small Powered by xMap Flows line, and account emails such as sign-in codes still come from xMap. Knowing both lists before you sell saves an awkward conversation later.

This article is for resellers, consultancies and agencies who want clients to see their brand when they use AI employees. It goes through each branding option, what the client sees, a made-up reseller's setup, the honest limits, and the order to set things up in. The AI employees for agencies page covers the wider partner offer.

The three layers of branding

1. Logo and colour

An organization's admins upload a logo (with a version for dark mode if they like) and pick a colour. The logo then appears in the app's menu and editor, on shared maps, lists, dashboards and client views, at the top of emails the AI employees send, and on the first page of PDF reports. The colour replaces the default blue on buttons, headings and charts. A colour too light to read white text on is refused, so pages stay readable.

2. Email from your own domain

By default, emails from AI employees come from xMap's address with your organization's name shown as the sender. You can instead send them from an address at your own domain, such as reports@yourcompany.com. Adding the domain gives you three DNS records to add where your domain is managed; once they check out, the AI employees' emails, alerts, scheduled exports and approval requests go from your address. xMap checks the records each day and switches back to its own address, and tells your admins, if they disappear.

3. Your own web address

Organizations on a paid plan can open the app on a subdomain of their own, such as flows.yourcompany.com. You prove you own the name with a DNS record, then point it at the app. On that address, the sign-in pages and the app show your logo and name instead of xMap's, your colour is applied, and shared links use your address.

What stays xMap's

  • A Powered by xMap Flows line stays on the sign-in pages of your own address, and a Made with xMap Flows line on shared pages.
  • Account emails (sign-in codes, invitations, password resets, billing) come from xMap, not from your domain.
  • Links inside emails point to xMap's own address.
  • Signing in through an outside account provider is not offered on your own address; people sign in there with their email and password.
  • The PDF guides and xMap's own pages keep xMap's brand.

A worked example

This example is made up. A consultancy in Sao Paulo sells a location intelligence service to retail chains in Brazil and Chile. It wants clients to see its name, not a third party's.

  1. In each client's organization it uploads its own logo and sets its green as the colour.
  2. It adds its domain for email in its main organization and in each client organization, so weekly reports arrive from an address at its own domain.
  3. It sets up insights.its-domain.com as its own address and gives clients that link to sign in.
  4. Each client gets a client view on that address with the results of the AI employees the consultancy runs for them, and a monthly PDF report with its logo on the cover.
  5. In its proposals it says the service is built on xMap Flows, and that sign-in codes come from xMap.

Clients spend their time inside the consultancy's brand. The reports, alerts and pages they read every week all carry it.

Mistakes to avoid

  • Branding before the work is right. A logo on a weak report is still a weak report. Get the AI employees useful first.
  • Forgetting the DNS step. Email from your domain and your own address both need records added where the domain is managed. Plan a day for someone with access to do it.
  • Hiding the platform. Clients notice the Powered by line. Mention it up front.
  • A colour with poor contrast. If your brand colour is pale, pick its darker shade for buttons.
  • One organization for all clients. Branding is set per organization, so separate clients also lets you brand each one differently if needed.

Setting it up, in order

  1. Make one organization per client and build or import the AI employees each one needs.
  2. In Settings, Logo and colour, upload the logo and choose the colour.
  3. In Settings, Email sender, add your domain and the three DNS records it shows, then press Check.
  4. If you are on a paid plan, in Settings, Your own address, add the subdomain, add the DNS records, and check it.
  5. Make a client view for each client and send them the link.

A good first branded AI employee is a monthly market note: Schedule, Area of interest, Nearby places, xMap LLM and Make a report, which puts your logo on the cover. Start from A monthly brief on your store network or Rating watch for my clients.

Questions

Can I remove the Powered by xMap Flows line?

No. It stays on your own address's sign-in pages and as a Made with xMap Flows line on shared pages.

Do sign-in emails come from my domain?

No. Account emails such as sign-in codes and invitations always come from xMap. Your domain is used for what the AI employees send.

Is my own web address available on the free plan?

No. It is for organizations on a paid plan. Logo, colour and email from your domain do not need one.

Can each client have a different brand?

Yes. Branding is set per organization, so each client organization can carry your brand or the client's own.

Templates that do this

Read next

More on ai employees and automation · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.