Support Relay
Answer website support chats from Discord. Keep every conversation in its own thread, reply naturally, and let visitors see when you are typing—even when you work from your phone.
Managed integration · Website setup required. Contact Diszy to connect your website; inviting the bot alone does not activate your chat.
Request website setup →Last updated: September 5, 2026
Support Relay — data processing information
Support Relay transfers support conversation data between a connected website and its configured Discord server. The website operator selects which conversations and content are sent. Please also read the connected website’s privacy notice and Discord’s privacy policy.
Data used by the integration
The relay processes site and conversation identifiers, timestamps, conversation status, permitted visitor display details, message content according to the configured privacy mode, and Discord server, channel, thread, message, and operator identifiers. Authorized replies are sent back to the website. Typed drafts are not transferred; typing signals contain operator identification and activity timing.
Message visibility
Metadata mode excludes message bodies. Preview mode limits retained/displayed message text to 500 characters. Full mode accepts up to 4,000 characters, subject to Discord display limits. Anyone with access to the configured Discord channel can potentially see mirrored information; a private channel and carefully limited membership are essential.
Storage and deletion
Retained sensitive relay fields and site secrets are encrypted at rest. Delivery queues temporarily retain the payloads needed for retrying. Automated cleanup uses the deployment’s configured retention windows; configuration and routing/audit identifiers may remain beyond sensitive-content expiry. Relay cleanup does not delete messages already posted in Discord or the website’s own conversation records. Archiving a thread is not deletion.
Human support and optional AI
The standard installation relays human replies. Optional AI processing requires separate deployment and site-level activation and is not activated by inviting this bot. Its data handling must be disclosed separately before use.
Contact
For Diszy integration and relay-data questions, contact info@diszy.com. For the original support conversation or a deletion request covering the website and its Discord server, contact the website operator. Provider details are available in the Diszy imprint.
Last updated: September 5, 2026
Support Relay — service and usage information
Support Relay is a managed website-to-Discord integration. Installing the app does not create a website chat, provision a site secret, or activate a service plan. Scope, availability, and any commercial terms are agreed during onboarding. Purchasing general Diszy credits does not activate this integration.
- Keep the support channel private, restrict operator access, and protect site credentials. Only send information appropriate for your support workflow and the configured Discord audience.
- Normal text messages from authorized operators in mapped threads are forwarded to visitors. Prefix internal notes with
//. - A reply is confirmed only when the connected website acknowledges it. Check failed delivery indicators; Discord, the relay, or the website may be unavailable.
- Attachments are not forwarded. Discord message edits and deletions are not synchronized to previously delivered website replies.
- The website remains the original conversation system. Archiving a Discord thread does not delete the conversation or mirrored data.
- Automated AI replies are outside the standard human-relay setup and require separate configuration and review.
Contact info@diszy.com for onboarding, support, or stopping an integration.
Your website inbox. Your Discord workflow.
Support Relay connects an existing website chat to Discord. The website keeps the original conversation; your team answers from Discord without switching to a separate support dashboard.
One conversation, one thread
- A tidy inbox: each website conversation opens a thread inside your private support channel. Messages appear in chronological order.
- Reply normally: open a thread and type a message. Authorized operators do not need a slash command or a reply form.
- Mobile-friendly: the same thread and message composer work in the Discord mobile app.
- Typing activity: compatible website chats can show “Niklas is typing…” while an operator types. Draft text is never sent.
- Clear delivery status: ⏳ means pending, ✅ means the website confirmed delivery, and ❌ means delivery failed.
- Close the loop: use the “Erledigt” button to dismiss a conversation and archive its thread.
Connect your website
This is currently a managed integration, not a drop-in chat widget. Contact info@diszy.com with your website URL and the chat system you use. Diszy coordinates provisioning and an end-to-end test.
- Prepare Discord. Add the bot to your server and create a private support channel accessible only to your operators and the bot. No Administrator permission is requested by the bot.
- Connect the backend. Your developer sends signed conversation events to the relay and implements a signed HTTPS endpoint for replies, dismissals, and typing signals. Keep the shared site secret on the server, never in browser code.
- Configure access. During onboarding, configure the website, channel, operator roles or users, and the amount of message content mirrored into Discord.
- Test before enabling. Verify visitor messages, direct replies, typing expiry, delivery confirmation, and closing/reopening a conversation. Review your visitor notices and channel access before using real customer data.
Operator notes
Start a message with // for an internal note that stays in Discord. Normal messages in mapped threads are sent to the visitor. Messages in the parent inbox or unrelated threads are ignored.
Only text replies are supported. Attachments and stickers are not forwarded. Editing or deleting a Discord message does not edit or delete a reply already delivered to the website. A typing indicator is temporary and depends on the website implementing it.
Administration
Provisioning uses the administrator-only /support-site commands: create, list, test, enable, disable, and rotate. Command availability on additional servers is arranged during onboarding.
The standard workflow relays human replies. Automatic AI replies are not enabled by this installation flow. The Diszy credit checkout does not activate Support Relay; setup and any service terms are agreed during onboarding.