The use case: how Raycast deploys Slack
Raycast runs its fully remote team in an internal Slack workspace, with channels, huddles, workflows and automated update streams. It uses a second, public workspace to stay in direct contact with its user community, and Slack Connect channels to work with customers and partners.
More reported results
Figures published in Slack’s case study. They are not independently measured by usedby.
some issues move from report to deployed fix within a day
In the customer’s words
I’d have no idea how to run Raycast without Slack. We’re a remote company, so it’s 26 people sitting in 26 different rooms. For us, it’s impossible to do it any other way.Other AI tools used by Raycast
Other public relationships recorded on usedby.
Explore Raycast’s AI stack
Slack users in Workplace Software
Companies in the same sector, with public evidence.
See all Slack customers
Go straight to the source
Based on Slack’s published case study. We check the public evidence; the results are reported by the vendor.
slack.com- Last checked
- Nov 12, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: within minutesChecked
Printed word for word on the page, near the name of Raycast.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Raycast.
- Raycast uses SlackChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Bugs that could sit in a support queue for days can be raised and answered within minutes, in either direction.