Skip to main content

Scenario

SaaS product with an in-app / website support chatbot that needs to remember user context across conversations.

Extraction

From chats, tickets, and events, GetProfile keeps a live profile per end-user:
  • plan_tier: free / pro / enterprise
  • product_areas_used[]: “billing”, “integrations”, “dashboards”
  • recurring_issues[]: “confused about usage limits”, “OAuth failures”
  • frustration_level: low / medium / high
  • tone_preference: patient explanations vs short answers
No one fills this out manually; it’s inferred from conversations + app events.

Injection

When the user talks to the bot again, calls go through the GetProfile proxy:
  • It injects a short profile block into the system prompt:
    • “Pro-tier user, power user of integrations, recently frustrated about rate limits, prefers direct answers.”
  • It also injects a couple of recent, high-signal memories:
    • last failed integration attempt,
    • last time support promised a fix.

Impact

The bot can:
  • Skip basic docs if user is a power user.
  • Preempt “we’ve had this issue before” with context.
  • Use calmer, more careful language if frustration_level is high.

Implementation

Trait Schema Example

Proxy Integration

Learn how to set up the proxy for automatic injection

Trait Schemas

Configure custom traits for your support use case