An assistant tells you what to do. Ray does it, once you say yes.
Summaries and answers are the easy half. The work is what comes after: filing it, chasing it, updating the record, telling the client. Ray does that half, in the tools your team already uses, and shows you exactly what it is about to do before it does it.
Ray is on Slack today. Free to start, and nothing sensitive happens without your approval.
- 50 free tasks to start, then 25 a month free
- No credit card
- Nothing sensitive without your approval
How it goes now
The version of this everyone recognises, and nobody has time to fix.
- You can get a good summary of a thread and still have to do everything the thread was about.
- The assistant knows what is in Slack and nothing about the tools where the work actually lives.
- Anything that can act either acts without asking, which nobody trusts, or needs a workflow built in advance for each thing it might do.
- Every tool that could help needs somebody to go and open it.
How it actually works
No builder, no workflow to configure, and nothing that acts on its own.
It reads the room, not just the message
Ray is a member of the channels you invite it to and follows them. Mentions work, and so does simply describing something that needs doing.
It reaches your tools, not a copy of them
Trackers, docs, CRM, email, calendars, analytics and billing. Reads run freely, because reading is not the dangerous part.
Anything that changes the world waits
Writes, sends and money show you a card with the exact content first, including the full text of an email. There is no setting that turns that off.
It remembers your team
How you name things, who owns what, which project a nickname refers to. That memory belongs to the workspace and it stays when people leave.
What that looks like in a channel
Somebody says something. Ray does the rest, and asks before anything leaves the room.
“Summarise this thread and file whatever needs filing.”
Ray answers with the summary straight away, then shows you a card for the ticket it wants to create, because one of those is a read and the other is not.
Linear
Jira
Asana
Notion“Email the client the recap.”
Ray drafts it and shows you the recipient, the subject and the verbatim body. Nothing sends until somebody taps Approve.
Gmail
Outlook
HubSpot“How many people search for standup bot?”
Ray looks it up with real keyword data rather than guessing, which is a read, so it just answers.
Google Search Console
Google Analytics
PostHogIt works where the work already is
Each of these has its own page saying exactly what Ray reads and what waits for your approval. Nothing is hidden behind a demo call.
What Ray does not do here
Worth knowing before you try it, rather than after.
- Ray is not a chatbot you configure with workflows and triggers. If you want a builder with branches and conditions, an automation tool is the better fit and we say so on the comparison pages.
- It cannot see channels it has not been invited to, and there is no way to give it a view of the whole workspace at once.
- Of the tools Ray connects, some are read-only, and each integration page states exactly what Ray can and cannot do there.
- Ray is on Slack today. Discord, Teams and Google Chat are planned rather than shipped.
What people ask first
The short answers are here. If we have not covered something, just ask.
Add Ray to one channel and hand it something.
Free to start, no card, about two minutes. Ray sees only the channels you invite it to.