2. What it is
Product Profile is a structured workspace form that stores foundational business context for assistant grounding.
Product Profile
Give your assistant the right business context from day one
Maintain core product and positioning fields in one place so answers remain aligned as your offering evolves.
What Product Profile controls
Product Profile fields are injected into assistant context to improve domain grounding across every conversation. By defining your product description, target audience, and key features in one structured form, the assistant understands your business from the first message. This baseline context reduces hallucinations and keeps answers relevant to your specific market and offering.
Product description
A plain-language summary of what your product does, used by the assistant to frame answers with accurate business context.
Target audience
Define your primary customer profile so the assistant tailors recommendations and language to the right user persona.
Key features list
Enumerate your core capabilities as customer-facing outcomes so the assistant can reference them accurately in comparisons and overviews.
Commercial and positioning context
Pricing summary and competitive advantage fields help responses stay aligned with your market positioning and commercial messaging. When customers ask about pricing or how your product compares, the assistant draws from these fields instead of generating generic or inaccurate responses. This prevents off-brand positioning in sales-adjacent support conversations.
Pricing summary field
Provide high-level pricing framing and tier logic so the assistant can give consistent, accurate pricing context before detailed plan questions.
Competitive advantage field
A short differentiation statement grounded in real capabilities that the assistant uses to position your product authentically in comparative answers.
Consistent positioning cues
Commercial fields are applied across all conversations, ensuring every customer interaction reflects your intended market narrative.
Centralized assistant grounding
Instead of repeating core business context across many pages and snippets, teams can maintain a single canonical profile entry that serves as the baseline for all assistant interactions. This reduces duplication, prevents conflicting information, and makes updates trivial since there is only one place to change. Product Profile works in concert with other knowledge layers to provide both broad context and specific detail.
Single place for core product facts
Maintain one authoritative source for business fundamentals instead of scattering them across multiple knowledge entries.
Editable in app by workspace
Update profile fields directly in the application interface without needing developer access or deployment cycles.
Used with other knowledge layers
Product Profile provides the foundation that pages, snippets, and custom answers build on for a coherent knowledge architecture.
Field-by-field behavior impact
Product Profile fields shape baseline assistant framing. Keep each field specific so answers stay aligned with your positioning.
| Field | What to include | Assistant impact |
|---|---|---|
productDescription | Plain-language description of what your product does and who it serves. | Improves baseline framing in product overview responses. |
targetAudience | Primary customer profile and common buyer/user context. | Reduces mismatched recommendations for wrong user types. |
keyFeatures | Discrete features phrased as customer outcomes, not internal jargon. | Improves feature comparisons and first-response relevance. |
pricingSummary | High-level pricing framing and tier logic without legal contract text. | Keeps pricing explanations consistent before deep plan questions. |
competitiveAdvantage | Short differentiation statement grounded in real capabilities. | Prevents generic or off-brand positioning in comparative answers. |
3. When to use it
- At initial assistant setup for baseline grounding.
- After major repositioning, pricing, or product updates.
- When answers drift from intended market framing.
4. When not to use it
- For detailed operational procedures (use pages/snippets).
- For exact legal or policy wording (use custom answers).
- For rapidly changing release notes (use knowledge sources or snippets).
5. Setup steps in app
- Open Product Profile in the Knowledge section.
- Fill product description and target audience.
- Add key features (one by one) for product specificity.
- Add pricing summary and competitive advantage.
- Save and review assistant answers for alignment.
6. Best use cases
- Keeping positioning consistent across multi-agent teams.
- Reducing ambiguous answers around target customer fit.
- Improving first-response quality for sales-adjacent support questions.
7. Common pitfalls and how to avoid them
- Pitfall: vague feature list. Avoid with concrete feature phrasing and differentiators.
- Pitfall: stale pricing summary. Avoid by assigning owner and release checklist updates.
- Pitfall: mixing detailed policy here. Avoid by linking to supporting knowledge assets instead.
8. Success metrics to track
- Reduction in misframed product responses.
- Improved answer consistency across similar product questions.
- Lower recurrence of positioning-related knowledge gaps.
9. Related capabilities
- Assistant Contexts for additional factual grounding entries.
- Knowledge Pages for detailed long-form content.
- Custom Answers for exact wording needs.
- Knowledge Gaps for detecting where profile context is insufficient.
Which option should you use?
Use this matrix to choose the right knowledge option for each support intent.
| Intent | Best option | Why | Link |
|---|---|---|---|
| Exact policy wording | Custom Answers | Deterministic response for high-risk phrasing. | /custom-answers |
| Short operational facts | Snippets | Fast to publish and update. | /snippets |
| Multi-step guides | Knowledge Pages | Better for long-form structure and context. | /knowledge-pages |
| Synced external docs | Knowledge Sources | Best for URL crawl and document ingestion workflows. | /knowledge-sources |
| Baseline product framing | Product Profile | Keeps answers aligned with core positioning. | /product-profile |
| Operational constraints and fallback rules | Assistant Contexts | Adds scoped behavioral context without rewriting docs. | /assistant-contexts |
FAQ
10. Product profile FAQs
Does Product Profile replace knowledge pages and snippets?
No. It provides baseline business context, while pages and snippets provide detailed support content. Learn more
How often should Product Profile be updated?
Update it whenever positioning, pricing summary, audience focus, or key features materially change. Learn more
Who should own Product Profile quality?
Typically product marketing or support enablement teams maintain these fields with periodic review from support leadership. Learn more
Launch a conversation layer your whole GTM team can use.
Unify grounded AI, web and WhatsApp coverage, human handoff, and conversation analytics without stitching together separate tools.