Hosted Service Documentation
Welcome to the Renbo Inbox Hosted Service manual. This guide covers how to deploy the customer support widget using our global CDN script, customize its parameters, and configure your target channels.
1. Widget Integration Guide
Forcing users to npm install your chat UI instantly alienates anyone running WordPress, Webflow, Shopify, or plain HTML. A <script> tag is the only correct choice for a universal widget.
Renbo Inbox compiles down to a single, lightweight vanilla JavaScript bundle with no virtual DOM bloat, meaning it loads instantly anywhere.
Drop-in Setup (WordPress, Webflow, HTML)
To deploy the live customer inbox widget on your website, copy and paste this code block directly before the closing </body> tag:
<!-- Register the Renbo Inbox Client Widget -->
<script src="https://cdn.renbo.io/widget.js" defer></script>
<!-- Render the inbox element linked to your target space -->
<renbo-inbox project-id="prj_12345"></renbo-inbox>Custom Attributes
You can customize the widget dynamically by appending HTML parameters directly onto the <renbo-inbox> custom element:
| Attribute | Type | Default | Description |
|---|---|---|---|
project-id | String | required | Your unique Conduit workspace client identifier. |
theme | cyan | emerald | purple | white | cyan | The glow accent theme for the chat interface. |
position | left | right | right | Screen layout anchor position. |
title | String | Support | Bold header text displayed inside the chat bubble. |
hide-badge | Boolean | false | Remove the “Powered by Renbo” attribution (Premium only). |
2. Workspace Channels Setup
To keep our infrastructure lightweight, Renbo Inbox leans heavily on native platform authentication models. The setup flow for each channel is designed to be completely friction-free.
| Channel | Connection Mechanism | Setup Complexity |
|---|---|---|
| Telegram | Add bot to group ➔ type /connect [Token] | 2 minutes |
| Slack | Single OAuth click ➔ select target channel | 1 minute |
| Discord | OAuth Invite link ➔ select target server/forum | 1 minute |
| Scan QR code via Conduit dashboard link | 3 minutes |
📢 Telegram Group Routing
Because support chats should map to distinct, threaded message sessions inside your target group:
- The dashboard generates a unique connection token (e.g.,
/connect rb_sk_9482). - The developer adds the official Renbo Inbox Bot to their Telegram group or channel.
- The developer types the connection token command into the group chat.
- Our bot captures the webhook event, matches the token to your project ID, and automatically registers your Telegram
chat_idin our Cloudflare KV store.
💬 Slack Threaded Inbox
Connecting Slack requires zero API configuration:
- Click the Add to Slack button inside your Integrations tab.
- This triggers standard Slack OAuth, installing the lightweight Renbo Inbox App to your workspace.
- Select which channel (e.g.,
#support-inbox) the app has permission to write to. All inbound payloads are threaded under parent notifications to keep discussions clean.
👾 Discord Forums
Discord routes payloads to support forum threads:
- Click the Connect Discord button to trigger a Bot Invite Link.
- Grant permissions to add the bot to your Discord server.
- Select a designated support forum channel; the bot will dynamically spawn temporary threads for each incoming customer session.
3. WhatsApp Session Architecture
A critical design challenge is managing WhatsApp sessions without crushing server memory. Running hundreds of individual headless Chromium browsers via whatsapp-web.js requires gigabytes of RAM and massive hardware costs.
To deliver a hosted service that is both affordable and high-performance, we implement a dual-tier session routing topology.
1. The Shared Global Number (Free & Cheap Tiers)
All developers on our free or basic tiers route customer communications through a single shared master WhatsApp phone number owned by Renbo Studios (e.g., +234 800-RENBO-INBOX).
- How it works: Because everyone shares one WhatsApp number, your system tags the customer context using an initial routing menu or keyword check (e.g., “Hi, I need support for [Startup Name]”). Once matching is established, all subsequent messages route straight to the developer’s Slack thread.
- Benefit: Maintaining a single stable, long-running WhatsApp session keeps our server overhead extremely low, passing the savings down to you.
2. Bring Your Own Session (Premium Tier)
When a startup scales and wants to use their own official brand number, they connect their dedicated session:
- How it works: They scan a QR code via our Conduit dashboard, spinning up an isolated instance of the WhatsApp protocol worker.
- Benefit: Standard, direct customer messages to your official business phone number without any shared routing menus or keyword checks. This maps perfectly to the Premium Tier ($7/mo) to cover the raw hardware cost of running the isolated browser instance.