Is DiscordGenius right for you?
Subscribe now or
Production-ready live support workflow, deployable to a Discord server and any website
Moderate Request

Website-to-Discord Live Chat Bot
Built Through 4 Requests

A website chat widget that opens private Discord channels, lets staff reply from Discord, captures offline leads, restores conversations, exports history, and supports Free and Premium plan limits.

5 Slash commands
4 Request rounds
Bot + Widget + Dashboard Deliverables
Live Demo Available now

Request 1: Turn website messages into Discord channels

The first request was intentionally simple: add a chat bubble to the website, create a private Discord channel for every visitor, and let the team reply from Discord instead of a separate helpdesk inbox.

Client request

Initial ask We need a small chat bubble for our website. When a visitor sends a message, it should create a private channel in our Discord server so our team can reply from Discord. We do not want a separate helpdesk inbox. Ideally setup is just adding the bot, running one command, and pasting one script tag on the site.
Builder fulfilment Delivered the first working version: invite the bot, run /setup category:#Website Chats, paste one script tag, and every visitor chat opens a private chat-XXXXX Discord channel. Staff replies in Discord stream back to the website widget in real time.

/setup

Creates the live chat tenant, connects it to a Discord category, and returns the install snippet.

One script tag

The website only needs a small widget script. No custom backend or separate support inbox is required.

Private chat channels

Every visitor gets a five-character chat ID and a matching private Discord channel.

Website widget creates a chat ID
DiscordGenius website with the live chat widget open and a generated chat ID visible
Discord channel created for the visitor
Discord channel created by the live chat bot for a website visitor session

Request 2: Lock it to our domains and match our brand

Once the basic relay worked, the client wanted production safeguards: only approved domains should load the widget, and staff should be able to change the widget color and welcome message from Discord.

Delivered commands

/origins domain:<domain> Adds an allowed origin so copied script tags cannot be reused on unrelated websites. Wildcard subdomains are supported for production, staging, and docs sites.
/customize color:<hex> welcome_message:<text> Lets Discord admins adjust the widget primary color and welcome copy without waiting for a code change.

Domain whitelist

The server validates the page origin before accepting a widget connection for that tenant.

Tenant branding

Color and welcome copy are stored per server, then fetched by the widget when it loads.

Dashboard visibility

The dashboard exposes allowed origins and install state so admins can check production readiness.

Request 3: Capture leads when the team is offline

The third request was a UX decision: do not block the first message with a required email field, but still give visitors a way to get notified if staff reply later.

Optional email prompt after chat starts
DiscordGenius live chat widget showing an optional email notification prompt after a chat has started

Notify Me prompt

The email prompt appears after the visitor starts a chat, keeping the first interaction frictionless.

Offline reply routing

If staff respond after the visitor leaves, the reply can be emailed to the visitor automatically.

Premium reply-to flow

Premium email replies can route back into the original Discord channel, preserving one conversation thread.

Request 4: Restore chats, export history, and add plans

The final launch-readiness request added restore codes, history export, Discord export commands, Stripe billing flows, and clear Free/Premium plan limits.

Restore path visible before a new chat starts
DiscordGenius live chat widget showing the option to restore a previous chat

Operations features

/download-history Exports Premium chat history so support teams can audit conversations and review quality.
/closechat Lets staff close a finished visitor conversation from Discord once the support issue is resolved.
Free plan Supports 5 concurrent live chats, real-time Discord relay, customization, and domain whitelisting, with Premium upgrade paths clearly called out.
Premium plan Raises the limit to 200 concurrent live chats and unlocks full chat history export for growing teams.

The public product page now lives at livechat.discordgenius.com, with Free and Premium plans plus a live demo path.

A real UX question came through live chat

The client used the card chat to ask whether email should be required before the first message or offered after the conversation starts.

Chat decision

Client question Quick UX question: should we ask for the visitor's email before they send the first message, or only after they start the chat? I am worried a required email field will reduce chat starts, but I also do not want us to lose leads when nobody is online.
Builder answer I would avoid gating the first message. Let people ask the question first, then show an optional Notify me email prompt once the chat is active or when the team may reply later.
Accepted UX decision Do not require email before the first message. Show optional Notify Me email capture after the chat starts. Keep the restore code visible so visitors can return without creating an account.

When chat was not enough, they requested a call

For the final email-capture nuance, the client requested a short call to decide whether pricing-page visitors should see different copy than lower-intent visitors.

15-minute call request

The agenda asked whether email capture should change based on the page the visitor is on.

Decision recorded

Keep email optional everywhere for v1. Add page-aware copy later only if traffic proves the complexity is worth it.

Back into the thread

The call outcome becomes part of the same request record instead of disappearing into meeting notes.

What the final system includes

Website chat widget

Embeds on any approved website and starts visitor conversations without a separate helpdesk backend.

Real-time staff replies

Staff can answer from Discord and visitors see those replies in the website widget.

Private Discord channels

Each chat maps to a private channel so staff can reply using the Discord workflow they already use.

One-line install snippet

Admins can paste one script tag into an approved site to launch the widget.

Domain locking

Tenant origins protect the install snippet from being copied onto unapproved sites.

Widget customization

Discord commands update the widget color and welcome message for each server.

Offline email fallback

Visitors can opt into email notifications after a chat starts, and staff replies can reach them later.

Restore codes

Five-character chat IDs let visitors return to a conversation without creating an account.

Plans and billing

Free and Premium tiers support a self-serve launch path with Stripe checkout and billing management.

Premium history export

Premium teams can export chat history for audits, support review, and handoff.

Admin-only setup controls

Setup, allowed origins, customization, and history exports stay behind Discord admin permissions.

Key takeaway: one request became a full support product

  • The client did not need to predict every requirement upfront. They started with a simple chat relay, then added safety, branding, email capture, restore, exports, and pricing as the product matured.
  • Discord stayed the team inbox. Staff reply from Discord while visitors stay on the website, keeping both sides in their natural workflow.
  • Each iteration fit the same subscription model. Product decisions, UX questions, call requests, and implementation all stayed on the same DiscordGenius board.
  • The final product is live. Visitors can test the public live chat product today at livechat.discordgenius.com.

Need a Discord-native support workflow?

This walkthrough is not just a mockup. The finished live chat system is running as a live product. Open the demo, add the bot to a Discord server, and test the website-to-Discord flow yourself.