Remote Support Custom Domains

ScreenMeet provides the ability to customize the domain shown during a ScreenMeet Remote Support session. This allows you to provide a fully branded experience for your customers, enhancing trust and brand consistency.

There are three options available for setting up a custom domain. We recommend Option 2 for the best balance of branding, security, and implementation effort.

Option 1: ScreenMeet Subdomain (e.g., yourcompany.screenmeet.com)

This approach uses a custom subdomain while retaining the screenmeet.com top-level domain.

• Pros: This is the easiest and fastest option. It requires no technical effort or configuration from your team.

• Cons: The URL is still visibly associated with screenmeet.com.

• How to Proceed: This is an optional, add-on ScreenMeet service. Please contact our support team at support@screenmeet.com for more information.

Option 2: Fully Custom Domain (e.g., meet.yourcompany.com)

This approach uses a fully custom URL that you control, such as meet.yourcompany.com or support.yourcompany.com. This is the most popular option for a fully integrated, white-label experience.

There are two possible technical implementation paths for this option.

• Pros: Provides complete branding control and integrates with your organization's domain and security policies.

• Cons: Requires setup and coordination from your IT or DNS team.

Implementation Path A: Self-Managed Proxy

Your organization can set up a reverse proxy at a URL of your choice.

• Origin: The proxy should use https://myhelpscreen.com as its origin.

• Configuration: The proxy must be configured to forward all querystrings and headers, with one exception:

• Host Header: The Host header must be hard-coded to myhelpscreen.com.

Implementation Path B: DNS CNAME Record

Your organization can set up a DNS CNAME entry to point your custom domain (e.g., meet.yourcompany.com) at a CDN endpoint provided by ScreenMeet. This implementation also requires setting up an SSL certificate.

You have two choices for managing the SSL certificate:

1. ScreenMeet Managed (Recommended)

   • ScreenMeet will use AWS ACM (Amazon Certificate Manager) to provision the SSL certificate for your chosen hostname.

   • This requires two CNAME entries from your team: one for the actual hostname and a second for SSL certificate validation (e.g., _a79865eb4cd1a6ab990a45779b4e0b96.yourcompany.com).

   • With this approach, ScreenMeet manages the automatic renewal of the certificate. The certificate issuer will be listed as Amazon.

2. Customer Provided

   • Your organization can provide an SSL certificate that you provision yourselves.

   • ScreenMeet will import this certificate into our CDN.

   • This approach requires your team to provide an updated certificate before it expires (all SSL certificates have a maximum lifetime of 2 years).

Option 3: Hosted Custom Landing Page (e.g., yourcompany.com/support)

This option involves creating and hosting your own webpage that acts as a portal or entry point for your ScreenMeet sessions. This page is built and maintained entirely by your organization.

• How it Works: You build and host an HTML page on your own website. On this page, you would place a button or link that uses your ScreenMeet session URL (or an API call) to launch the support session.

• Pros: You have 100% control over the branding, user experience, and hosting environment.

• Cons: This option requires web development resources, hosting, and ongoing maintenance from your team.

• Example code: https://codebeautify.org/htmlviewer/y253b1549