STRAX Reach · Team and community chat
Discord direct messages and slash commands in Reach
Developers and merchants in your Discord can now simply message the bot. Reach files each direct message in the member's conversation, and your team answers from the console.
- Plain direct messages
- Signed interactions
- Link by code
Two ways in, one conversation per member
Ordinary direct messages reach Discord bots over a permanent Gateway connection. The workflow worker can hold that connection for your bot and hand every DM to Reach, where it lands in the member's conversation with their Discord id as identity. Sending link and the code from your portal ties that id to an account.
Slash commands still work for members who prefer them. Discord signs each interaction with your application's public key, Reach verifies it, acknowledges at once and files the question.
Answers edit the deferred command reply when it is still fresh and otherwise arrive as a direct message from the bot. Server channels are never read, so account questions stay private. Because both routes use the same Discord user id, a member who first tried a slash command and later wrote a plain message keeps one conversation with one history. Moderators therefore never need to copy questions between tools or chase members across servers.
Where it helps
Developer support for your API
Merchants integrating your payment API DM the bot with a question and a support engineer answers with their earlier threads in view.
Beta feedback
Testers of a new wallet release report issues privately without cluttering the public channels.
Account questions away from the crowd
Members who start in a public channel are pointed to the bot, where their account can be discussed safely.
What you need
-
A Discord application with a bot
With the Message Content intent switched on for direct messages.
-
One workflow worker with the Gateway service
Enabled by your administrator; it keeps the bot connected.
-
A public HTTPS address
For the interactions endpoint that carries the slash commands.
-
Reach Core
The records and console the messages file into.
Good to know
Only direct messages and the two slash commands are read; server channel messages, buttons and attachments are not used. The Gateway service runs on one worker and is off until your administrator enables it.
Questions
Why does the bot token appear in two credentials?
The DM service needs a Discord bot credential with Gateway settings, and the existing credential keeps serving the dispatcher, so the same token is entered in both.
Do members still need /ask?
Members can simply write to the bot once the Gateway service is on; /ask remains for servers where DMs are closed.
Can the bot read our public channels?
The service only asks Discord for direct messages, so channel conversations never reach Reach.
What happens if the worker restarts?
The connection resumes automatically, and Reach drops any message it has already filed.
Read more
-
The whole Reach family →
Reach Core and every channel package, with what each one needs.
Add Discord to Reach
Tell us which channels your clients use and we will plan the rollout with your team.
Premium Requires STRAX Reach - Core, which is licensed.
About this listing
| Version | 1.2.0 |
| Author | STRAX |
| Category | Communication |
| Published | 2026-09-24 |
What's inside
| Credential | 3 |
| Data table | 1 |
| Global variable | 1 |
| Workflow | 4 |
What happens on install
After the import, and only with your consent, the installer runs:
- Reach - Register Channel : Registers the Discord channel with Reach Core, disabled until its credentials are entered
Free listing
Install it from Feature Marketplace inside STRAX
It builds on STRAX Reach - Core, a premium package. Ask us for a quote to license it first.
Open Feature Marketplace
In your STRAX installation, open Feature Marketplace from the navigation.
Find "STRAX Reach - Discord"
Search or browse to this listing and review the contents disclosure; every package shows what it contains before anything runs.
Install
Choose Install, or "Customise with AI" to adapt the package to your environment first. No licence is needed for free listings.
Discord is a trademark of its owner, named here only to identify the service this package connects to.
See it on your own systems.
A demo takes an hour, on your data landscape rather than ours.


