Skip to main content

​
What you’ll find on this page

White Label Configuration is the control center for your branded app. It’s the first section of the White Label Platform, under App Configuration. At the top, you’ll see two tabs:
  • Configuration: core settings that affect how your app works (name, domain, billing defaults, legal pages and the minutes warning email).
  • Appearance: the visual identity your customers will see (colors, email language, logos, favicon and default theme).
Open it here: Open White Label Configuration
White Label Configuration page on the Configuration tab with App Name, Custom Domain with the DNS Configuration button, Currency and App Language

Screenshot: the Configuration tab, with an example app name and domain.

The video walks you through the whole configuration, step by step:

Video: app name and domain → DNS Configuration (Provider and Manual) → currency, language and server location → minutes warning email and its preview → Appearance tab.

When you change anything, a bar appears at the bottom with Clear (undo your changes) and Save. Click Save before leaving the page.
Some settings can vary depending on your plan and permissions.

​
Configuration

​
App Name

App Name is shown in the sidebar, page titles, and emails. It’s the name your customers will recognize. A good rule: use the same name you use in your sales materials.
Example: if you sell “Aurora Reception,” set the App Name to Aurora Reception. In Custom Domain, enter the domain customers will use to access the app, without http:// or https://. Callin recommends using a subdomain you control, for example:
  • app.yourdomain.com
Why a subdomain matters:
  • Your root domain (like yourdomain.com) typically hosts your marketing website, landing pages, blog, and tracking scripts.
  • Keeping the product on app.yourdomain.com helps avoid conflicts and keeps your website setup independent.
Pick a simple subdomain your customers will remember: app, portal, or dashboard.

​
DNS Configuration

After you enter your custom domain, click Save, then click DNS Configuration. Until the domain is saved, you’ll see the message Please save your domain first before installing SSL or configuring DNS. DNS Configuration opens a side panel with two ways to set up DNS:
  • Provider (automatic-assisted)
  • Manual (you add the records yourself)

​
Which DNS records do I add for a subdomain?

Add one record only: an A record with your subdomain as the name (for example, app) and the IP address shown in your panel. Don’t add an A record on @ or a CNAME record, so your main website keeps working. If the panel shows an A record on @ and a CNAME record, ignore them.

​
Provider (automatic-assisted setup)

Use Provider when your domain is managed by Cloudflare, GoDaddy or Namecheap. You select your provider and Callin helps you set up the domain automatically. What you do:
1
Open the Provider tab.
2
In DNS Provider, select your provider: Cloudflare, GoDaddy or Namecheap.
3
Click Discover.
What to expect:
  • Callin will try to guide you through the DNS setup for the domain you entered.
  • If something fails, you’ll see Something went wrong. Please check your configuration and DNS records and try after some time. That usually means the DNS records don’t match what’s expected yet. Wait a little, or use Manual.
DNS Configuration panel on the Provider tab with the DNS Provider list open (Cloudflare, GoDaddy, Namecheap) and the Something went wrong message at the top

Screenshot: the Provider tab, where you pick Cloudflare, GoDaddy or Namecheap and click Discover.

Common mistake: DNS changes don’t apply instantly. If you just edited records, wait a bit and try again.

​
Manual (add DNS records yourself)

Use Manual if:
  • Your provider is not listed, or
  • Provider setup fails, or
  • You prefer to manage DNS yourself.
On the Manual tab, Callin shows Add these DNS records at your registrar. For a subdomain like app.aurorareception.example, you only need one record:
Common mistake: Adding an A record on @ when you use a subdomain. @ is your root domain, so your main website stops working. Don’t change the @ record, and don’t add a CNAME record.
If your panel still shows an A record on @ and a CNAME record, ignore them. Add only the record above, with the same IP address.
Only add an A record on @ if you want the root domain itself (like aurorareception.example) to be the app. Your website on that domain will stop working. The record includes:
  • Type (for example, A)
  • Name (for example, app)
  • Value (the destination)
  • TTL (often “300 or auto” depending on your provider)
Your workflow looks like this:
1
Open Manual.
2
Add the record at your DNS provider.
3
When the record is in place, click Install SSL to finish.
Only click Install SSL after the DNS record is added and has propagated. Propagation time depends on your DNS provider.
If you’re unsure where to add the record, search your DNS provider’s help for “add A record.” The field names in their interface can vary.

​
Currency

Currency is used for plan prices and billing. You can choose USD - US Dollar, AUD - Australian Dollar, CAD - Canadian Dollar, EUR - Euro, GBP - British Pound Sterling or BRL - Brazilian Real. Type in the search box to find one quickly. Set it to match how you plan to charge customers. This is especially important if you will create subscription plans and charge through Stripe, because customers expect consistency between pricing and billing.

​
App Language

App Language sets the default language of the app for your customers. You can choose English, Español, Italiano, Português, हिन्दी (Hindi), Deutsch, Nederlands, Français or Português (Brasil). If you serve customers in several countries, choose the language of your main audience.

​
Server location

Server location lets you choose the geographic region where your data is hosted, to meet data residency and compliance requirements. You can choose USA – Ashburn (Virginia) or Germany – Frankfurt. We recommend Germany – Frankfurt for the data of European customers. If you work with customers that have strict requirements (healthcare, finance, public sector), align this setting with what you promised contractually.

​
Privacy Policy and Terms of Use

These fields link to your legal pages:
  • Privacy Policy: where you explain how you handle personal data.
  • Terms of Use: the rules customers agree to when using your service.
Paste the full URL of each page, for example https://yourdomain.com/privacy.
Even if you’re an agency, treat this like a product: publish these pages on your main website (root domain) and link them here.

​
Minutes exhausted warning email

Minutes exhausted warning email warns your customers by email when their included minutes have been fully used.
1
Turn on Enable warning email. The email editor opens.
2
Write the Subject.
3
Choose the Body type: Normal text (plain text; line breaks are kept) or HTML (raw HTML).
4
Write the Body. By default it includes your app name and your domain.
5
Click Preview email to see the final email your customers will receive, then Close.
To edit it later, click Configure email. Remember to click Save.
Minutes exhausted warning email editor with the Subject, the Normal text and HTML body types, the Body, and the Preview email and Close buttons

Screenshot: the warning email editor, with an example app name and domain.

Tell your customers what to do next, for example: “Upgrade your plan or contact us to add more minutes.”

​
Appearance

When your domain and core settings are ready, move to the Appearance tab to match the app to your brand.
White Label Configuration page on the Appearance tab with Primary Color, Secondary Color, Email Primary Color, Email CTA Button Color, Email Language and the Logo and Dark Logo uploads

Screenshot: the Appearance tab, where you set your colors, email language, logos, favicon and default theme.

​
Colors

Click a color square to pick a color:
  • Primary Color: used for buttons and highlights in the app.
  • Secondary Color: used for accents and states.
  • Email Primary Color: the main accent color in your transactional emails.
  • Email CTA Button Color: the color of primary buttons and links inside your emails.
If your brand already has a style guide, start with your primary brand color, then pick a secondary color that looks good on both light and dark backgrounds.

​
Email Language

Email Language is the default language of the emails your customers receive. It uses the same languages as App Language.

​
Logos (light and dark)

Upload two versions of your logo:
  • Logo (Select logo): for light backgrounds.
  • Dark Logo (Select dark logo): for dark backgrounds.
Use PNG or SVG, up to 2 MB, ideally with a transparent background. The same logo isn’t always readable on both themes.
If your logo appears tiny, the image usually has a large white margin around it: Callin scales the whole image down to fit. A tightly cropped, transparent PNG usually solves it.

​
Favicon

The Favicon is the small icon shown in the browser tab and bookmarks. Click Select favicon and upload an ICO or PNG of 32×32 or 48×48 pixels, up to 1 MB.

​
Default Theme

Default Theme controls how the app looks by default:
  • System: follows each user’s device theme.
  • Light: light mode.
  • Dark: dark mode.
A practical approach: choose System if you want the app to feel native to each user’s preferences. When you’re done, click Save.