Domain
Your white-label domain is how customers reach your branded version of Insighto. They sign up at app.youragency.com, your chatbots load from chatbot.youragency.com, and your scripts hit api.youragency.com. This page is the DNS + Insighto side of getting that working.
DNS setup — A records, not CNAMEs
Insighto serves your white-label traffic from two static IPs. You need A records, not CNAMEs. CNAMEs won't work because the app and chatbot live on different IPs.
| Hostname pattern | Record type | Value |
|---|---|---|
app.youragency.com | A | 57.151.120.174 |
api.youragency.com | A | 57.151.120.174 |
chatbot.youragency.com | A | 172.174.188.46 |
(Use any subdomain names you like — app / api / chatbot is the convention.)
Add the three records in your DNS provider, save, and wait for propagation (usually under 5 minutes; can be up to a few hours depending on TTL).
Save in Insighto
Open Manage Agency → Domain. Three JSON fields:
{
"appDomain": "app.youragency.com",
"apiDomain": "api.youragency.com",
"chatbotDomain": "chatbot.youragency.com"
}
Click Save.
The form locks after the first save
This is one-shot. Once you click Save, the form locks itself and you can't change the domain from the UI. If you need to change it later, you'll need support intervention. Triple-check the spelling before saving.
(Why? Subaccounts get provisioned with URLs tied to the domain. Changing it mid-flight would break every customer link.)
Verify it works
After saving and DNS has propagated:
- Open
https://app.youragency.com— should load the Insighto sign-in screen branded as your agency. - Look at the favicon and title — should be your agency's, not Insighto's.
- Sign up a test account at
https://app.youragency.com/signup.
If the page doesn't load: re-check the A record values, and confirm propagation with dig app.youragency.com from a terminal.
Where to next
- Branding — make sure logo, color, and SMTP are also set.
- Subaccounts — the customers who'll use your domain.
- Getting started — the 7-step path.