How to set up Callin.io in White Label mode for clients

I went through this process when I wanted my clients to see everything under my logo and domain instead of Callin.io’s. The White Label setup is straightforward, but there are a few important details:

1. Twilio credentials.
   In the White Label setup, add your Account SID and Auth Token. They must be named exactly “account_sid” and “auth_token” or it won’t work.

2. Custom domain.
   Point a subdomain (e.g., app.mycompany.com) to the White Label workspace. This way, clients log in via your brand, not callin.io.

3. Numbers and traffic.
   Even in White Label mode, calls still run through Twilio. So number purchase/import and caller ID management work the same as in standard mode.

4. Common mistakes.

• Using restricted Twilio credentials: make sure the account can handle both calls and numbers.

• No active number: without one, outbound agents won’t work.

• Forgetting to test with a real call before inviting a client.

5. Final test.
   Create a test agent, run one inbound and one outbound call, and confirm both branding and call flow behave as expected.

The best part is that once configured, your client won’t notice Callin.io behind the scenes—they’ll see only your brand and domain.

i’d start by getting the white-label domain and branding sorted, then test the full client setup before offering it widely. with Twilio, double-check the Account SID and Auth Token, keep credentials out of frontend code, enable 2FA, and check number permissions and billing so you don’t run into surprise call failures 😝