ArcGlass vs. Enterpret

Last updated: May 16, 2026

Company data compiled from public sources; figures are approximate and may have changed since publication.

Strategic positioning

	ArcGlass	Enterpret
Buyer	Leadership, Product, Sales (cross-functional)	Product (primary), CX, Research
Headline value	“Signals from every conversation, routed to every team, nothing falling through the cracks.”	“The voice of the customer, with a precise taxonomy.”
Center of gravity	Cross-channel signals → team-routed actions → follow-up enforcement	Feedback aggregation → theme taxonomy → reporting and rollups
Operating mode	Read & write — closed-loop automation	Read-mostly — insights and dashboards
Pipeline model	Independent pipelines per customer / source / use case	Centralized feedback corpus with one taxonomy per workspace

Both products extract signals from customer conversations. Enterpret optimizes for the precision of the insight; ArcGlass optimizes for what happens after the insight fires.

Overlap surface

1. Source ingestion Comparable, different angles

Both products ingest from many surfaces. The mix differs.

• Enterpret edge: survey tools (Typeform, Delighted, Qualtrics), app-store reviews (Google Play, App Store), G2 / Capterra / TrustRadius review sites, Dovetail and other research tools, native CRM (Salesforce, HubSpot), product analytics (Amplitude, Mixpanel). Built for the “voice of customer” aggregation problem — if a review or survey response exists somewhere, Enterpret is built to pull it.
• ArcGlass edge: live customer-conversation surfaces with full thread reconstruction — Slack, Discord, GitHub Discussions, Reddit, X/Twitter, Discourse, Microsoft Teams, Gmail / Outlook email threads, meeting transcripts via Fireflies. Each ingested as an independent pipeline with its own analysis and routing rules.

Different surface choices reflect different jobs to be done: Enterpret is built to be a complete “feedback warehouse,” ArcGlass is built to be a live signal layer over active conversations.

2. Theme taxonomy Enterpret wins

This is Enterpret's signature capability and the biggest gap to call out honestly.

• Enterpret: generates and maintains a hierarchical theme taxonomy specific to your product, evolving as feedback shifts. Themes are deduplicated across surfaces, mapped to product areas, and counted with volume + sentiment over time. Strongest in market on this dimension at enterprise scale.
• ArcGlass: classifies primary and secondary topics per conversation and clusters issues via embeddings into bug-cluster candidates, but does not maintain a long-lived hierarchical taxonomy with the same maturity. ArcGlass topic-detection is per-conversation; Enterpret taxonomy is per-product.

If your problem is “I need a clean, evolving map of what every customer cohort is asking for, by product area, over rolling windows,” Enterpret is the right tool. ArcGlass does not aim to be a taxonomy engine.

3. Signal extraction depth ArcGlass wins

Per-conversation, ArcGlass extracts a wider signal stack.

• ArcGlass: sentiment, emotion (27-way via a fine-tuned model), intent, primary & secondary topic, content-safety risk, resolution status, response times, action items, engagement metrics, ghost / stale detection. Plus deep-insight pattern analysis with confidence and severity scores.
• Enterpret: sentiment, theme, and theme-volume trend per feedback unit. Less per-conversation signal density — the design assumes conversations get aggregated into themes, not analyzed individually for action.

4. Champion detection ArcGlass wins

Enterpret does not surface champions. ArcGlass does, on both sides.

• ArcGlass: composite-scored champion detection with explicit weights (volume 40%, speed 30%, effectiveness 20%, breadth 10%) for both company champions (your staff) and customer champions (their advocates on the customer side). Identifies who's actually driving engagement on each side.
• Enterpret: none. Person-level rollups exist for filtering feedback by author, but not champion identification with explicit scoring.

5. Early-warning risk ArcGlass wins

Both products surface emerging issues, on different timescales.

• Enterpret: theme-volume spike detection — if complaints about onboarding triple this week, the theme bubbles up. Population-level. Slow signal.
• ArcGlass: relationship-level early warning that fires per customer per conversation — negative sentiment spikes, escalation triggers, stale unresponded threads (Ghost Detector), bug-cluster candidates, response-time degradation. Fires at the moment a customer is at risk, not after the population-level trend stabilizes.

6. Actions & automation ArcGlass wins decisively

The biggest functional gap.

• ArcGlass: 30+ integration verbs across six team functions — sales (CRM create/update, log activity), product (issue create, feature request capture), engineering (Jira, Linear, GitHub Issues, Azure DevOps, GitLab), marketing (HubSpot, audience tags), support (Zendesk, ServiceNow, PagerDuty), docs / comms (Slack, Teams, Discord, Google Chat). Plus AI agents that fire actions automatically based on rules.
• Enterpret: integration outputs are mostly read-side — push themes/feedback into Slack, Jira, Linear, Notion. No closed-loop automation, no AI-agent action surface, no cross-team verb library.

7. AI tuning & override loop ArcGlass wins

• ArcGlass: free-text rules (“if a customer mentions pricing twice in a week, route to AE”), per-conversation overrides, override-pattern mining for suggested rules, full provenance per field (whether a value came from base AI, a policy, a rule, or a human override), rule execution audit trail.
• Enterpret: taxonomy curation and theme merging are user-tunable. No free-text rule engine that fires actions. No per-conversation override loop with provenance.

8. AI agents ArcGlass wins on breadth

• ArcGlass: eight functional agents — Escalation, Question Router, Policy, Smart Action, Ghost Detector, Email Orchestrator, Meeting, Inbound. Each operates on signals and fires cross-team actions.
• Enterpret: Compass, a Q&A agent for asking questions about your feedback corpus. Strong inside its narrow scope; not an operational agent layer.

9. Follow-up enforcement ArcGlass wins

ArcGlass's Ghost Detector watches for unresponded threads and stale conversations across surfaces, then nudges. Enterpret has no equivalent — once feedback is ingested and themed, the user is on their own to act on it.

10. Pipeline architecture ArcGlass wins

• Enterpret: one feedback corpus per workspace, with one evolving taxonomy across all of it. Strong for unified rollups; less flexible for “run a dedicated pipeline for this customer / this channel / this use case independently.”
• ArcGlass: independent pipelines per customer, per source, or per use case. Different teams can stand up their own pipelines with their own rules, sources, and routing, without polluting a shared taxonomy.

11. Leadership view Different lenses

• Enterpret gives leadership a product-feedback lens — top themes by volume, sentiment trends, theme co-occurrence, cohort breakdowns. Excellent if leadership's question is “what does the customer base want?”
• ArcGlass gives leadership a customer-relationship lens — status across customers, projects within each customer, follow-ups outstanding, engagement health, where signals are firing right now. Excellent if leadership's question is “which customer is about to slip and what's already in motion to fix it?”

Coverage areas only one side has

Takeaways

1. The products solve adjacent problems. Enterpret answers “what are customers saying?” ArcGlass answers “what's happening with each customer right now, and what needs to be done by whom?” A product team that wants a clean voice-of-customer map will reach for Enterpret first; a leadership team that wants live cross-customer status with team-routed action will reach for ArcGlass.
2. ArcGlass's defensible wedges: closed-loop action automation across six team functions, two-sided champion detection, the policy engine with provenance, independent pipelines, follow-up enforcement. Enterpret cannot match these without rebuilding around the action loop instead of the taxonomy.
3. Enterpret's defensible wedges: theme taxonomy quality, survey and review-site ingestion breadth, and an enterprise track record on the voice-of-customer aggregation problem. ArcGlass does not aim to be a taxonomy engine and will not catch up here organically.
4. If you're choosing between them: pick Enterpret if your problem is “product needs a clean, evolving map of customer voice across surveys, reviews, and feedback.” Pick ArcGlass if your problem is “signals are landing in every channel and no one's acting on them in time.” A few enterprise teams will run both: Enterpret for the strategic feedback map, ArcGlass for the live operational signal layer.

How ArcGlass thinks about the overlap

We don't position ArcGlass as an Enterpret replacement. Enterpret has built a real product around theme taxonomy that we don't try to compete with directly. We position ArcGlass as the layer that sits between “a signal fired” and “the right team took the right action and confirmed it landed.” That gap is the most frequently cited limitation of read-mostly feedback platforms — the insight is great, but nothing closes the loop. ArcGlass was built around closing the loop from day one.

The natural integration pattern: Enterpret consumes ArcGlass's structured conversation output as one of its feedback sources, while ArcGlass routes the per-customer, per-conversation actions that Enterpret's population-level themes can't trigger on their own.

Questions about this comparison? Reach out at [email protected] — we're happy to dig into specifics for your stack.