Short answer: Private account details, security-sensitive procedures, legal advice, custom pricing, unapproved roadmap, confidential customer information, and claims that have not been reviewed should stay private in a Support Hub. A Support Hub should publish approved answers that help customers, prospects, search engines, AI assistants, and agents without exposing information that requires human judgment or should remain internal.
A Support Hub is not a place to publish everything.
It is a place to publish the answers that should become public source material.
That distinction matters because public support content can be read by buyers, customers, search engines, AI systems, competitors, and agents.
A Support Hub needs boundaries
A Support Hub works because it makes approved knowledge public and crawlable.
But approval-gated does not mean everything becomes public.
Some answers are useful only inside a support workflow. Some require legal, security, product, or founder review. Some depend on the customer account. Some should be handled by a human because the wrong answer could create risk.
The job is to decide which answers belong in public infrastructure and which belong in private support, internal docs, or human review.
Run the free EntityMesh scan to find which support answers should be public and which should stay private.
What should stay private?
Keep the following out of a public Support Hub unless there is a specific approved reason to publish them:
- Private customer data.
- Account-specific troubleshooting.
- Security-sensitive procedures.
- Legal advice.
- Medical, financial, or regulated advice.
- Custom pricing or negotiated terms.
- Unannounced roadmap.
- Internal strategy.
- Private partner details.
- Unsupported performance claims.
- Claims not yet reviewed by the right owner.
These materials can still inform the build. They just should not become public source material automatically.
What can usually become public?
Public Support Hub content should be stable, useful, approved, and safe to answer.
Good candidates include:
- Product definitions.
- Service explanations.
- Approved onboarding steps.
- Public policies.
- Support paths.
- Pricing factors where approved.
- Integration availability.
- Common buyer questions.
- Public troubleshooting basics.
- Glossary terms.
- Comparison criteria.
- Next-step guidance.
These pages help humans and machines understand the brand without exposing sensitive details.
Why approval matters
Approval protects brand truth.
EntityMesh can diagnose, draft, and structure Support Hub assets, but public pages should be reviewed before publication.
Who approves EntityMesh content? explains the review model.
The reviewer should confirm:
- The answer is accurate.
- The claim is supportable.
- The language is current.
- The page does not expose sensitive information.
- The next step is appropriate.
- EntityAgent can safely use the knowledge if it is included.
How to classify each question
Use a simple three-part classification:
| Classification | Meaning | Example |
|---|---|---|
| Public | Safe, approved, and useful for prospects or customers | "How does onboarding work?" |
| Private | Account-specific, sensitive, or internal-only | "Why did this customer fail payment review?" |
| Conditional | Could be public after review or with caveats | "What affects pricing?" |
This keeps Support Hub work practical.
It also helps EntityAgent avoid answering from material that should not be public.
What should happen to private material?
Private material should not be discarded.
It can become:
- Internal support documentation.
- Review notes.
- Source material for public summaries.
- Human escalation rules.
- EntityAgent refusal or routing guidance.
- Product feedback.
- Future public content after approval.
The goal is not to hide useful knowledge. The goal is to publish responsibly.
Run the free EntityMesh scan to map which repeated questions are ready for public answers.
Frequently asked questions
Should every support answer be public?
No. Only stable, approved, useful, and safe answers should become public Support Hub content.
What should stay private in a Support Hub?
Private customer data, account-specific troubleshooting, security-sensitive procedures, legal advice, custom pricing, unapproved roadmap, and unsupported claims should stay private or require human review.
Can private material still help EntityMesh?
Yes. Private material can inform public summaries, internal docs, escalation rules, and future approved answers without being published directly.
Why does this matter for AI search?
Public support pages can become source material for AI systems. That makes approval and privacy boundaries important.
How does EntityAgent handle private content?
EntityAgent should answer from approved EntityMesh knowledge and route unsupported or private questions to the correct source or human review path.