Scenario
Team wants structured user profiles for analytics, routing, or other internal logic — not just for LLM prompts.Extraction
They stream conversation logs, events, and reviews to GetProfile:- It extracts traits like:
NPS_risk: likely detractor vs promoterchurn_risk_reasons[]product_feature_needs[]expertise/segment(SMB vs enterprise, hobbyist vs pro)
Injection
- Some teams might still have their own LLM stack; they just call
GET /profiles/:idto build prompts manually. - Others may later switch to GetProfile proxy to get automatic injection with the same traits.
Impact
- They can use traits everywhere:
- marketing segmentation,
- feature flags (“show advanced UI for experts”),
- routing to different flows based on
segmentorrisk.
- And, if/when they want, they get “free” prompt injection by pointing their LLM client to the GetProfile proxy.
Implementation
Trait Schema Example
Use Cases for Extracted Profiles
Marketing Segmentation
Route users to different marketing campaigns based on extracted traits
Feature Flags
Show/hide features based on user expertise or segment
Support Routing
Route support tickets to appropriate teams based on user profile
Analytics
Build dashboards and reports from structured profile data