Discord Livedesk
Route web chat conversations to Discord for human agents to respond in real-time
Discord Livedesk is one of the places a hand-off can go. When a customer asks for a person (or your agent can't help), the conversation appears as a thread in a Discord channel your team watches. When someone replies in that thread, the reply is delivered straight to the customer's chat widget.
You set it up on Actions → Hand off to your team, next to email and Live Desk.
Key Features
- Hand-offs in Discord: A new thread opens with the conversation so far as soon as a customer asks for a person
- Or every conversation: Switch to Every conversation to watch all website chats live
- Conversation context: Summary embeds show customer email, location, device, and referring page
- Replies go back to the customer: Answer in the thread and the customer sees it in their chat
How It Works
- A customer chats with your agent on your website
- They ask for a person, or your agent can't help and hands off
- FutureBase posts a summary embed to your channel and opens a thread with the conversation so far
- Your team replies in the thread, and the customer sees the reply in their chat widget
- Further messages from the customer continue in the same thread
With Every conversation, step 3 happens on the customer's first message instead, and every reply is mirrored as it happens.
Quick Setup
Connect in FutureBase
- Open Actions in your FutureBase dashboard and choose Hand off to your team
- Under Who hears about it, choose Connect next to Discord, then pick your server and authorize the FutureBase bot
- Choose Pick a channel and select the channel where conversation threads should be created
- Choose what to post: Only hand-offs (the default) or Every conversation
Choose a channel dedicated to support conversations. Each conversation creates a new thread, so a channel just for incoming support requests keeps things tidy.
Configuration Options
Include Customer Email
When enabled (default), the conversation summary embed includes the customer's email address if they've provided it. This helps agents quickly identify repeat customers or follow up via email.
Include Customer Info
When enabled (default), the summary embed includes metadata like:
- Country: The customer's country based on IP geolocation
- Device: Mobile, tablet, or desktop
- Platform: Windows, macOS, iOS, Android, etc.
- Page: The URL of the page where the customer started the chat
This context helps agents understand the customer's situation without asking basic questions.
Translate
Off by default. Turn it on and pick your team's language on Actions → Hand off to your team, next to Post. Everything posted to the thread (the customer's messages, your agent's answers, the hand-off transcript) is translated into that language first, and a reply typed in the thread reaches the customer in the language they wrote in. Each message is translated once and stored, and translation runs on your agent's credits.
Best Practices
Channel Organization
- Dedicated channel: Create a channel specifically for livedesk threads (e.g.,
#support-inbox) - Archive old threads: Discord automatically archives inactive threads; you can adjust the archive duration in channel settings
- Pin important threads: Use Discord's pin feature for VIP customers or ongoing issues
Team Workflow
- @mention roles: Set up Discord notifications so your support team is alerted to new threads
- Use reactions: Team members can use reactions to claim or acknowledge conversations
- Thread naming: FutureBase names threads after the conversation; you can rename them for easier tracking
Response Time
Replies in Discord are delivered instantly to customers. However, customers may close their browser tab and miss responses. Consider:
- Using the email notification features for customers who haven't received a human reply
- Setting clear expectations about response times on your website