customer-feedback-ingest

name	customer-feedback-ingest
description	Use when adding a new customer or updating an existing customer in the customer interest tracker from a meeting transcription, email thread, Jira ticket, pasted notes, or any source containing customer requirements/interests. Also use when the user says "add this customer", "update the tracker", "ingest this feedback", or shares a new transcription file.

Customer Feedback Ingest

Extracts customer interests from a source and adds/updates the customer in the restricted tracker.

Tracker Location

rhoai-restricted/customer-feedback/customer-interest-tracker.html

This file is gitignored (NDA content). All source transcriptions live in rhoai-restricted/customer-feedback/transcriptions/.

Source Types

1. Transcription file — read from rhoai-restricted/customer-feedback/transcriptions/
2. Email thread — fetch via Google Workspace MCP (search_gmail_messages + get_gmail_thread_content)
3. Pasted text — user pastes content directly
4. Jira ticket — fetch via REST API per CLAUDE.md

Extraction Checklist

From each source, extract:

• Customer name and parent company (e.g., "Brightly (Siemens)")
• Contacts — names, titles, roles (CTO, architect, PM, etc.)
• Status — one of: ENGAGED, EVAL, PoC, PROD
• Interest areas — map to tracker column headers (see Column Map below)
• Interest level per area — star (critical/blocking), filled (primary), open (secondary/mentioned), dash (not discussed)
• Key requirements — bullet list with bold lead and context
• Action items — what, who owns it, status
• Meeting dates — with duration and format (in-person, virtual, email)

Column Map (Interest Matrix)

These are the exact columns in the tracker. Map extracted interests to these:

Column	What counts
MCP Gateway	Gateway deployment, virtual MCPs, envoy, RHCL
MCP Catalog	Catalog UI, discovery, pre-loaded MCPs
MCP Registry	MLflow registry, versioning, governance, spec compliance
Lifecycle Operator	MCPLO, deploy/upgrade/monitor MCP servers
Zero Trust / OAuth	OAuth 2.0, PKCE, Keycloak, IDP federation, Okta
Token Exchange	JWT exchange, short-lived tokens, per-hop tokens
Audit Trail / OBO	On-behalf-of, audit logging, agent identity chain
Dynamic Client Reg	Self-registration, dynamic client reg with human-in-loop
Virtual MCPs / Tool Agg	Virtual MCP servers, tool aggregation behind one endpoint
Tool Filtering	Subset tools per role/use-case, RBAC on tools
Progressive Disclosure	Tool search, contextual tool surfacing
Registry Spec Compliance	MCP Registry Spec, IDE marketplace integration
Inference Gateway	Model serving, MAS, external models, VLLM/LLMD
AI Grid / Edge	Edge inference, location-aware routing, NVIDIA AI Grid
Token Metering	Chargeback, showback, per-user/per-model token tracking
Rate Limiting	Quotas, rate limits, subscription tiers
Agent Ops	Tracing, evaluation, observability, drift detection
Skills / Agent Registry	Skills registry, agent registry, agent catalog
Sandboxing	OpenShell, sandbox containers, agentic safety
Ingestion Pipeline	Supply chain scanning, signing, certification, partner onboarding

Extended Interest Areas (second matrix)

Column	What counts
Agent Memory	Context management, enterprise brain, memory-over-MCP
Guardrails	Safety guardrails, red teaming, content filtering
Cost Controls / Chargeback	Per-engineer spend visibility, billing, chargeback mechanisms
Per-User Quota Mgmt	Individual API keys, per-user token quotas
Model Routing (cost-aware)	Route to cheaper/local models transparently
Context Analysis	Custom context analysis frameworks, prompt analysis
Co-Engineering	Joint PoC, co-engineering proposals

HTML Symbols

★  = star    — critical / blocking requirement
●  = filled  — primary interest / active requirement
○  = open    — mentioned / secondary interest
—  = dash    — not discussed

Status Tags

<span class="tag tag-poc">PoC</span>
<span class="tag tag-production">PROD</span>
<span class="tag tag-eval">EVAL</span>
<span class="tag tag-engaged">ENGAGED</span>

Process

1. Read the source — transcription, email, or pasted text
2. Read the current tracker — check if customer already exists
3. Extract interests using the checklist above
4. If new customer:
   • Add row to Interest Matrix <tbody> (match column order exactly)
   • Add row to Extended Interest Areas <tbody>
   • Add detail row to Customer Detail table
   • Update summary cards (Active Customers count, Meetings Tracked count)
   • Add to Cross-Customer Themes rows where applicable
   • Add action items to the Action Items table
5. If existing customer:
   • Update interest symbols (only upgrade: dash→open→filled→star, never downgrade)
   • Append new requirements to their detail bullet list
   • Add new action items
   • Update status tag if escalated (EVAL→PoC→PROD)
   • Update meeting list with new meeting
6. Confirm changes with the user before finalizing