ArcGlass vs. Unwrap.ai
Company data compiled from public sources; figures are approximate and may have changed since publication.
TL;DR. Unwrap and ArcGlass start in similar territory — both aggregate customer voice across many sources. They diverge fast on what happens next. Unwrap is a product-feedback intelligence platform: themes, sentiment trends, summaries for product and CX teams. ArcGlass is a cross-channel signal-and-routing layer: signals fired per conversation, routed to whichever team should act, with follow-up enforcement. If the question is “what are customers saying,” Unwrap is clean. If the question is “who's owning the next move and did it land,” the products diverge.
Strategic positioning
| ArcGlass | Unwrap.ai | |
|---|---|---|
| Buyer | Leadership, Product, Sales (cross-functional) | Product, CX |
| Headline value | “Signals from every conversation, routed to every team, nothing falling through the cracks.” | “AI-powered customer feedback intelligence.” |
| Center of gravity | Cross-channel signals → team-routed actions → follow-up enforcement | Feedback aggregation → AI-clustered themes → product-feedback reporting |
| Operating mode | Read & write — closed-loop automation | Read-mostly — reports and dashboards with light routing |
| Pipeline model | Independent pipelines per customer / source / use case | Centralized feedback corpus with one taxonomy per workspace |
Same family of product (customer voice). Different jobs to be done. Unwrap is built for the product team that needs a clean theme map. ArcGlass is built for every team that needs to act before a signal goes stale.
Overlap surface
1. Source ingestion Comparable, different angles
Both pull from many surfaces. The mixes differ.
- Unwrap edge: support tools (Zendesk, Intercom, Front), app-store reviews (Google Play, App Store), G2 / Capterra review sites, survey tools (Delighted, Typeform), social mentions, sales call summaries via Gong.
- ArcGlass edge: live conversation surfaces with full thread reconstruction — Slack, Discord, GitHub Discussions, Reddit, X/Twitter, Discourse, Microsoft Teams, Gmail / Outlook email threads, meeting transcripts via Fireflies. Built for active conversations, not just feedback aggregation.
2. Theme clustering Unwrap wins
Unwrap's headline capability.
- Unwrap: AI-driven theme discovery across the feedback corpus, with merging, splitting, deduplication, and volume / sentiment over time per theme. Strong UX for product teams who want a structured taxonomy of customer voice.
- ArcGlass: classifies primary and secondary topics per conversation and clusters issues via embeddings into bug-cluster candidates. Topic detection is per-conversation; long-lived hierarchical taxonomy is not the architectural goal.
3. Per-conversation signal extraction ArcGlass wins
ArcGlass extracts a wider signal stack on every individual conversation.
- ArcGlass: sentiment, emotion (27-way), intent, topic, content-safety risk, resolution status, response times, action items, engagement metrics, ghost / stale detection, deep-insight pattern analysis with confidence and severity.
- Unwrap: sentiment and theme assignment per feedback unit. Less per-conversation signal density — the design assumes conversations roll up into themes, not get analyzed individually for action.
4. Cross-team action routing ArcGlass wins decisively
- ArcGlass: 30+ integration verbs across six team functions — sales, product, engineering, marketing, support, docs / comms. Plus AI agents that fire actions automatically.
- Unwrap: 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.
5. Champion detection ArcGlass wins
Unwrap does not surface champions. ArcGlass identifies both company champions (your top responders) and customer champions (the advocates on the customer side) via composite scoring.
6. Early-warning risk ArcGlass wins
- Unwrap: theme-volume spike detection at the population level — if complaints about onboarding triple this week, the theme rises. Slow signal, after-the-fact.
- ArcGlass: per-customer per-conversation early warning — negative sentiment spikes, escalation triggers, stale unresponded threads, bug-cluster candidates, response-time degradation. Fires when risk emerges, not after population averages stabilize.
7. AI tuning ArcGlass wins
- ArcGlass: free-text rule engine, per-conversation overrides, override-pattern mining, provenance per field, rule execution audit trail.
- Unwrap: taxonomy curation and theme merging are tunable. No free-text rule engine that fires actions. No 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. Operational, cross-team, signal-anchored.
- Unwrap: AI-powered summarization, theme generation, and Q&A over the feedback corpus. Strong inside that scope; not an operational agent layer.
9. Follow-up enforcement ArcGlass wins
Ghost Detector watches for unresponded threads and stale conversations across surfaces. Unwrap has no equivalent — once feedback is themed, the user is on their own to act on it.
10. Pipeline architecture ArcGlass wins
Unwrap has one feedback corpus per workspace. ArcGlass has independent pipelines per customer / source / use case — teams can stand up their own pipelines with their own rules without polluting a shared taxonomy.
Coverage areas only one side has
Only ArcGlass
- Cross-team action routing (sales / product / engg / marketing / support / docs)
- Two-sided champion detection
- Ghost Detector / stale-thread enforcement
- Free-text rule engine with override provenance and suggestion mining
- Eight AI agents operating on signals
- Per-conversation early-warning risk composite
- Independent pipelines per customer / use case
- Live conversation surfaces (Slack, Discord, X, Reddit, Discourse) as first-class pipelines
- Community health metrics
- RAG context layer feeding every LLM call
Only Unwrap
- AI-driven evolving theme taxonomy across the feedback corpus
- App-store review ingestion (Google Play, App Store)
- Public review-site ingestion (G2, Capterra, TrustRadius)
- Survey-tool ingestion (Delighted, Typeform)
- Theme-level volume and sentiment trend rollups
- Q&A over the feedback corpus
- Product-team-tuned reporting UX
Takeaways
- Adjacent problems. Unwrap answers “what are customers saying at the population level?” ArcGlass answers “what's happening with each customer right now, and who needs to act?” A product team starting from zero on voice-of-customer will reach for Unwrap first; an organization with signals scattered across teams and channels will reach for ArcGlass.
- ArcGlass's defensible wedges: closed-loop action routing across six team functions, two-sided champion detection, the policy engine with provenance, follow-up enforcement, independent pipelines.
- Unwrap's defensible wedge: theme clustering quality and product-team reporting UX. ArcGlass is not aiming at this.
- If you're choosing between them: Unwrap for a clean, evolving voice-of-customer map. ArcGlass for live cross-team operational signal routing.
How ArcGlass thinks about the overlap
We don't position ArcGlass as an Unwrap replacement. Unwrap is solving the product-feedback aggregation problem cleanly. ArcGlass solves the signal-to-action gap that read-mostly platforms leave open. They can sit in the same stack: Unwrap on the strategic theme map, ArcGlass on live operational routing across every team's channels.
Questions about this comparison? Reach out at [email protected] — we're happy to dig into specifics for your stack.