White Label Setup Guide

• A myCRMSIM account with white label access enabled
• A domain you own (e.g., app.yourdomain.com)
• Access to your DNS provider (GoDaddy, Cloudflare, Namecheap, Route53, etc.)
• Your brand logo (PNG, JPG, SVG, or WebP — max 2MB)
• Your brand favicon/icon (same formats — max 2MB)
• (Optional) GHL OAuth credentials if you use GoHighLevel integration

1. Log into the myCRMSIM dashboard 
2. Click the "Setting" tab at the bottom of the left-hand sidebar.
3. Click the "Branding" tab from the top navigation menu.
4. Switch the "Enable Branding" toggle to ON.

Once enabled, all branding configuration fields will appear.

Fill in these required fields:

Click the color swatch to open the color picker. Enter a hex code directly or use the picker.

(Enabled or Disabled from myCRMSIM)
Toggle features on or off depending on what you want your users to see:

1. In the Integration Settings section, find the Domain / Hostname field.
2. Enter your domain without https:// or trailing slashes.
• ✅ Correct: app.yourdomain.com
• ❌ Wrong: https://app.yourdomain.com/

This proves you own the domain. AWS needs this to issue an SSL certificate.

Use the copy button to copy the exact values.

This points your domain to the myCRMSIM servers via CloudFront.

Go to your DNS provider and add both CNAME records. Here are quick instructions for common providers:

1. Go to your domain → DNS → Records
2. Click "Add Record"
3. Type: CNAME, Name: (paste), Target: (paste)
4. Important: Set the proxy to DNS only (grey cloud icon). Orange cloud (proxied) will block SSL validation.
5. Repeat for both records

1. Go to My Products → DNS → Manage
2. Click "Add" under Records
3. Type: CNAME, Name: (paste), Value: (paste), TTL: 1 hour
4. Repeat for both records

1. Go to Domain List → Manage → Advanced DNS
2. Click "Add New Record"
3. Type: CNAME Record, Host: (paste), Value: (paste), TTL: Automatic
4. Repeat for both records

1. Go to Hosted Zones → Select your domain
2. Click "Create Record"
3. Record type: CNAME, Name: (paste), Value: (paste)
4. For root domains (@), use ALIAS instead of CNAME pointing to the CloudFront distribution
5. Repeat for both records

1. Go back to your myCRMSIM Settings page.
2. Click the Check button again.
3. The system will start polling for verification.

These fields are only needed if you use GoHighLevel (GHL) integration:

1. Click Save Branding Settings.
2. Wait for the success confirmation.
3. Open your custom domain in a new browser tab (e.g., https://app.yourdomain.com).

Verify the following:

With our white-label portal, you can enable a client or end-user (Subaccount Admin) to access the portal, log in under your branding, and manage their own devices and messages via the sub-account area.

• Log in to your myCRMSIM dashboard as the agency/master account
• Navigate to the Sub-account Admin section and create a new user

• Enter a name for the user/sub-account (e.g., [email protected])
• Assign the workspace/sub-account that this user will manage
• Ensure the workspace has already been connected and is visible
• Set the user’s status to Active

• Option A: Set a device allowance (e.g., 1 device) → the user will be able to add up to that many devices themselves
• Option B: Assign specific device(s) → select device(s) from your existing list and assign them to the user so they do not have to add them themselves

• Once the sub-account user is created, the login details are automatically sent to the user’s registered email address
• The email will include:
• The login URL (white-labeled under your branding, e.g., your custom domain like https://smsapp.yourdomain.com)
• The username (usually the user’s email)
• The password (if included or set during creation)

• Verify DNS records are exactly as shown (no extra spaces or missing dots)
• Cloudflare users: Make sure proxy is OFF (grey cloud) for the SSL validation record
• Wait at least 30 minutes — DNS propagation takes time
• Use DNS Checker to verify your CNAME records are visible globally

• Make sure the routing CNAME (Record 2) is also added
• Clear your browser cache or try incognito mode
• Wait 15 minutes — CloudFront deployments take time to propagate globally

• Check that the domain in settings exactly matches what you're visiting
• Make sure branding toggle is ON and settings are saved
• Hard refresh the page (Ctrl+Shift+R / Cmd+Shift+R)

• File must be PNG, JPG, SVG, WebP, or ICO
• File must be under 2MB
• Re-upload and save again

• Remove https:// or http:// from the domain
• Remove any trailing slashes (/)
• Domain must contain at least one dot (e.g., app.yourdomain.com)

• DNS records must be configured correctly before domain verification can succeed
• Never share your Client Secret or OpenAI API Key
• Subdomains work best (e.g., app.yourdomain.com). Root domains require Route53 with ALIAS records
• After any branding changes, users may need to hard-refresh their browser to see updates
• The white label applies to all users who access the platform through your custom domain