STRAX Reach · Team and community chat
Slack direct messages in Reach
Business clients and partners message your Slack app directly, and your team handles those threads in Reach with everything else.
- Direct messages with the app
- Slack request signatures
- Partner records
A shared channel of work, kept on the record
Slack sends each direct message through the Events API, signed with your app's signing secret. Reach checks the signature and the timestamp, then files the message against the partner who owns that Slack user id.
Replies go out as the bot through the Web API. Because Slack user ids are stable, a partner's whole history follows them even when they change workspaces or channels.
Keeping partner questions in Reach instead of a scattered set of Slack threads means the next person on shift sees what was promised. The partner still writes in Slack; your team works from the console with the partner's full history.
Partnership managers rotate, holidays happen and handovers get lost. With partner threads recorded in Reach, whoever picks up the relationship next reads the complete background before replying, including decisions agreed months earlier.
Where it helps
Merchant onboarding
Walk a new merchant through settlement setup over Slack and keep every answer on their record.
Settlement queries
Partners ask why a settlement is late and the operations team replies with the batch reference.
Incident notices
Tell affected partners about a processing delay and collect their questions in one place.
Compliance document exchange
Ask a merchant partner for updated company documents and track the request until they confirm it has been sent.
What you need
-
A Slack app
With bot scopes for chat, direct message history and reading and opening direct messages, installed in the workspace.
-
The bot token and signing secret
Kept in the STRAX credential vault, together with the workspace team id.
-
A public HTTPS address
Slack verifies the request URL before it sends events.
-
Reach Core
The records and console the app files into.
Good to know
The app answers direct messages. Enable the Messages tab in App Home, or people will not be able to write to it.
Questions
Can it read our public channels?
It listens to direct messages only, which keeps partner conversations private and your channels out of Reach.
Does it work with shared channels between companies?
Partners from other workspaces can direct-message the app when your Slack plan allows it.
What is still missing?
Files and documents; text is supported.
Can we answer from Slack itself?
Answers are written in the Reach console so they are recorded on the partner record, then delivered to the partner in Slack as the bot.
Read more
-
The whole Reach family →
Reach Core and every channel package, with what each one needs.
Add Slack 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 | 1 |
| Workflow | 2 |
What happens on install
After the import, and only with your consent, the installer runs:
- Reach - Register Channel : Registers the Slack 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 - Slack"
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.
Slack 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.