TL;DR
Prepare the approved materials your team already uses to explain your brand, product, service, policies, process, and proof. Useful source material can include product pages, service pages, FAQs, support tickets, sales questions, onboarding docs, demo notes, customer emails, screenshots, testimonials, case studies, policy notes, approved terminology, and topics that should stay private. EntityMesh uses this material to build approval-gated Support Hub and Answer Hub infrastructure.
Who this is for
- Founders preparing for an EntityMesh build.
- Marketing leads gathering public source-of-truth material.
- Support and customer success leads collecting repeated questions.
- Product owners clarifying approved terms, proof, and policies.
Does source material need to be perfect?
No.
Source material can be raw. Notes, exports, tickets, transcripts, screenshots, and rough documents can be useful if the facts can be reviewed.
The goal is not polish. The goal is to give EntityMesh enough source material to structure accurate, approval-gated public answers.
EntityMesh should not invent missing proof, customer results, legal claims, timelines, pricing logic, or product behavior.
What should you gather first?
Start with existing public pages:
- Homepage copy.
- Product or service pages.
- Support docs.
- FAQ pages.
- Policy pages.
- Case studies.
- Public proof assets.
- Approved comparison language.
Then add the materials your team uses privately:
- Sales questions.
- Support tickets.
- Onboarding docs.
- Demo notes.
- Customer emails.
- Screenshots.
- Implementation notes.
- Internal explanations that may be safe to summarize.
These inputs help EntityMesh identify what can become Support Hub answers, Answer Hub pages, knowledge-base guides, FAQs, glossary definitions, or EntityAgent source material.
What should be flagged before review?
Flag anything that may be private, sensitive, unapproved, customer-specific, legal-adjacent, security-related, or operationally confidential.
Examples include:
- Customer-specific information.
- Sensitive security details.
- Private operations.
- Legal or compliance content.
- Confidential roadmap items.
- Unapproved pricing logic.
- Account-specific troubleshooting.
- Unsupported performance claims.
Not everything submitted becomes public. Client approval determines what publishes.
Who should review the material?
Assign review owners before the approval stage.
Useful reviewers can include:
- Founder or executive owner.
- Product lead.
- Marketing lead.
- Support lead.
- Sales lead.
- Legal or compliance reviewer when needed.
Reviewers should confirm that public answers are accurate, current, supportable, and safe to use as source material.
Frequently asked questions
Can EntityMesh build from nothing?
EntityMesh can identify gaps and draft structures, but public claims should be grounded in approved source material. It should not invent proof or unsupported claims.
Does everything I share become public?
No. Source material can inform the build without becoming public. Private, sensitive, customer-specific, legal, security, and confidential operational details should be flagged.
Who decides what publishes?
The client approves what publishes. EntityMesh should not publish source-of-truth content without review.
What if my material is messy?
That is normal. Messy source material is still useful if it can be grouped, labeled, and reviewed by the right owner.
Why does source material matter for EntityAgent?
EntityAgent answers from approved EntityMesh knowledge. Better reviewed source material creates a stronger approved answer base.