Brixo
Skip to main content
How It Works

Here's how it works

From raw conversation data to insights your team can act on. Two paths to get started, one outcome: you understand what your customers are experiencing.

Two ways to get started

Path A

Upload Your Data

Already have conversation exports? Upload them and Brixo gets to work immediately.

Best for: Teams that want to evaluate Brixo with existing data before instrumenting.

  1. 1.Export your conversations
  2. 2.Upload to Brixo
  3. 3.Brixo ingests, labels, and structures every conversation
  4. 4.See your first insights in minutes
Path B

Instrument Your Experience

For a real-time view into your product. Point the Brixo SDK at your conversation source.

Best for: Teams ready for always-on customer experience analytics. Typical setup: 15-20 minutes.

  1. 1.Install the SDK (npm install @brixo/sdk)
  2. 2.Initialize with your API key
  3. 3.Stream conversations to Brixo in real time
  4. 4.Insights update continuously
Both paths lead to the same place: your agent, working for you

What Brixo shows you

Conversation Analysis

Every conversation structured by topic, intent, sentiment, and outcome. Search semantically across all conversations, ask questions in plain language instead of writing SQL, and filter by what matters.

TC
TechCorp Inc.
John Smith · Dec 8 · 29 min✓ Resolved⚡ Medium Effort
Events
Conversation StartedEscalationHandoffConversation Ended
Sentiment
1/1 Frustrated1/1 Confused
Intent
• Report BugGet InformationRequest Help

Hi, I'm having trouble connecting to your API. I keep getting a 401 error when trying to authenticate. I've double-checked my API key but it still doesn't work.

Neutral• Report Bug

Hello John! I'd be happy to help you with the API authentication issue. Could you confirm which environment you're trying to connect to — production or sandbox?

Thanks for the quick response! I'm trying to connect to production. We've been using the API for months without issues until yesterday.

Grateful

Trends

See patterns over time: which topics are growing, where errors are spiking, how sentiment is shifting, and what customers are asking for most. Spot friction before it becomes churn.

Trend Overview
24h7d30d
6040200MonTueWedThuFriSatSun
Trending Topics
Onboarding Help
85%
Billing Questions
62%
API Errors
48%
Feature Requests
35%

Prioritized Insights

Brixo doesn't hand you a list of every conversation. It surfaces what's worth your attention: friction patterns, emerging issues, experience breakdowns, with the evidence behind each one.

⛓ Conversational Insights

Based on 30 conversationsAnalysis current

Patterns and friction points extracted from analyzing user ↔ assistant conversations.

Executive Summary

The product is powerful, but users are constantly falling into expert-only paths without realizing it. When things break, the system explains instead of guiding — and that's where frustration spikes.

1
SQL & Data Transformation Is the #1 Pain PointCritical

Users hit frequent SQL syntax errors, DB-specific incompatibilities, and JSON parsing failures. Trial-and-error debugging loops dominate conversations.

2
Spreadsheet / "Transformations" Mental Model Is ConfusingCritical

Users don't understand the difference between sheet inputs, platform inputs, and dynamic content inputs. The implicit data flow is opaque.

3
Errors Are Frequent — and Feel HostileHigh

Users see raw database errors, JSON dumps, and template execution failures with no context on what broke, why, or what to do next.

4
Assistant Expectations > Assistant CapabilitiesHigh

Users expect the assistant to "fix it" but get plausible-but-incorrect SQL and multi-turn debugging loops. Trust degrades quickly.

5
Feature Discoverability GapsMedium

Capability boundaries are unclear. Users discover limits only when they hit them, leading to frustration from unclear affordances.

Account Intelligence

Every insight is tied to a real customer or account. See which accounts are struggling, which are healthy, and which need attention this week. No more guessing at account health from usage metrics alone.

AccountsView all
AccountConvosUsersIssues
LH
LumaHealth Clinics
1045
DF
DataFlow Systems
36104
OH
OmniaHR
1454
AF
ApexFin Banking
2263
TC
TechCorp Inc.
4292
GG
GreenGrid Energy
2772
BR
BeaconRetail
1642
QL
QuantumLabs AI
1132
NA
NovaAnalytics
3161
HL
Horizon Logistics
1851
Frequently Asked Questions

Everything you need to know

Can't find what you're looking for? We're happy to help.

What data does Brixo need to get started?

Brixo needs your AI product’s conversation data — the messages exchanged between your customers and your AI agent, copilot, or chatbot. You can upload conversation logs as a CSV, integrate via the Brixo Python SDK, or stream existing telemetry through OpenTelemetry (OTLP). No specific format is required for CSV uploads — Brixo ingests, labels, and structures the data automatically.

Your first insights are minutes away.

Upload your data or connect your SDK and get a complete view of your AI product experience. Free to start, no engineering required.