Instead of scheduling URLs being "subdomain.timezest.com", partners would be able to configure a CNAME record in the DNS for their main domain - e.g. "scheduling.mymsp.com", and TimeZest would respond to requests made it it. HTTPS would be provided by Lets Encrypt, where TimeZest generates an SSL certificate for the subdomain.