STRAX Reach · Team and community chat
Rocket.Chat direct messages to your bot
Partners send a direct message to your bot on Rocket.Chat and your team answers from Reach, with the history kept on their record.
- Direct messages
- Webhook token check
- link command
Direct messages on a server you control
An outgoing webhook on your Rocket.Chat server sends every direct message addressed to the bot to Reach. Reach checks the integration token and confirms the room is a direct conversation with the sender before it files anything.
Replies are posted by the bot user through the REST API with its personal access token. Partners connect their account by sending the word link followed by their code.
Rocket.Chat is popular with agent networks that want chat on their own servers. Reach gives your team one place to answer those agents, while the conversations still happen in the tool the agents chose.
Field agents frequently work across regions with patchy connectivity. Short direct exchanges suit them, and your head-office team keeps a searchable trail of stock requests, commission questions and incident reports per agent.
Where it helps
Agent networks
Airtime and voucher agents on a partner's Rocket.Chat ask about commissions and stock.
Operations desk
Partner operators report failed transactions and receive references back from your team.
Private deployments
Keep partner chat on self-hosted servers while the history lands in Reach.
Stock alerts for agents
Warn voucher agents that a denomination is running low, and let them ask for a restock or report damaged scratch cards in the same direct conversation.
What you need
-
A Rocket.Chat server
Able to reach the install's public address.
-
A bot user
With a personal access token and its user id.
-
An outgoing webhook
On the message-sent event for all direct messages, posting as the bot.
-
Reach Core
The records and console the bot files into.
Good to know
Needs a STRAX build with the body-token signature scheme from 24 September 2026. Edited messages are ignored so a client's record never changes after the fact.
Questions
Which rooms does it read?
Direct messages with the bot only. Reach checks the room before it stores a message.
How do replies reach the partner?
The bot posts them in the same direct conversation.
What is still missing?
Attachments and message edits.
Can one bot serve several partner servers?
Each package connects one Rocket.Chat server. Install the channel once per partner server when you work with several.
What do agents see when a message fails?
The message is marked failed on the partner's record with the reason the server returned, so the agent can retry or switch channel.
Read more
-
The whole Reach family →
Reach Core and every channel package, with what each one needs.
Add Rocket.Chat 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.0.0 |
| Author | STRAX |
| Category | Communication |
| Published | 2026-09-24 |
What's inside
| Credential | 2 |
| Global variable | 2 |
| Workflow | 2 |
What happens on install
After the import, and only with your consent, the installer runs:
- Reach - Register Channel : Registers the Rocket.Chat 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 - Rocket.Chat"
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.
Rocket.Chat 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.