Product Description vs. Organizational Memory

Glyphic has two free-text fields that admins use to teach it about your business and how your team communicates. They live next to each other in Settings → Organizational but serve different purposes — and putting the wrong content in either one can degrade the AI's outputs.

Quick comparison

	Product Description	Organizational Memory
Purpose	Tells Glyphic what your company sells	Tells Glyphic how your team communicates
Used by	Annotations, Custom Insights, Ask Glyphic, call prep, deal copilot	Ask Glyphic responses, generated emails, Quick Action outputs, all generated text
Who edits it	Admins only	Admins only
Auto-updates	No — static	No — static
Mental model	Your company knowledge base	Your team's style guide

Keep them separate. Tone instructions in Product Description bleed into Custom Insight extraction; product details in Organizational Memory get applied as style rules to every generated message.

Product Description

What it is

A free-text field where you describe your business: what you sell, who you sell to, how you differentiate. This is core context that Glyphic reads whenever it needs to reason about your product or market.

What to include

• Value proposition — the problem you solve and for whom.
• Products / services — names, key features, capabilities.
• Differentiators — why customers pick you over alternatives.
• Target customers — ICP, industries, common use cases.
• Case studies — concrete proof points to reference.
• Terminology — internal acronyms and naming.
• What you don't do — useful for accurate gap detection ("the customer asked for X, which we don't offer").

For multi-product companies, use one field with a paragraph per product. Glyphic differentiates between them based on context in the call.

Where it's used

• Call summaries and annotations — adds product context.
• Custom Insights — particularly for feature-gap and competitive insights.
• Ask Glyphic — grounds answers in your product and positioning.
• Call prep sheets — surfaces relevant context before meetings.

Things to know

• Static — Glyphic doesn't update it automatically. Refresh when products launch, features change, or positioning shifts.
• Admin-only.
• High blast radius — changes affect Custom Insight extraction, Ask Glyphic answers, and annotations across the platform.

Organizational Memory

What it is

A free-text instruction layer that defines how Glyphic communicates: tone, style, formatting, mandatory inclusions, things to avoid.

What to include

• Tone — e.g. "Direct and concise."
• Language rules — e.g. "Respond in German if the customer speaks German."
• Formatting — e.g. "Use bullet points, not paragraphs."
• Mandatory inclusions — e.g. "Always mention SOC 2 when security comes up."
• Things to avoid — e.g. "Never include pricing unless explicitly asked."
• Terminology — e.g. "Say 'partners', not 'clients'."

Where it's used

• Ask Glyphic — controls response style.
• Generated follow-up emails — applies tone and structure.
• Quick Actions — standardizes outputs.
• All AI-generated text in the platform — acts as a persistent system instruction.

Things to know

• Static — does not auto-update.
• Admin-only.
• Don't put product information here — keep it in Product Description.
• Applies organization-wide. May override Personal Memory in some cases.

Personal Memory (for context)

Personal Memory is the user-level counterpart to Organizational Memory. Each user gets their own.

	Personal Memory	Organizational Memory
Set by	Individual user	Admin only
Auto-updates	Yes	No
Scope	That user only	Whole organization
Examples	"I prefer bullet points"	"All responses must be concise"

Personal Memory builds up over the first few calls a user runs through Glyphic. See Personal Memory — Overview.

Recommended setup order

1. Set Product Description first — ideally before processing any calls. Cover value proposition, products, differentiators, ICP, terminology.
2. Set Organizational Memory — tone, formatting, communication rules. Applies immediately across all outputs.
3. Update Product Description when products launch, features change, or positioning evolves.
4. Let Personal Memory build — users can edit their own at any time under Settings → Personal.

Common mistakes

Mistake	Fix
Leaving Product Description blank	Fill it in before processing the first calls.
Putting tone instructions in Product Description	Move them to Organizational Memory.
Putting product info in Organizational Memory	Move it to Product Description.
Letting users edit org-level fields	Both fields are admin-only by design.
Assuming the fields auto-update	Both are static — schedule periodic reviews.
Writing only a sentence or two	Provide rich, multi-paragraph context — short fields produce shallow outputs.

Summary

• Product Description = what you sell.
• Organizational Memory = how you communicate.
• Keep them separate. Mixing them degrades Custom Insight accuracy and produces inconsistent generated text.