Overview

White Label allows you to make your application look completely your own. You will no longer see the Callin.io branding, but instead your logo, your colors, and your domain. This means that when your customers log in, everything they see will match your brand, from the browser tab to the buttons in the interface.

Step 1: Access the White Label CMS

First, you need to reach the place where all these options are configured. From your main dashboard, click on the settings icon in the upper right corner. This will open the configuration CMS. In the left-hand menu, select White Label. This is where you will define how your application looks and how it is accessed. Tip: take a few minutes to explore this section. Every field you complete here has a direct impact on how your users perceive your product.

Step 2: DNS Configuration

Before changing logos or colors, the first and most important step is making sure your domain is properly configured. It is recommended to always use a subdomain (for example: app.yourdomain.io) rather than pointing the root domain. Using the root domain (yourdomain.io) may cause conflicts with your main website or with other services already running. In your DNS provider (Cloudflare, GoDaddy, Namecheap, etc.), add the following records: Type: A
Host: app
Value: 3.84.157.237
TTL: Automatic or 3600 seconds
Type: CNAME
Host: www
Value: app.yourdomain.io
TTL: Automatic or 3600 seconds
With this setup, anyone typing app.yourdomain.io will access your application directly, and if they type www.yourdomain.io, it will redirect correctly. Practical advice: if you manage multiple services under your domain, create a separate subdomain for each one. For example:
app.yourdomain.io → your application
api.yourdomain.io → your API
help.yourdomain.io → your help center
This keeps everything organized and prevents conflicts. Keep in mind that DNS changes are not instant. They can take anywhere from a few minutes to 24 hours to propagate depending on your provider. Be patient and avoid making repeated changes thinking it is not working.

Step 3: General Application Settings

Once the domain is set, you can move on to giving your application its identity.
App Name: This is where you decide what your app will be called. This text will appear in the browser tab and in some internal notifications. Example: if your company is Finance Pro, you can write “Finance Pro” or “Finance Pro Manager”. Tip: use a short, recognizable name. Very long names may be cut off in the browser tab.
Domain: This field is where you must enter the exact subdomain you configured in DNS, for example: app.yourdomain.io. If it does not match your DNS configuration, the application will not load.
Logo: Here you upload the main image of your brand. This is not just a visual detail: this logo will be the first thing your customers see when they log in. Recommendation: use a high-quality PNG with a transparent background, 200x200px in size, and under 2MB. Example: if your logo has different versions (horizontal, vertical, icon-only), choose the one that looks best in a square format.
Favicon: The favicon is the small icon that appears in the browser tab next to the page title. Even though it may seem minor, it adds professionalism when your customers work with multiple tabs open. Use a favicon of 32x32px or 64x64px in PNG format. Keep it simple so it is instantly recognizable.
Colors: Here you customize buttons, links, and key interface elements. This is one of the strongest ways to reflect your brand identity. Practical tip: if you already have a corporate website, use the same HEX codes here. Example: #003366 for your brand’s blue. This ensures consistency and builds trust with your customers. Avoid colors that are too similar to each other (for example, light gray background with dark gray text), as it can affect readability.

Step 4: Advanced Options

Now that you have defined the visual identity, you can fine-tune technical settings.
Currency: Define the currency in which prices and payments will be displayed in your app. Example: USD for dollars, EUR for euros. Tip: choose the currency most commonly used by your customers. This will prevent confusion in billing.
BYOC (Bring Your Own Carrier): This option allows you to connect your own telephony provider instead of the built-in one. It is useful if you already have better rates or an active contract. Advantage: greater control over call costs.
Custom Recording: Enable this feature if you want your calls to be recorded for free within the platform. This prevents additional Twilio charges. Tip: check your local regulations on call recording to make sure you comply with legal requirements.
Custom AMD (Answering Machine Detection): This automatically detects voicemail boxes. Configuring it here saves costs and improves your call flows. Example: if your team runs mass calling campaigns, this option prevents wasting time with voicemail.

Common Mistakes and Solutions

Logo or favicon not displayed → make sure they meet the recommended size and format.
Domain not working → double-check your DNS setup and confirm you are using a subdomain.
Colors not applied correctly → verify the HEX code entered is accurate.
Changes not saved → always click Save Settings before leaving.

Your Brand, Your Application

With this setup, your platform is now ready to reflect your brand identity and custom domain. Every detail, from the logo to the colors, helps your customers feel they are working directly with your company rather than a generic service.

Video: Configuring White Label Settings Video 1

Watch this video to see a full walkthrough of configuring your White Label Settings in the CMS. Step 1 - White Label Settings

Video: Configuring White Label Settings Video 2

Step 2 - White Label Settings