AloPedia — RunBear Case Study

1
minutes
March 30, 2026

About Aloware

Aloware is an AI-powered contact center platform built for sales and support teams. It integrates natively with CRMs like HubSpot and Salesforce, combining calling, SMS, AI voice agents, power dialer, and automation into a single platform — so reps spend more time selling and less time on admin. Aloware serves over 1,000 small to mid-market B2B teams across SaaS, real estate, insurance, financial services, and more, starting at $30 per agent per month with unlimited calling and texting included.

One @mention in Slack. Instant answers from every system the company runs on.

Why We Did This

As Aloware scaled across 8 enterprise systems — Confluence, Jira, HubSpot, Chargebee, Zoom, Google Calendar, and more — employees were spending hours every week just finding information. The answer always existed somewhere. It was just never in one place.

New hires took weeks to learn where things lived. Teams were pinging colleagues on Slack about things that were already documented. Every cross-tool lookup meant opening 3–4 apps and losing the flow of work.

Leadership defined the goal clearly: give every employee one place to ask any question and get an accurate answer — without leaving Slack.

What We Did

We built AloPedia — an AI Slack bot connected to the company's entire knowledge base. Employees @mention her in any channel, ask in plain English, and get an answer in seconds.

AloPedia connects to:

Data Type Systems
Static Knowledge Confluence, Marketing Artifacts, Product Docs
Live Records Jira, HubSpot, Zoom Transcripts, Google Calendar, Chargebee, Aloware
Coming Soon Intercom

Deployed across 5 Slack channels (#Spice, #Marketing, #CX, #Tech-support, #Product) and available via DM for private or sensitive queries.

Real examples in action:

Question What AloPedia Returns
"What's the status of the Acme Corp deal?" Live CRM record — stage, owner, amount, last activity
"What is our refund policy for annual plans?" Exact policy pulled from Confluence
"Show me open tickets for the mobile app bug" Live Jira list with status, priority, assignee
"What did we cover in Tuesday's leadership sync?" AI-generated Zoom transcript summary
"Generate a billing report for this account" Structured report combining CRM + billing data

Results:

Metric Result
Systems Connected 8+
Teams Deployed 5+ (Sales, CX, Support, Marketing, Product)
Information Retrieval 1 Slack message vs. 3–4 app switches
New Hire Ramp Time Significant reduction from day one
  • Sensitive data stays protected — each user only sees what they're already authorized to acces.

How We Did It

AloPedia runs on RunBear's multi-system Slack framework with three layers:

  1. Interface — Slack. All interactions happen via @mention
  2. Routing — RunBear's agent determines which system(s) to query based on the question
  3. Data — Connected systems respond via RunBear's native connectors

Key design decisions:

Permission-aware by design. AloPedia uses each user's own credentials — not a shared service account. A rep sees their own pipeline. A director sees the whole team's. The bot never elevates or reduces what someone can access. First-time setup takes 30 seconds via a one-time OAuth authorization in Slack.

Everything stays in Slack. No new app, no new login, no workflow change. Employees interact with AloPedia exactly like messaging a colleague.

Confluence as the source of truth. AloPedia reads from Confluence and surfaces it instantly — keeping documentation authoritative while making it accessible in seconds.

No custom code required. The entire deployment — 8 system connections, 5 channel deployments, company-wide rollout — was completed in weeks using RunBear's native connectors and configuration panel.

"We wanted every employee to have access to a teammate that knows everything about how our company works. AloPedia does exactly that — it lives where we work and makes everyone faster."

— Aloware Leadership Team