The help center needed its own Goodword address.
The support articles lived in Intercom. The custom domain would let people reach them through the Goodword site identity instead of an address owned by the support provider.
The setup required changes in two places. Intercom needed the intended hostname in its Help Center settings. The domain provider needed the corresponding DNS record so requests could be routed to the hosted documentation.
After the hostname was registered, the service also needed to provision a security certificate. Until that process completed, the address could fail or show a browser warning even when the DNS record was correct.
We checked the public path after the certificate became available. The help address needed to load over HTTPS, show the current Goodword support content, and remain usable when somebody followed a link from the application.
The custom domain did not change the inbox used for support conversations. It changed the location of the documentation people could read before or while asking for help.
The private archive includes account settings, verification records, and internal support material. Those details are not reproduced here. No customer conversation, support volume, or unpublished article appears in this entry.
The public-safe event is the domain setup. Goodword's support documentation was being given a stable address under the company domain while Intercom continued to host the actual help center.
The work followed the December consolidation of support, feedback, and general email into a managed inbox. The July change gave the written support material a similarly clear public entrance.
We registered the hostname, waited for verification, and checked the secured page.
Links already used in the application could then point to the branded address.
The result was a help address that belonged visibly to Goodword while keeping the support publishing system behind it replaceable.