# Help Scout Docs

- Canonical HTML: https://growth.iangoh.com/sources/help-scout-docs-docs-helpscout-com/
- Original source: https://docs.helpscout.com/article/1329-control-access-to-docs-using-beacon
- Domain: docs.helpscout.com
- Latest check: 2026-05-28
- Channels: AI, Brand, Customer Success, Onboarding, Operations, Product, SEO, Support, UX, Website

## Cited GrowthDex tactics

- [Article-to-Beacon contact link at the point of confusion](/growth-ideas/article-to-beacon-contact-link-at-point-of-confusion/) - Add a plain contact link at the end of docs articles so the user can open Beacon with one click when the answer did not quite finish the job.
- [Availability-gated docs chat with message fallback](/growth-ideas/availability-gated-docs-chat-with-message-fallback/) - Only surface live chat on docs pages when staffing is real, and fall back to message capture when the team is offline instead of pretending the handoff is immediate.
- [Beacon-only docs site behind login](/growth-ideas/beacon-only-docs-site-behind-login/) - Keep the docs archive off a public site until logged-in users can reach it through Beacon, so onboarding and support answers stay usable without turning unfinished docs into public scenery.
- [Customer-facing docs on a brand subdomain](/growth-ideas/customer-facing-docs-on-brand-subdomain/) - Put the help center on a branded subdomain instead of a vendor URL so the support surface inherits the same trust signals as the main product.
- [Internal runbook collections feeding Beacon AI](/growth-ideas/internal-runbook-collections-feeding-beacon-ai/) - Keep internal-only runbook collections inside the same docs system so support and AI answers can use them without exposing every troubleshooting note to the public.

## Related reading

- [GrowthDex Blog](/blog/)
- [All growth ideas](/growth-ideas/index.md)