Give your Unwrap Assistant a persistent understanding of your product, team, and data — so every conversation starts smarter.

Overview

Context is a freeform text field that view admins can configure to give the Unwrap Assistant a persistent foundation of knowledge about your product and team. Whenever a user starts a new Assistant conversation — whether that's asking a question, building a group, or generating a board — the Assistant reads the context first and uses it to inform everything it produces.

Without context, the Assistant works from your feedback data alone. With context, it understands the vocabulary, priorities, and nuances that make your team's analysis meaningful.

While only Admins can edit context, all users in your organization can view the context for their view. Changes apply to the entire view, so all users in that view will be affected.

Notes:

• Context currently only informs the Assistant. It does not affect any other Unwrap features such as the Taxonomy, Feedback Page, Dashboards, or Alerts.

• Context applies per-view only. Today, there is no organization-wide context that applies across all views.

How it works

Context is stored at the View level, meaning each view in your Unwrap organization can have its own distinct context. When a user opens a new Assistant conversation, the Assistant automatically reads the context before responding — no extra steps required.

Updates to context take effect immediately for any new conversations started after saving, but do not affect conversations that are already in progress or were started before the update.

Getting started

Editing Context (Admins Only)

• Navigate to any Assistant page in your view.

• Click the Context chip below the Assistant search bar.

• Edit the context field with the information you want the Assistant to use. See Best Practices below for guidance on what to include.

  • Note: There is a 25,000 character limit.

• Click Save. The updated context will apply to all new conversations in this view going forward.

Viewing Context

• Navigate to any Assistant page in your view (General Assistant, Group Build, or Boards).

• Locate the Context chip below the Assistant search bar. It is labeled "Context."

• Click the chip to open and read the current context for your view.

Where context is applied

Once saved, context informs the following Assistant applications:

• General Assistant — Uses your vocabulary, definitions, and reporting preferences when answering questions and naming things.

• Group Build — Follows your guidance to determine which themes are related and what belongs in a group.

• Boards — Tunes chart titles, axis labels, and content to match your view's preferences.

Best Practices

• Ground the Assistant in your product's language. Include the names of your product features, how customers refer to them, and any shorthand or internal terminology your team uses. This prevents the Assistant from misidentifying or mislabeling concepts.

• Describe your data sources and custom fields. Let the Assistant know what feedback sources are ingested into this view and what your custom fields represent. For example: "The 'Tier' field refers to customer subscription level: Free, Pro, or Enterprise."

• Clarify distinctions between similar concepts. If two features or terms are commonly confused — by customers or by the Assistant — spell out the difference explicitly. For example: "'Reports' and 'Dashboards' are different products. Reports are exported PDFs; Dashboards are live in-app views."

• Correct past Assistant mistakes directly. If the Assistant has misclassified feedback, used the wrong terminology, or produced unhelpful groupings, add a note in the context describing the correct behavior. This is the most targeted way to improve Assistant quality over time.

• Keep it focused and scannable. The context is not a product wiki — it's a briefing note. Prioritize the information most likely to affect how the Assistant interprets and responds to your feedback data.

FAQs

Q: I updated the context, but the Assistant still seems to be ignoring it. Why?

A: Context only applies to conversations started after the update was saved. If you're in an ongoing conversation, start a new one and the updated context will be in effect.

Q: Can I have different context for different teams in my organization?

A: Yes — context is set at the view level. If your organization uses separate views for different teams or product lines, each view can have its own tailored context.

Q: Who can see what's in our context?

A: All users in the view can read the context by clicking the Context chip. Only admins can edit it.

Q: Is there a way to disable context for a specific conversation?

A: Not currently. The Assistant reads the context at the start of every new conversation in the view. If you need to test behavior without context, you can temporarily clear the context field and save, then restore it afterward.

Q: What's the best way to improve Assistant quality over time?

A: Use context as a living document. When you notice the Assistant making a consistent mistake — wrong terminology, poor groupings, misattributed feedback — add a correction directly to the context. Over time, this creates a highly tuned Assistant that reflects how your team actually thinks about your product.