RagbeeYour knowledge base,
everywhere your team already talks.
Ragbee connects one tenant-isolated knowledge base to the chat platforms your people actually use. Ask in Zoom, get the same grounded, source-cited answer you'd get in the dashboard — no new apps to learn, no data copied into third-party silos.
Channels
Every channel runs through the same verified, signed pipeline: identity-checked webhooks, per-tenant routing, PII redaction on every reply.
Zoom Team Chat
Install once, your whole Zoom account gets the assistant. DMs and channel mentions, conversation memory per channel, automatic account routing for multi-tenant installs.
Telegram
A support bot your team can DM from anywhere. Great for field and shift workers who live on their phones rather than a desktop.
Discord
Community and team servers. Channel-scoped context, so each channel keeps its own conversation thread.
Messenger
Your Facebook Page becomes the assistant — your branding, your name, answers from your documents. Built for small businesses whose customers message the Page.
Slack
Workspace-wide install with threaded replies. Mention the bot in any channel or DM it directly.
Website chat widget
One line of HTML puts your assistant on any website — your branding, your greeting, answers from your documents. Rate-limited and policy-only by design.
Voice & Email
Phone support with identity verification, and email ingestion — because some questions still start outside chat. See the payroll workflow.
How a channel connects
1 · Upload your knowledge
PDFs, policies, handbooks, URLs, cloud folders. That's the bot's entire brain — it only answers from your documents, with citations back to the source.
2 · Click connect
Dashboard → Chatbots → Connect. OAuth does the rest: tokens, routing keys, and verification are captured automatically. No engineering ticket.
3 · Ask anywhere
DM the bot or mention it in a channel. Replies come from your workspace — isolated per tenant, logged for your admins, redacted before they leave.
Trust is the feature
Most chatbots either answer everything or nothing. Ragbee's channel policy is deliberate — and enforced in code, not in a policy PDF.
- Chat channels answer policy and knowledge questions — handbook, benefits, procedures, pricing, anything in your documents.
- Personal data requires a verified channel. Ask "what's my PTO balance" in a bot and it points you to the verified self-service flow or phone line. It will never ask for your SSN in a group chat.
- PII redaction on every reply — sensitive patterns are stripped before a message leaves our infrastructure.
- Per-tenant isolation — your documents, logs, and bot tokens never cross tenants. Signed webhooks on every platform; unauthorized requests are rejected at the door.
- Uninstall is self-cleaning — deauthorize the app and tokens are revoked, conversations purged on schedule.
Make it yours
Your brand, your voice
On Messenger the bot is your Page — your name and photo. On every channel, set the bot's display name, first-message greeting, and tone. Warm and casual, brief and precise — it's your assistant, not ours.
One knowledge base, every surface
Dashboard chat, support workflows, voice line, and every chat channel and the website widget read the same workspace. Update a document once — every channel is current.